Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility with Node.js native TAP output #72

Open
guybedford opened this issue Dec 19, 2022 · 3 comments
Open

Compatibility with Node.js native TAP output #72

guybedford opened this issue Dec 19, 2022 · 3 comments

Comments

@guybedford
Copy link

It would be amazing to have a good reporter that has high compatibility with Node.js native TAP output via the new Node.js test core module.

This package gets the closest I've found so far, but with a couple of limitations:

  • Error stacks do not get displayed when piping the tap stream.
  • Skipped tests are not picked up
  • Test "TODO"s are not picked up

I understand node-tap is the target, but I can't seem to find an alternative, and it would be great to have a high quality formatter for these use cases.

@Sceat
Copy link

Sceat commented Dec 26, 2022

The fact that errors are not displayed is a real issue tho, hard to debug without them

@Yamboy1
Copy link

Yamboy1 commented Jan 9, 2023

100% agree. Have been playing around with node:test's tap output with many reporters, and this is by far the one with the best support, but the lack of any diagnostics or error stacks just make it unusable. Additionally, pure TAP output is hard to read, so I think I will have to use node-tap for now instead of node:test purely because of reporter support

vitalets added a commit to vitalets/tap-mocha-reporter that referenced this issue Jan 29, 2023
@vitalets
Copy link
Contributor

I fixed error stacks in this PR.
Until it merged you can use tap-mocha-reporter from the fork:

npm i -D vitalets/tap-mocha-reporter

isaacs pushed a commit to vitalets/tap-mocha-reporter that referenced this issue Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants