Cross project clover coverage

We are in the process of refactoring our app into multiple projects.

As we are moving the unit tests to the correct project (including the class file), we are starting to see some classes that used to have coverage from a variety of different tests stop showing any coverage at all once the unit tests are no longer in that project (but are in the same package).

The tests in question are being run (with clover instrumentation) successfully - no failures, no errors. And no code coverage for classes in a different project.

Any idea of why this is happening?

Now, to be clear, up until this time *all* of our unit tests where in a different project from the classes they were testing. This has only started to happen as we move the unit tests into the correct projects (and out of the massive catch basin).

Thanks,

Clark.

1 answer

0 votes

Hi Clark,

you didn't wrote what IDE you were using. I would recommend making a full rebuild, including cleaning of Clover database files after your relocation of files is finished. Eclipse, IDEA and/or Clover could had something left in their caches.

Regards
Marek

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

443 views 2 5
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you