Skip to content
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

Previous coverage report displayed after all objects dropped. #562

Closed
OsBlaineOra opened this issue Jan 24, 2018 · 1 comment
Closed

Previous coverage report displayed after all objects dropped. #562

OsBlaineOra opened this issue Jan 24, 2018 · 1 comment
Labels
Milestone

Comments

@OsBlaineOra
Copy link
Contributor

@OsBlaineOra OsBlaineOra commented Jan 24, 2018

Database: Cloud database 12c.
utPLSQL: v3.0.4

Starting with a new schema.

  1. Create one or more objects (func, proc or package)
  2. exec ut.run(ut_coveralls_reporter());
  3. A coverage report is generated.
  4. Drop all non-test objects.
  5. exec ut.run(ut_coveralls_reporter());

The report from step 3 is returned even though the covered objects have all been dropped.

Side note: I don't think it's related but, I do have one test package that tests a function in a different schema. It's not related to the objects above and doesn't seem to affect the report.

@jgebal jgebal added the bug label Jan 24, 2018
@jgebal jgebal added this to the v3.0.5 milestone Jan 24, 2018
@jgebal
Copy link
Member

@jgebal jgebal commented Jan 24, 2018

We need to add call to ut_coverage_helper.cleanup_tmp_table in ut_runner.finish_run

jgebal added a commit that referenced this issue Jan 30, 2018
@jgebal jgebal closed this in #567 Jan 30, 2018
@jgebal jgebal modified the milestones: v3.0.5, v3.1.0 Feb 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants