Code Coverage Wrong After 2019.2 Update

Completed

dotCover is complaining that "Coverage info for some tests is absent or outdated" after upgrading to dotCover 2019.2.2, and some but not all of my coverage data is missing, before updating it was correct.  I have tried the suggestions on the "dotCover is not showing Code Coverage" page: disabling solution structure matching, PDB files are being generated, and nothing is being filtered out.

This is a multi project solution, and the correct coverage data is being displayed momentarily while other projects in the solution are being tested, however when the final unit test is completed it gets updated with old data from several days ago.

7 comments
Comment actions Permalink

Hello Eric,

Doesn't it help if you cover all tests in the "tests" popup window?

If it doesn't help, please try to 'Drop coverage data' and restart coverage in all your unit test sessions.

0
Comment actions Permalink

Dropping the coverage data fixed the issue.

 

Thanks

0
Comment actions Permalink

I just install dotCover 2019.3.1 and having the save problem as described in original question.  I also have tried the suggestions on the "dotCover is not showing Code Coverage" page: disabling solution structure matching, PDB files are being generated, and nothing is being filtered out.  Then tried deleting coverage data which also did not work.

Any other suggestions?

0
Comment actions Permalink

Unfortunately dropping the coverage data does not always work.

I usually have to do the following:

 

1. Close Visual Studio.

2. Find and delete the following directory c:\Users\<your user name>\AppData\Local\Temp\JetBrains\ReSharperPlatformVs16\vAny_971ac927

3. Start Visual Studio and hopefully it is working.

0
Comment actions Permalink

Same Problem for me in 2019.3.4, Delete Cache as suggested by Ekaterina Solovova did not work. The manually deletion Eric James suggested worked for me. I'm using XUnit.

Regards,

Nicolai

0
Comment actions Permalink

I have the same problem.  I'm running Resharper 2020.3.  Even if I run coverage on a single test, it will tell me the coverage for that test is outdated and I have to rerun it from the test coverage window to get it to update.  If I tell it to run coverage on a single test, it should run coverage on that test immediately.  Yes, if I run it manually from coverage window by clicking on the "tests" link it will run, but why do I have to tell it to run the same test twice?

0
Comment actions Permalink

I have had a similar issue - all was working fine, then had to start with a clean PC (IT dept had to re-image back to Win10), installed VS2019 and dotultimate 2020.3 - Unit test coverage still says "Coverage info for some tests is absent or outdated".

I have deleted coverage data which also did not work.

I have deleted the cache as per Eric James Post this did not work.

Anything else to try ?

 

0

Please sign in to leave a comment.