"Run Selected Unit Tests" fails when context name contains upper case chars

[dirk.mika1]

1. Create a unit test package like:

   CREATE OR REPLACE PACKAGE ut_test
   IS
      -- %suite
      -- %suitepath(test.sub1)

      -- %beforeall
      PROCEDURE setup;

      -- %context
      -- %name(Context1)

      -- %test
      PROCEDURE test01;

      -- %endcontext
   END ut_test;
   /

2. Click on "Run Selected Unit Tests" in the context menu in the Unit Test Manager on the node that represents the context.
   

   

3. The following error occurs:

ORA-20204: No suite packages found for path SP_UT2:test.sub1.ut_test.context1.
ORA-06512: at "UT3.UT_RUNNER", line 158
ORA-06512: at "UT3.UT_SUITE_MANAGER", line 343
ORA-06512: at "UT3.UT_SUITE_MANAGER", line 343
ORA-06512: at "UT3.UT_SUITE_MANAGER", line 369
ORA-06512: at "UT3.UT_SUITE_MANAGER", line 457
ORA-06512: at "UT3.UT_SUITE_MANAGER", line 553
ORA-06512: at "UT3.UT_RUNNER", line 146
ORA-06512: at line 21

If I name the context context1 instead of Context1 the error does not occur.

[mstaszew]

Thanks, I can reproduce and will investigate.

Michael

[mstaszew]

I believe this is a defect/behavior within utPLSQL. I will raise an issue with them to see what they say.

In one of the posts on their GitHub Issues page they reference a query that can be used to return all runnable paths for a suite.

select object_owner||':'||path as runnable_path,
       item_line_no,
       item_description,
       object_name,
       object_owner,
       item_type
  from table( ut_runner.get_suites_info('MSTASZEW', 'UT_TEST')) x
;

Here are the results from my test:

And using the exact path their query returns I see the same error:

It's been two years since their last release (v3.1.14) and they have some open issues still so I think you should just use your workaround in the meantime.

Michael

[mstaszew]

@dirk.mika1 - I logged an issue with utPLSQL. You can monitor this issue and follow its progress. ORA-20204 raised when running a context path · Issue #1317 · utPLSQL/utPLSQL · GitHub

The defect is on the utPLSQL side so once they fix it you'll need to update. I don't expect any Toad changes will be required to support it.

Michael