runtimetest: Granular TAP output#1
Closed
wking wants to merge 3 commits intomrunalp:tap_runtime_testfrom
Closed
Conversation
Author
|
You could also pull the TAP harness outside of or similar. That way folks can easily swap in their own preferred harness. Let me know if you want me to reroll taking that approach. |
Author
|
Better skip support is on the way with mndrix/tap-go#6, so it's probably best to hold off here until that lands and I reroll this to take advantage of it. |
Author
|
I've pushed b462307 → f3c0d27 with |
This reverts commit 67daea2. We won't need these with granular TAP handling. Conflicts: Godeps/Godeps.json Signed-off-by: W. Trevor King <wking@tremily.us>
I couldn't figure out how to do this with 'godep update', so I just copied the files over and bumped the hash by hand. Signed-off-by: W. Trevor King <wking@tremily.us>
Granular TAP output makes it easier to see what's being tested (and what's going wrong). You could feed this into any TAP harness you like, but I've chosen prove (it seems popular). You need a TAP harness looking for test failures, because runtimetest now returns zero when it successfully runs the tests (regardless of whether the tests all pass). With this commit, runtimetest will exit zero when it can successfully *run the tests* (regardless of whether all the tests pass). A TAP harness like prove should be used to consume the output TAP to decide if validation succeeded or not. To avoid confusing the TAP consumer, all of the non-TAP logging goes to stderr (and not stdout). Signed-off-by: W. Trevor King <wking@tremily.us>
Author
|
Shifted to opencontainers#308. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Granular TAP output makes it easier to see what's being tested (and what's going wrong). You could feed this into any TAP harness you like, but I've chosen prove (it seems popular). You need a TAP harness looking for test failures, because runtimetest now returns zero when it successfully runs the tests (regardless of whether the tests all pass).
The
OPTINDshift is out ofgetopts(1p).I've dropped the “VALIDATING RUNTIME” header since prove displays the command it's running in its usual output (e.g.
/usr/bin/runc .. ok).Full example output:
And failing (if I just run
runtimetestin my host namespace):