Have one code coverage report per database instance not per connection

[jgebal]

This is a feature request.
It would be nice to have the coverage reports generated and saved differently then the current approach.
Currently one report is generated per one database connection.

When analysing code coverage we usually look at coverage per instance.
There are cases when for testing single instance multiple connections need to be used.
The code coverage in the current state does not give a true value in those cases.

The existing reports could still be generated and accessed with chooser on the index.thml, just similar to the way we currently have filter combo-box for schema names.

[javornikolov]

Actually it might be not even a single database. One app may be based on multiple databases (one or several schemas per app in a DB).

[jgebal]

Yes. I totally agree - one app can use several databases.
From the coverage report, it would be good to have one report per database instance not per database connection.
The difference is, that if tests are using several connections to one database, the coverage report on a connection level will not give a true picture of code coverage.
The true code coverage will be a coverage as it is by all connections to a particular database.