Thanks for reporting it @durrani

Hi @durrani !
I can't reproduce it on develop branch.
What version do you use?

@Pazus
Did you try with 2 unit test packages: ut_name and ut_name_suffix without suitepath?
Can we simply add a test to confirm that this behavior is no longer there, when calling ut.run with test package name?

I've added #470, as the reported side-effect could actually be an interesting feature:
ut.run('test_package*'); could be giving the reported behavior - execute by part of package name.

@Pazus , @durrani, I also cannot reproduce the behavior using our develop branch.
Testcase:

create or replace package ut_test as
--%suite

--%test
procedure aa;
end;
/

create or replace package ut_test_suffix as
--%suite

--%test
procedure aa;
end;
/

exec ut.run('ut_test');

ut_test
  aa [.014 sec] (FAILED - 1)
 
Failures:
 
  1) aa
      ORA-04067: not executed, package body "UT3_TESTER.UT_TEST" does not exist
      ORA-06508: PL/SQL: could not find program unit being called: "UT3_TESTER.UT_TEST"
      ORA-06512: at line 6
Finished in .019856 seconds
1 tests, 0 failed, 1 errored, 0 disabled, 0 warning(s)

Only the ut_test was called.

There was however an issue when calling by suitepath - fixed by @Pazus

Sorry for late reply. Yes, I was also using suitepath. Thank you both.

@durrani you can now use v3.0.3 - fixed

Thank you very much @jgebal @Pazus