Jacek Gębal

The problem seems unrelated to `ut.expect` but related to heterogenous services and autonomous-transactions. if instead of running: ``` set serveroutput on begin ut.run('test_my_package'); end; ``` You run: ``` set serveroutput...

Before building the documentation some additional refactoring is needed on reporters and buffer. I have an idea that can simplify reporter building reporters significantly. It will also dramatically reduce amount...

I think it would be good to do a full review of what JUnit is proposing for parametrized tests and maybe check how other testing frameworks are solving this. In...

What version of database are you using?

It looks like the schema you're running coverage on contains some really long lines. Those lines mist contain lots of special characters (from XML/HTML point of view) and so they...

We could probably trim the source code when it is too long, that's the one option that I see a possible.

Hi @jashka34 utPLSQL framework cannot be installed un edition-enabled schema. I strongly suggest installing utPLSQL in separate schema (database-wide) that is not edition-enabled. That way, all users of DB can...

Hi @jashka34 I think there are two options. - I can try to make the utPLSQL framework installable in edition-enabled schema - no need to update documentation - I can...

The workaround for now would be for you to change all the source code and add: `noneditionable` to all packages/types/triggers/synonyms in utPLSQL installation. In order for us to do this...

Let me see if I can make it happen. I think I had a branch open for this some time ago.