Jacek Gębal

> Maybe also by default include the objects directly referenced by test package? Sorry @PhilippSalvisberg That is irrelevant. I forgot that this functionality is already implemented.

What version of utPLSQL do you have in database? Can you check select ut.version() from dual;

Also have a look at #99

Well... It's probably not just hypothetical issue. I actually have higly shared DB, where developer accounts have concurrent session limit of 4. So if I want 4 reports I neet...

Potentially faster execution time if reading reporters output takes more time. This is however only a hypothesis so probably no real benefit until proven otherwise.

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....

At the moment there is no way to include/exclude objects in coverage by object type in utPLSQL core framework. Also, the option for inclusion/exclusion of objects by regular expression is...

Currently one coverage reporter operates on a single connection alias.

Currently it's a bit dirty. Your local project spec_helper.rb is controlling it. The local project spec_helper is uncovering the ruby-plsql-spec library internals by referencing env parameters used by library and...

Hard to explain. I'll make changes in a branch and share. On 23 Nov 2015 22:13, "Yavor Nikolov" [email protected] wrote: > OK, I see now > > PLSQL::Coverage.start(name) > >...