Hi, some feedback about NCrunch 5.1:

In Rider:
The Risk/Progress bar is not working, I can't get it to show.
RDI is showing popup information over wrong object (outlined too much to the left) (See image)

In VS2022/Rider:
This issue might be PEBCAK, but I found it a bit weird how the RDI overlay works when multiple tests cover a line. In the attached link you can see 2 images where there are a bunch of tests that go over a line of code. In the RDI overlay I am unable to select any other 'frame' or 'test', and only the test
where a property is null and skips the logic is shown in the RDI overlay. Only when I select a certain test and pick 'Show coverage for this test only' I see the expected RDI overlay. Is this how it is supposed to work? (See image)


About RDI:
I was wondering if it is possible to 'browse' the complex objects like you can when debugging. It seems like now the majority of my objects I can just see that it is 'an object of that type' without anything else. I don't like the idea of having to add ToString overrides everywhere so I can use the RDI overlay and actually see which objects are where. If it is not possible to for example browse complex objects, maybe it could be an idea to allow usage of the DebuggerDisplay attribute instead of ToString?


On a side note: yesterday for some reason in Rider ncrunch was unuseable, even on a tiny project with perhaps 20 files it took minutes to build and run tests, but that seems fixed now. Not sure what changed on my end (I did upgrade to NCrunch 5.1). I don't think I have any valuable information for why this was slow though.

Some imgur images to show some issues/clarify some questions:
https://imgur.com/a/5JT2Ujj

Hi, thanks for your feedback.



This is planned. We needed to have a feature cut off that would let us release RDI, and proper support for complex types didn't quite make it in. We know how to do it, but it will take some engineering. The plan is to capture the state of complex type instances with their fields/properties, and possibly to span out through small object trees up to a configurable limit. We have capacity limits, so we likely can't capture everything, but we will definitely be doing better than just ToString.

Regarding the images you've posted:

As Michael has mentioned, under Rider we aren't yet properly considering the effect of the parameter names being popped up inside source lines. This messes with our column mapping. VS has an advantage here for the moment because we're able to use the code geometry to place the markers. We're looking at ways we can solve this under Rider.

The source you have in your ordered condition looks like it is executed once for the test you've opened the RDI frame on. Right now in RDI we have two ways to open frames:
1. Opened for just one test (left-click the scope bracket around the coverage markers). The overlay frameset will contain all the times the method was called by the test. The test itself is selected based on which one NCrunch thinks is most important at the time. It will prefer to use the one selected in the Tests Window, otherwise it will default to the first failing test, otherwise it will just get the first test covering the line.
2. Aggregated for ALL covering tests (right-click the scope bracket around the coverage markers). This will show all frames for all the covering tests. Based on your use-case, I think this is probably what you were after in this situation.

It's possible to be more selective about which test the frame is opened for by instead opening the test list by clicking on a coverage marker, then right clicking a test and opening the RDI overlay using the context menu.

As you've discovered, showing coverage for a specific test only is a good way to set the focus of the engine. When you do this, you'll only get frames for that test.

There are plans to allow you to aggregate for selected groups of tests, but we're not there yet.