Closed mmkal closed 4 years ago
From what I have read about the TAP standard these additions we are talking about are outside of the specification, so we can call them and format them however we want?
So we could use your filepath, line and colum as a starting point, adding this to the output in both error and pass? https://github.com/avajs/ava/blob/master/lib/reporters/tap.js#L35:L51
Do we actually have access to that information when we are in the reporter though? As far as I know thats not in test.metadata or anything else?
From what I have read about the TAP standard these additions we are talking about are outside of the specification, so we can call them and format them however we want?
Yes. They should be added as data in the YAML-block. There we are free to add whatever data we want.
So we could use your filepath, line and colum as a starting point, adding this to the output in both error and pass? https://github.com/avajs/ava/blob/master/lib/reporters/tap.js#L35:L51
👍
Do we actually have access to that information when we are in the reporter though? As far as I know thats not in test.metadata or anything else?
Only for errors currently, but would be useful to have it in the metadata.
Simple feature request... it'd be nice if the filename for a TODO test was shown (in the same way as it is for a failing test), so TAP parsers/IDEs can see them.
For example, with a Visual Studio Code task problem matcher, they could be flagged up as informational or warning problems. Then clicking on them in the "problems" view would take focus straight to the call to
test.todo(...)
.