[v5.6.0.1]
Given I have filtered test coverage, Is NCrunch Hot Spots supposed to update between test runs or not?
Repro:
1. Run test1 in a new process.
2. Show code coverage only for that test, notice window "Ncrunch Hot Spots" is reflecting this filtered coverage.
3. Run same test again within existing test process, coverage markers are updating but NCrunch hot spots is not updating.
Expected: Hot spots to update automatically similar to the coverage markers
Actual: Hot spots only updates when I run "show coverage for covering tests only".
Scenario:
While focusing on 1 test while developing, I want to see the hotspots so I catch bottle necks early in process.
Now the work process is something like "show coverage for test1" -> <hot spots updating> -> "alter code" -> <test executing in new process> -> "run test in existing process" -> <test executing in existing process> -> "show coverage for covering tests only" -> <hot spots updating>.
Thanks.
Daily Usage Issues
NCrunch Hot Spots not updating when coverage filter is active
Started by GreenMoose on 1,202 views
Remco NCrunch Developer
#17629
01 Oct 2024 12:02 UTC
The hot spots window is the only window in the NCrunch UI that doesn't automatically update itself as the underlying data changes. It's the only part of the UI that has a Refresh button.
We didn't really want it to be like this, but it's a very expensive view to create, and updating it in real time risks sending the engine's core thread out to lunch while the window is open.
So unfortunately for this workflow, you'll need an extra button click to get the latest data on screen.
We didn't really want it to be like this, but it's a very expensive view to create, and updating it in real time risks sending the engine's core thread out to lunch while the window is open.
So unfortunately for this workflow, you'll need an extra button click to get the latest data on screen.
Post a reply
Log in to reply.