Skip to content

test.py tap13 output

Here's a work in progress that generates valid (ish -- haven't tested all kinds of stuff just yet) tap13 output from the test runner. I was initially thinking that we'd do a separate test runner (tap and tap13) but seeing how our current tap is invalid at best and this diff is easier to read I thought I'd post it in its current state for feedback/discussion.

Together with https://pypi.python.org/pypi/tap2junit we now generate junit that jenkins like.

Open issues/things to discuss:

  • ~~cctest output needs to be changed -- invalid failures~
  • do we split up tap vs tap13 (i prefer not)
  • if not, is this a semver major or minor? hard to say with tooling; especially seeing how our tooling has been invalid for so long.

I'll rebase/clean up once we converge on what to do. Hopefully we can get this in as quick as possible -- the build groups general theory is that this will Make Jenkins Great Again.

Merge request reports

Loading