Description
From #618 (comment)
For most test suites, the mini reporter just spits out test titles faster than the human eye can process. This gives you warm fuzzies knowing that things are actually happening, but it's not super useful. Which test failed is generally the most valuable feedback your test suite gives you, so it seems silly to make users wait until all the tests have run to deliver valuable information we already have.
My first idea was that, in addition to the current test, the reporter should persist the title of the most recent failure. This would work well if there was a single failure early on, but not so good if there were lots of failures, rapid fire, throughout the test run.
*UPDATE: * We are going with @vdemedes solution here: #653 (comment)
I now think we could do this even better by processing keys from stdin, I am thinking something like the following:
The tests titles fly by, you see the error count incrementing, and the title of the most recent failure is "sticky" (shown until a new failure comes along). This is basically the same idea I had before.Pressing ⬆️ puts you into error review mode, and the title of the most recent failure (at the time the ⬆️ was pressed) is now really sticky - incoming failures do not cause the "sticky" failure title to be updated.Pressing ⬆️ again takes you one failure earlier in the "failed test" list.Pressing ⬇️ takes you later in the list.Pressingenter/returnexits error review mode.
IssueHunt Summary
m5x5 has been rewarded.
Backers (Total: $60.00)
issuehunt ($60.00)
Submitted pull Requests
Tips
- Checkout the Issuehunt explorer to discover more funded issues.
- Need some help from other developers? Add your repositories on IssueHunt to raise funds.