Skip to content

Conversation

@jgebal
Copy link
Member

@jgebal jgebal commented Jun 15, 2019

Fixed issue with utPLSQL failing to run when schema contains package named the same as schema owning it.
It is now possible to have utPLSQL test package like this:

create or replace package some_schema.some_schema as
  --%suite

  --%test
  procedure sample_test;
end;
/

create or replace package body some_schema.some_schema as
   procedure sample_test is begin ut.expect(1).to_equal(1); end;
end;
/

The tests from the package can be invoked by calling:
exec ut.run('some_schema.some_schema');

If only schema is provided, all test packages in schema are executed.
exec ut.run('some_schema');

Resolves #569
Resolves #885

Fixed issue with utPLSQL failing to run when schema contains package named the same as schema owning it.
It is now possible to have utPLSQL test package like this:
```
create or replace package some_schema.some_schema as
  --%suite

  --%test
  procedure sample_test;
end;
/

create or replace package body some_schema.some_schema as
   procedure sample_test is begin ut.expect(1).to_equal(1); end;
end;
/
```

The tests from the package can be invoked by calling:
`exec ut.run('some_schema.some_schema');`

If only schema is provided, all test packages in schema are executed.
`exec ut.run('some_schema');`

Resolves #569
Resolves #885
@jgebal jgebal merged commit f8e42da into develop Jun 16, 2019
@jgebal jgebal deleted the feature/remove_dbms_utility_name_resolve branch June 17, 2019 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"Call params for test are not valid" for all tests in specific schema get rid of calls to dbms_utility.name_resolve if possible

3 participants