Updating TAP reporter to specification version 13 #163
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lib/reporters/tap.js
Outdated
Contributor
Author
|
Sorry about the missing newline. It should be fixed now. |
geek
added a commit
that referenced
this pull request
Aug 20, 2014
Updating TAP reporter to specification version 13
|
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First, this adds the functionality in #119.
Second, the "TODO" and "SKIP" reports were not implemented properly as directives. According to the spec, directives must come after a
#symbol.Finally, since the YAML block can be used to describe any data structure, I moved the stack trace for errors into a multi-line string so it would be compliant with the YAML specification.
Let me know if you have any questions or if this commit needs some cleanup.
Cheers!