Releases: dhershman1/tap-junit
Releases · dhershman1/tap-junit
v5.0.4
v5.0.3
New
- Setup github actions
Fixed
- Removed LGTM badge from README
- Remove circleci workflow
Chore
- Dependency version bumps to next major releases
- Audit cleanup
v5.0.2
Fixed
- Dependency Version Bump (#42) (Thanks @Turtl3Squad)
v5.0.1
v5.0.0
Breaking Changes
- Changed the output generation of tap-junit to follow this spec more closely #37
- This means no more floating comments, they are now either in the
system-out
tag or themessage
attribute
- This means no more floating comments, they are now either in the
- Changed how handling tap comments works, please see the Comments section in the Readme
Improved
- Bit of re organization of the tool
- Bumped Docker node and tap versions
Fixed
- Broken comments on some tap outputs
v4.2.0
v4.1.0
v4.0.0
BREAKING CHANGES
- Converted from tap-out to tap-parser
- This change means that the xml generated is now "Flat" (see below)
- This removes the error count as there isn't an event for this anymore
- Skips are handled WAY better and more naturally with TAP
- This should flow better with proper tap output
- If a file extension is set in the command, it will be used for the generated file, if not
.xml
will be used - Error counter removed with new parser
- The
testcase
name no longer has test number, the test number is now provided in theid
attribute oftestcase
New
- Todo support
- Added new argument support
-p
or--pretty
use this if you want the xml output to be "pretty" (this isfalse
by default)
Improved
- Optimized performance from both parsing and serializing
- Data is built more dynamically, instead of relying on certain keys to exist
- Better JUnit formatting
- Moved from xmlbuilder to xmlbuilder2
Flat XML
Now <testsuits>
containes only a singular <testsuite>
element, within that all of the <testcase>
elements now live. Here's an example:
v3 tap-junit output:
<testsuites tests="4" name="suite-name" failures="0" errors="0">
<testsuite tests="3" failures="0" errors="0" name="1 === 1">
<testcase name="#1 test is equal"/>
<testcase name="#2 test skip extra # SKIP">
<skipped/>
</testcase>
<testcase name="#3 should not be equal"/>
</testsuite>
<testsuite tests="1" failures="0" errors="0" name="2 === 2">
<testcase name="#4 should be equal"/>
</testsuite>
<testsuite tests="0" failures="0" errors="0" name="SKIP skipped test"/>
</testsuites>
v4 tap-junit output:
<testsuites tests="4" name="Tap-Junit" failures="2">
<testsuite tests="4" failures="2" skipped="1">
<testcase id="1" name="test is equal"/>
<testcase id="2" name="test skip extra # SKIP">
<skipped/>
</testcase>
<testcase name="#3 should not be equal"/>
<testcase id="3" name="should not be equal"/>
<testcase id="4" name="should be equal"/>
</testsuite>
</testsuites>
v3.1.2
v3.1.0
New
- You can now use custom extensions, just apply then to your file name in the
-n
option (#24)- Example:
tape test/*.js | tap-junit -o output/tests -n tape.xuni
- If no extension is provided
tap-junit
will default to.xml
automatically
- Example:
Improved
- Slight tweak to the contribution and PR template mark down files