-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have one code coverage report per database instance not per connection #27
Comments
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). |
Yes. I totally agree - one app can use several databases. |
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.
The text was updated successfully, but these errors were encountered: