Skip to content
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

Write a TAP legacy formatter. #215

Closed
schwern opened this issue Nov 16, 2011 · 1 comment
Closed

Write a TAP legacy formatter. #215

schwern opened this issue Nov 16, 2011 · 1 comment

Comments

@schwern
Copy link
Contributor

schwern commented Nov 16, 2011

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.

@ghost ghost assigned schwern Nov 30, 2011
schwern added a commit that referenced this issue Nov 30, 2011
* 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
schwern added a commit that referenced this issue Nov 30, 2011
@schwern
Copy link
Contributor Author

schwern commented Nov 30, 2011

There's probably other issues, but it will shake out as we test it against CPAN modules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant