You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initial support for running test failures first via failures_first=true (#212)
* Hacky prototype for running test failures first
* Also sort unseen before passes
* Use id => unit8 mapping
* Update option name, default it to true
* Add tests
* Defailt to `false`
* Another test
* Add to README
* Bump version
* Support nworkers>0
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,6 +130,12 @@ You can set `runtests` to stop on the first test-item failure by passing `failfa
130
130
131
131
If you want individual test-items to stop on their first test failure, but not stop the whole `runtests` early, you can instead pass just `testitem_failfast=true` to `runtests`.
132
132
133
+
#### Running previous failures first
134
+
135
+
You can set `runtests` to run first any test-items that failed the last time they were run by passing `failures_first=true`.
136
+
When `failures_first=true` is set, test-items are order so that previously failing test-items run first, followed by previously unseen test-items, followed by previously passing test-items.
137
+
138
+
This option can be combined with `failfast=true` to efficiently find the next failing test-item during development.
0 commit comments