Add TAP reporter#1305
Conversation
|
Hi @WayneNani, One thing could you please update the documentation reporters section with screens etc.? Kind regards Lukasz |
Sorry, something went wrong.
|
Hey @lwasylow , |
Sorry, something went wrong.
Sorry, something went wrong.
|
Sorry, something went wrong.
|
Hello @WayneNani As you have probably noticed, the project was on pause for quite some time. Will you be available to address the review comments (if any)? |
Sorry, something went wrong.
|
Hey @jgebal, I am happy to address any remarks you have. |
Sorry, something went wrong.
|
@WayneNani How would the TAP reporter show results of nested suites or suite with contexts? I would expect the report to show it as a subtest according to the TAP specification. Even it it is already implemented in this PR, it is not mentioned in documentation of reporter and it is not expressed in the tests. I would expect reporter to support the Commented Subtests (those are recommended).
|
Sorry, something went wrong.
|
@WayneNani Once this is done. We will include this change in next release (coming soon). |
Sorry, something went wrong.
|
@jgebal Thanks for the review! You are right, I forgot to include tests regarding suites and contexts and have fixed that. I decided to use the existing reporters test package which comes with a suitepath and context and left the escaping test package nearly untouched. |
Sorry, something went wrong.
|
Because our pipeline doesn't seem to work with external PRs anymore, I will pull and deploy your changes locally to take a look. |
Sorry, something went wrong.
|
@WayneNani Thank you 👍 Starting with next release we will be only suppoorting DB 19c and above. Hopefully you don't need the reporter for any unsupported version of Oracle. |
Sorry, something went wrong.
7ce1909
into
utPLSQL:develop
Mar 19, 2026




I added a reporter for the Test Anything Protocol . It is easy to read for humans and machines alike and supported by a wide variety of consumers. These consumers can then aggregate test results from different projects or programming languages.
I tried to include all features from the latest TAP Specification as far as utPLSQL supports them (i.e., TODO tests are not supported in utPLSQL as far as I know).
I also added some test cases that should provide a decent coverage.
Please feel free to let me know if I can add anything else.