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
You can now use custom extensions (in version 3.1.0+) simply add the extension to the end of your file name. If none is provided tap-junit will still default to .xml
The above will create a file called tape.xuni in the output/tests directory with the results inside.
Output
Tap-Junit currently follows this spec on junit syntax/layout
<testsuitestests="4"name="Tap-Junit"failures="2">
<testsuitetests="4"failures="2"skipped="1">
<testcaseid="1"name="test is equal"/>
<testcaseid="2"name="test skip extra # SKIP">
<skipped/>
</testcase>
<testcaseid="3"name="should not be equal"/>
<testcaseid="4"name="should be equal"/>
</testsuite>
</testsuites>
Comments
So Tap Junit takes a tape style assumption when it comes to comments. That being, when a comment appears before a test (because that's how tape labels its tap output) it will be registered as a comment for that test, but the issue here is that you may lose placed comments in your tap files.
At the moment, I'm still trying to figure out a decent way to handle comments and record them. Keep this in mind that only a single comment before each test will currently be recorded for a system-out tag.
If you have ideas on how to better handle this, don't hesitate to reach out!
About
A silly simple, silly small XML output for tap/tape tests to convert them to junit