Use diag to debug on test failures #1
Conversation
Switch to Test::More instead of hand-coding TAP output Honour NO_NETWORK_TESTING Use strictures
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.
Given the large number of test failures for version 0.80 and the lack of any detail about those failures in the smoke tester reports, this PR is designed to add diagnostic detail in the event of those failures. If a dev release can be published with this amended test then that should hopefully give more to go on regarding the cause(s) of the failures.
I've also taken this opportunity to clean up the test script a little (Test::More, strictures, etc.)
This work was done as part of the CPAN PR Challenge.