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
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(...).
The text was updated successfully, but these errors were encountered:
Yeah, that would be useful for our Atom and Sublime plugins too. I think we could add some custom metadata to the TAP output, like filepath, line, column. Actually, we should really include that info for all tests.
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?
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.
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(...)
.The text was updated successfully, but these errors were encountered: