Skip to content

Coverage on another schema objects #63

Closed
@jgebal

Description

@jgebal
Member

There are following issues:

Include objects not populated when selecting Other user

When opening a Code coverage report window by navigating: Connection->Other Users->Some User->Packages->UT_package->Right click (Code coverage), the field Include objects is not getting populated.

Expected behavior

Include objects gets populated the same way as it is when navigating: Connection->Packages->UT_package->Right click (Code coverage)

The objects on Include objects list re not prefixed with owner

When tests are located in different schema then the tested code, the populated Include objects list does not give expected results - no coverage is showing.

The objects need to be prefixed with schema name.

Below animation illustrates both issues as well as the correct outcomes

SQLDev-coverage_issue

Activity

PhilippSalvisberg

PhilippSalvisberg commented on Jul 5, 2019

@PhilippSalvisberg
Member

Thanks for reporting this issue.

Populating default values for include objects is currently supported only for tests suites owned by the connected user. It's a good idea to support that as well for users listed below the Other Users node.

In your case you can connect to ut3_tester and run code coverage from there, entering UT3 for schema under test. As you shown, it does not work. The reason is, that ut3_tester lacks the necessary privileges to produce a code coverage result for the UT3 schema. As soon as you grant the necessary privileges (e.g. the DBA role or something more sensible) this works. I agree that we should simplify the usage of code coverage and prefix all include objects by its owner. Then Schemas unter test could be left empty.

added this to the v1.1.0 milestone on Jul 5, 2019
added a commit that references this issue on Jul 14, 2019

Merge pull request #72 from PhilippSalvisberg/feature/63_coverage

c59c506
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @jgebal@PhilippSalvisberg

      Issue actions

        Coverage on another schema objects · Issue #63 · utPLSQL/utPLSQL-SQLDeveloper