Jacek Gębal

If your tests share the same suitepath, you can benefit from defining this just once for whole set of test packages (suite)

```sql package common is --%suite --%beforeall procedure setup_sessionh end; package my_tests is --%suite --%suitepath(common) .... end; ```

Well, given this scenario, it would indeed be beneficial to have some basic support for executing some sort of `logon.sql` or `startup.sql` That should be then a feature in api...

I would consider this to be of a low priority for now

There was some interim issue with docker credentials. The images are getting pulled from docker now. There seems to be a different issue with the build process now

The issue is with oracle internal packages. For some reason, DBMS_PLSQL_CODE_COVERAGE fails when code has calls to some of SYS packages. I saw this issue myself when code was calling...

Yes. It requires a change to utPLSQL code.

Currently the `ut_realtime_reporter` is producing following output with disabled flag: ```xml true ``` If test is not disabled we get the following outcome. ```xml false ``` To keep backward compatibility...

@simasch @lwasylow @PhilippSalvisberg

Would GTT suffice? That way you don't need 19c to use it.