Resolved Prevent Code Coverage from opening Explorer *every time tests run* ?!

I started using Code Coverage 1.0.1 with Unity 2021.3.1.

Every time I run any test it opens another Explorer window!

I tried playing with the settings. With "Auto Generate Report" unchecked there is no Explorer window opened, but the report is also not being updated as indicated by "Generated on" timestamp (as well as additional tests by adding/removing code).

So I'm left with CC either being super-annoying, or disabled. Is there any way I can force it to generate reports WITHOUT opening a new Explorer window every time?

 

GOT IT!

The internal class CoverageSettings has a flag revealReportInFinder that defaults to true. That flag doesn't have a corresponding setting in CodeCoverageWindow, therefore it is always true.

I had to copy the package contents into the project to change that flag to false. Now I get reports without being annoyed, what a relief.

 

Btw I keep getting oddly uncovered lines, like completely illogical. It tells me I haven't tested a method, but the method body is fully tested, things like that.

For example:

 

Or this one:


Even without the line break in the constructor arguments I get empty lines marked as "not covered".

 

Okay, it's working better now. I upgraded to CC 1.1.1 but that didn't work. I went back to 1.0.1 and cleared Data and History. Now I get all the lines highlighted correctly (100% coverage) and [ExcludeFromCoverage] also works correctly.

 

By „refocus“ you mean the window pops up in front? That‘s essentially the same issue. I‘m running a test means I‘m working with the Unity editor. I don‘t need to look at an Explorer window after the test, nor do I need to look at the coverage results after every test. There is already a flag in CC settings that controls this behaviour but it isn‘t editable in the CC settings window (CC 1.0.1). Adding that would fix the issue.

Once the CC html is open in the browser there‘s really no need to look at the CC results in the filesystem.

I haven‘t tried making a build. Are you saying that in order to get full coverage results (ie „in sync“) I need to make builds? I‘ll certainly give that a try. I thought that just running the tests suffices, and adding more code to a class while also adding a test for the new code should „cover“ it.

PS: The fact that it opens new Explorer windows every time on my machine could be due to me using Directory Opus as the default explorer handler. I can imagine this could cause the „is that window already open?“ check to fail. Regardless, whether it‘s a new window, or the same, it pops up. That‘s focus stealing behaviour.

 

I'm on a MacBook now and can confirm that if there was already a Finder window opened, the existing one is refocused.

Nevertheless annoying since every time I run a test Unity editor loses focus, and if I wanted to see Coverage results I would simply switch to the Browser.

 

Cool, thanks for letting me know!