Fixed stack parsing when test failed with ` ut.fail ` #380 jgebal merged 13 commits into utPLSQL : develop from Pazus : issue-378 Jul 4, 2017 Conversation 23 Commits 13 Checks 0 Files changed, utPLSQL uses XMLType internally to represent rows of the cursor data. This is by far the most flexible method and allows comparison of cursors containing LONG, CLOB, BLOB, user defined types and even nested cursors. … The call to ut.fail is required to make sure that the test fails, if we expect an exception, …
extended_option can be one of:. include(a_items varchar2) – item or comma separated list of items to include exclude(a_items varchar2) – item or comma separated list of items to exclude include(a_items ut_varchar2_list) – table of items to include exclude(a_items ut_varchar2_list) – table of items to exclude unordered – ignore order of data sets when comparing data.
7/5/2019 · When all tests are run via top suite selection, then all tests succeed. But the following three utPLSQL tests fail when they are run isolated (in a new connection): at UT3$USER#.TEST_COV_COBERTURA_REPORTER.REPORT_ON_FILE, line 41 ut.expect (l_actual).to_be_like (l_expected), 7/13/2017 · Pazus merged 1 commit into utPLSQL : develop from unknown repository Jul 13, 2017. … is now also shown for unit tests owned by other users #380 Line no of failed test is now properly reported when using ` ut.fail ` #375 Annotation parameter list can now have spaces before/after brackets #373 Warnings in documentation reporter are now …
utPLSQL v3 Cheat Sheet from jgebal. procedure my_code_raises_zero_divisor is l_my_number number begin l_my_number := 1/0 –should raise ut.fail (‘Expected exception but.
7/18/2017 · utPLSQL v3.0.2 – released. Changes in this release. Documentation. Documentation now refers to migration project Documentation now refers to a valid object name: ut_file_mapping, 7/14/2017 · Pazus merged 2 commits into utPLSQL : develop from unknown repository Jul 14, 2017 Conversation 2 Commits 2 Checks 0 Files changed Conversation, 6/26/2017 · jgebal merged 2 commits into utPLSQL : develop from unknown repository Jun 26, 2017 Conversation 2 Commits 2 Checks 0 Files changed Conversation, 11/26/2019 · Hi! What started in a Slack chat grew into this issue 🙂 I have a test with Russian words in its name. So I expect it to be Russian when I call it via cli. Here’s my preset: NLS_DATABASE_PARAMETERS: NLS_TERRITORY = AMERICA NLS_LANGUAGE…
