New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test suite started to fail (with Test2::Suite 0.000121?) #1
Comments
I introduced a new 'Fail' event that combines the failed assertion and the diagnostics into a single event, some Test2::Suite tools were switched to use it. These tests will need to be updated to support the new events. I am thinking about how to avoid these kinds of issues in the future, I am thinking a test-testing tool that does not pay attention to the event types, but rather just pays attention to their effect. But you should not wait for that before updating your tests. Sorry for the inconvenience. |
Changelog diff is: diff --git a/Changes b/Changes index ebfc75a..2d986c6 100644 --- a/Changes +++ b/Changes @@ -2,6 +2,12 @@ Revision history for Perl extension Test2-Tools-JSON {{$NEXT}} +0.04 2019-08-07T10:01:59Z + + - fix broken tests in new version of Test2 (fix #1) + - pass $seen from params + - add Test2::V0 deps + 0.03 2018-01-30T09:03:58Z - same behavior of JSON::decode_json
With 0.04 it looks like this:
That is, it passes if Test2::Suite 0.000121 or 0.000122 is installed, and fails with older versions. |
Changelog diff is: diff --git a/Changes b/Changes index 2d986c6..4b66685 100644 --- a/Changes +++ b/Changes @@ -2,6 +2,10 @@ Revision history for Perl extension Test2-Tools-JSON {{$NEXT}} +0.05 2019-08-07T21:52:49Z + + - fix broken tests again + 0.04 2019-08-07T10:01:59Z - fix broken tests in new version of Test2 (fix #1)
@eserte Thank you. I've released these fixes with 0.05. |
The tests started to fail. Beginning of test log:
Statistical analysis suggests that the failure started with Test2::Suite 0.000121 (@exodist: FYI):
The text was updated successfully, but these errors were encountered: