On Apr 20, 4:27 am, bwaybandit <[email protected]> wrote: > use 'rescue' to handle your exception and there you can pass on > control to your next test or not. use unit/test framework to write > your tests. All that is handled for you. >
But do be aware that by design with most of these frameworks, when assert fails, that's it for the test it was executing, the framework will move onto the next defined test, but it won't continue executing code in that test SO if you had something like def test_My_First_test <code to get to where you can do your asserts> <firstassert> <secondassert> <thirdassert> end if the first assert fails, the other two will never get run, the framework will report the failure and move on to the next test at that point. that all makes a lot of sense to a dev who says 'well crud, if failed, better figure out what got broke'.. at the same time it frustrates the hell out of the QA guy like me who wants to know "what about the other two tests in that area? are they broke also, or what? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to [email protected] Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
