| Key: |
SEL-264
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
yourmom
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
All
|
|
|
It would be great to have the option to Run until the first/next test failure.
Since we hope there are zero test failures, stopping to investigate problems would be a good idea.
|
|
Description
|
It would be great to have the option to Run until the first/next test failure.
Since we hope there are zero test failures, stopping to investigate problems would be a good idea.
|
Show » |
|
Run Until Failure
Similar to
SEL-259, but I think nicer for the case described there (running until a broken test), since you don't need to restart the suite to get back there. Plus you presumably don't know where the errors are the first run...As an aside, this situation is probably most common for people who write interdependent tests. Calling serverside setup/teardown methods with TestRunner is non-trivial, so people end up having tests that setup up data for other tests to use. This leads to cascading failures and the need to restart the whole suite. Documentation of 'best practices' might help if this is not an intended use of Selenium.