A test runner with rich features is needed
Bug #65598 reported by
Jamu Kakar
on 2006-10-12
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Ion |
Medium
|
Jamu Kakar | ||
Bug Description
A smart test runner is required to make running tests easy, especially for large test suites. The test runner should be able to:
- pattern match to select tests to run
- pattern match to ignore tests
- log test results
- stop at the first test failure
- randomize test order (reproducibly)
- break into a debugger when a test fails
- report test results tersely and verbosely
Jamu Kakar (jkakar)
on 2006-10-12
| description: | updated |
| Jamu Kakar (jkakar) wrote : | #1 |
| Jamu Kakar (jkakar) wrote : | #2 |
Merged to ion/trunk r29.
| Changed in ion: | |
| assignee: | nobody → jkakar |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
Jamu Kakar (jkakar)
on 2009-07-15
| Changed in ion: | |
| milestone: | none → 0.1.0 |
To post a comment you must log in.
It would be cool if the test runner could be run in a mode where
it'll stop at the first failure and store the failure point. On
subsequent runs it should continue from this failure point,
repeating the same behaviour.