-
Consider enable of parallelism inside framework using dbms parallel, job_chains etc.
What are pros and cons.
-
In our project, we have a group of tests that measures the working time of sql queries and compares them with the expected working time. The total number of such tests is approaching 300.
Based on re…
-
Example:
Using utPLSQL, release 3.1.12, installed in the UT3 schema.
```
exec plscope_context.set_attr('OWNER', 'UT3');
exec plscope_context.set_attr('OBJECT_TYPE', 'PACKAGE BODY');
exec pls…
-
Hello,
we are getting this error whenever we try to run tests from a schema which has a name starting with a number.
We have created a package PKG1 on a schema with name 01234567A (these names are o…
-
Information about utPLSQL and Database version:
DB Version: 12.2.0.1.0
UT Version: v3.1.6.2735
JUnitReporter is activated and jenkins job is used to run multiple test cases.
If a test case f…
-
Hi
I get a report coverage from a test package.
I see green lines where these lines are covered and red line where not.
but in case of yellow color: the partially covered line: I didn't understan…
-
As descirbed by oracle - the code coverage should only point on "total_occur". But this is - honestly - not true.
UtPlSqlv3 is pointing to total_occur and total_time is plsql_profiler_data - which …
-
There could be a second type of tests that receives the values from a table. This allows to reuse the same tests with multiple values.
The test should receive a number as parameter (IN). That is the …
-
**Describe the bug**
Different to all the comparison matchers, BE_BETWEEN does not give away details of a type mismatch in its error message. It would be very helpful to have these details, for examp…
pesse updated
2 years ago
-
If a package has case-sensitive name (for example `DWH."aQa"`) `ut_suite_manager` while scanning schema fails with an error when calling `dbms_utility.name_resolve` as we dont add `"`.
The problem …