Skip to content

/ utPLSQL-SQLDeveloper

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Coverage on another schema objects #63

Closed
jgebal opened this issue Jul 4, 2019 · 1 comment
Closed

Coverage on another schema objects #63

jgebal opened this issue Jul 4, 2019 · 1 comment
Assignees
@PhilippSalvisberg
Labels
enhancement
Milestone
v1.1.0

Comments

@jgebal
Copy link
Member

@jgebal jgebal commented Jul 4, 2019

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
@PhilippSalvisberg PhilippSalvisberg self-assigned this Jul 5, 2019
@PhilippSalvisberg
Copy link
Member

@PhilippSalvisberg PhilippSalvisberg commented Jul 5, 2019 •
edited

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.
@PhilippSalvisberg PhilippSalvisberg added this to the v1.1.0 milestone Jul 5, 2019
PhilippSalvisberg added a commit that referenced this issue Jul 14, 2019
@PhilippSalvisberg
Merge pull request #72 from PhilippSalvisberg/feature/63_coverage
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.
GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
c59c506 
#63 - Improve code coverage for other schemas
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PhilippSalvisberg PhilippSalvisberg

Labels
enhancement
Projects
None yet
Milestone
v1.1.0
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@jgebal @PhilippSalvisberg
You can’t perform that action at this time.