Jacek Gębal

--%throws annotation named package constant/variable not recognized

1

When a test is executed, the named constant is being searched in scope of current user (user executing the tests. This is not how it is expected to work. Example...

Parameter drive tests

9

There is an interesting extension to JUnit: https://github.com/Pragmatists/JUnitParams We could think of implementing something similar. Here are examples of different ways to use it. https://github.com/Pragmatists/JUnitParams/blob/master/src/test/java/junitparams/usage/SamplesOfUsageTest.java

Currently http://utplsql.github.io/ is describing only the utplsql project. It should be describing utPLSQL organization and contain links to the individual sub-projects. Each project should have (optionally) it's own gh-pages branch...

**Describe the bug** When running tests with `ut_tfs_junit_reporter` on suite packages containing contexts, each context is reported as a separate suite. This doesn't seem correct as we loose ability to...

Add LCOV coverage reporting as a replacement for COVERALLS reporting

2

Existing COVERALLS reporting is no longer easy to publish to COVERALLS. If users would be using GithubActions/AzurePipelines etc., the preferred format would be LCOV. The preferred way to publish coverage...

Document how to run tests located in a given suite context

1

**Is your feature request related to a problem? Please describe.** Current documentation does not mention how to invoke utPLSQL to run tests from specific suite context. **Describe the solution you'd...

Document integration APIs for consumers

2

It becomes more and more important to have well documented public APIs. This is especially relevant for all the ut_runner invocation as well as reporters. That should be the baseline...

**Is your feature request related to a problem? Please describe.** With introduction o context for tests in utPLSQL v3.1.8, it is no longer possible to install multiple instances of utPLSQL...

# Current state When running matchers for compound (diff-able) data-types, we currently report actual and expected data only. No diff information is available when running `not_to_equal` and `not_to_contain` # Ideal...

Building custom reporters

1

Enhance documentation to include steps explaining how to build custom reporters. There are two types of reporters to be explained. - Output reporter - provides output to client (using output...