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
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!
The text was updated successfully, but these errors were encountered:
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
: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 liketap-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: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 myqunitx
cli if no extra build step is needed. Thanks again for this great work/reporter!The text was updated successfully, but these errors were encountered: