Timeline for How do you design your test method/function
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 2, 2018 at 10:08 | history | edited | Bharat Mane♦ | CC BY-SA 3.0 |
formatting
|
| May 31, 2011 at 3:50 | comment | added | Tarun | @marc, this is exactly what I do | |
| May 30, 2011 at 13:16 | comment | added | user246 | @marc Selenium does not dictate what happens when an assertion fails; that is up to the framework. You if you use Selenium with JUnit, you will get the semantics you described. Of course you don't have to use JUnit in order to use Selenium. | |
| May 29, 2011 at 22:19 | comment | added | Aruna | +1 Good point, Exactly! Assert will stop the execution of the test case if the verification point fails while verify continues. When multiple checks are used it is better to go for verify. | |
| May 29, 2011 at 21:03 | comment | added | marc | You may also want to consider what happens when an assertion fails. For example, in Watir (and Selenium I think), a failed assertion will end the test and move on to the next one. If you use verify, it will log the failure and continue on. I prefer to use verify if I'm grouping multiple checks into one test case that may fail independently of each other (ex. UI verifications). | |
| May 29, 2011 at 18:44 | history | answered | Aruna | CC BY-SA 3.0 |