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).
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.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot