- Don't use full URLs with open/openWindow commands (http://baseurl part will be added by ERSelenium):
- You can use setup/teardown methods. They should be implemented as direct actions in the separate class, which should be er.selenium.SeleniumAction-descendant. SeleniumAction class has some handy helper methods and automatically turns your selenium-related actions off when selenium is disabled in Properties. Here's the example of using selenium-related direct actions in the test (suppose that resetSessionAction() is defined in the class "Selenium"):
- You can use @repeat-@values-@done metacommands to execute specific part of the test with additional values edited in textboxes, e.g.:
The commands between @repeat and @done will be repeated several times, each time with new value in "user" and "password" input field. The values are seperated by spaces and if you have multiple @values lines, they all must have the same number of parameters. The @values section applies to the value of the next command.
@repeat ...some actions... @values user1 user2 user3 |type|user|user0| @values pass1 pass2 pass3 |type|password|pass0| ...some more actions... @done