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

Expose a cli/stream interface #8

Open
izelnakri opened this issue Feb 20, 2021 · 0 comments
Open

Expose a cli/stream interface #8

izelnakri opened this issue Feb 20, 2021 · 0 comments

Comments

@izelnakri
Copy link

izelnakri commented Feb 20, 2021

Hi there I'm also currently experimenting with a new testing framework but its rather targeting qunit instead of introducing anything new: https://github.com/izelnakri/qunitx

I've been investigating existing TAP reporters on npm, most of them are old, not well maintained and lacking proper DX-friendly test failure diffing. In fact the best one I could find is tap-difflet:

ava test/some-test.js --tap | npx tap-difflet

Currently I decided to always output TAP just like tap.js for qunitx, however would like to see more tap reporter alternatives npm for obvious reasons. Do you plan to implement a cli that receives streams and output reports like tap-difflet? Something like this would be great I think, I've read through the documentation and bit of the code, doesnt seem its implemented yet:

node test/some-test.js | treport # first command outputs TAP

Also, is there a way to also expose a node.js interface without an additional builder for react/jsx? Perhaps I can use treport directly in my qunitx cli if no extra build step is needed. Thanks again for this great work/reporter!

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

1 participant