-
Notifications
You must be signed in to change notification settings - Fork 185
Coverage report only on test packages #367
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
Comments
You should be able to see coverage on the source code rather than on the test packages. |
I'm using v3.0.1, alle three packages are in the same schema (ut3test). This is the command I use:
This is the output:
And this is what plsql_profiler_* tells me:
|
This is a very odd behavior. Can you share package spec of the test and tested code as well as the test results of: set serveroutput on
begin
ut.run();
end; Thanks |
Here they are! |
Hello, The issue has been tagged as discussion. I wonder if there's some progress in the discussion. |
Hi @safokkens
Here is what I got:
I cannot reproduce the issue, even using your code. Sorry but I run out of ideas to help you. |
Thank you for your answer. When I look at your output, I see a lot of functions that are not from my test package APP_TOOLING. I think those are your own tests, so I will ignore those (award_bonus, betwn_str, cleanup_temp_tables, insert_dummy_notes, print_crsr, remove_rooms_by_name and test_sess). All coverage that's left are the ones from tst_between_string en tst_hello_world. Exactly the same packages I get when running a coverage report. You reproduced the same behavior! I want to differentiate three kinds of packages:
What I want to see in Sonar is a report of the portion of our software that is tested. This gives me the code coverage. So I want a report over APP_TOOLING. What I get is a report about which portion of TST_BETWEEN_STRING en TST_HELLO_WORLD are run. |
Why is your Another side effect/issue is the fact that packages: |
When I change to:
So again tests are note filtered out, but at least your tests package is there. |
I'm glad we found the origin of the problem!
Could you please explain to me why my suitepath can't have the same name as the package that's tested? This way I want to group all unittests for a specific package. |
This is now getting resolved and will become part of v3.0.2. |
Going back to your question about organizing suites i would rather recommend the approach of keeping 1:1 mapping of test package and tested package.
|
You're welcome! I really like having my tests for a package in one test package, just like utPLSQL v2 did. But because I missed an extra level (context) I split them in multiple packages. Glad to see you are adding an extra level in the suite. I hope this level will appear in the test reports so we know the context of the runned tests. Thanks for your quick reaction and clear answers. I will test the fixes from your branch. |
I tested your branch and now the report works as expected. I hope to see a v3.0.2 soon! Regards, |
On a test database I've created a simple database package (app_tooling) and I'm testing it with two unit test packages (tst_between_string and tst_hello_world).
When running a coverage report (every style) I get the coverage of the two tst-packages, but what I want is the coverage of my software (app_tooling). Could this be a bug, or am I doing something wrong?
When I look at the profiler-tables, I see profiler data for all three packages so the coverage is indeed recorded.
The text was updated successfully, but these errors were encountered: