Jacek Gębal

I'll be happy to look into that

There are tow things here: - scope of coverage - size of project Does your project files = whole DB schema? If project < schema. Do you want to report...

To map your project files to db objects use parameter `-source_path` If your project files are distributed across multiple DB schemes we expect by default the naming convention of: -...

@tkleiber If you want to give a try to coveralls or sonar coverage you can give an example project structure/file names and we can help you figure how to configure...

Yes. One reporter=one output stream. If we would go that way, we would make PLSQL call to html report useless. For large codebase it is best to use sonar/coveralls reporting....

What CI are you using? How do you report coverage on other code that PLSQL? Answers to those questions can give some options.

OK. I've heard about jacoco a bit here and there. Seems quite common format.

utPLSQL/utPLSQL#557 created for this

Interesting idea. Reporter could create multi-file zip as BLOB and we could then unzip it in utPLSQL-cli side. That would require: - new (binary) output buffer - rebuild of the...

This can be done within reporter. Reporter gets whole suite before run starts. The big quiestion is, should it be part of reporter ir part of API. Should it be...