You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TAP v13 formatter contains a lot of improvements. Unfortunately, a lot of CPAN module tests look at the exact output of Test::Builder. They'll break.
One way to to fix this is to have a legacy TAP formatter, we'll call it TAP::TB1, which outputs just like Test::Builder 0.x does. Then test suites can use it. Test::Builder::Tester can also default to it.
Since most of the differences are strings embedded in complicated logic, a good solution would be to turn those strings into configurable attributes. Then have the TB1 formatter use different defaults. #219 should be done first.
The text was updated successfully, but these errors were encountered:
* Make the ending commentary dynamic in TAP::Base.
* Make the directive label dynamic.
The exit code commentary is still in Test::Builder, not in the formatter. I don't think
that's critical, I doubt most tests were relying on that.
For #215
The TAP v13 formatter contains a lot of improvements. Unfortunately, a lot of CPAN module tests look at the exact output of Test::Builder. They'll break.
One way to to fix this is to have a legacy TAP formatter, we'll call it TAP::TB1, which outputs just like Test::Builder 0.x does. Then test suites can use it. Test::Builder::Tester can also default to it.
Your task is to write this.
That's off the top of my head.
Since most of the differences are strings embedded in complicated logic, a good solution would be to turn those strings into configurable attributes. Then have the TB1 formatter use different defaults.
#219 should be done first.
The text was updated successfully, but these errors were encountered: