Jeremy wrote: > I know that Quixote uses test cases in strings, but it's the thing I > like the least about Quixote unittest like whitespace indentation, it's done that way for a reason. > I'm not sure how to achieve this or why you would want the test to > continue. same reason you want your compiler to report more than just the first error -- so you can see patterns in the test script's behaviour, so you can fix more than one bug at a time, or fix the bugs in an order that suits you and not the framework, etc. (for some of our components, we're using a framework that can continue to run the test even if the tested program dumps core. trust me, that has saved us a lot of time...) > After the first exception, something is broken and needs to be > fixed, regardless of whether subsequent lines of code work. jeremy, that's the kind of comment I would have expected from a manager, not from a programmer who has done lots of testing. Cheers /F
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4