It could be on by default, or through a command-line argument. This way you can quickly click on the filename/line number in VS Code to jump to the failing test. And by having the input that the test failed on, you could diagnose what happened without having to look up the spec in the first place.
Here's an example of what failing test output looks like today, without the filename/line number or input for the failed test.
↓ Tests
↓ Bob
✗ stating something
"Fine. Be that way!"
╷
│ Expect.equal
╵
"Whatever."
It could be on by default, or through a command-line argument. This way you can quickly click on the filename/line number in VS Code to jump to the failing test. And by having the input that the test failed on, you could diagnose what happened without having to look up the spec in the first place.
Here's an example of what failing test output looks like today, without the filename/line number or input for the failed test.
Moved from https://github.com/rtfeldman/node-test-runner/issues/428