Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. "Risk/Progress" - distinction beetwen "failed this run" and "failed last run"

    Yes - this is true. One way I'm thinking about trying to make this more obvious would be to have a different shade of red for situations where the number contains failing tests that are not current. Do you think this would work for you? Or do you have any other ideas?

  2. Add Pin/Unpin tests on assembly level

    This seems like a reasonable request - and it would work well with the tests window structure. I'll see what I can do.

  3. Cannot build VB.Net projects. Get error vbc, NCRUNCH; ^^ ^^ ' is not valid: Character is not valid.

    Hi Graham, Thanks for posting and I'm glad you like the tool :) I've done some more digging and I've managed to find a workaround for using DefineConstants on VB.NET projects. Depending upon the number of projects in your solution, there may be some effort involved. Basically, NCrunch is m…

  4. Results/ Coverage reporting

    Thanks for posting your thoughts on this. The ability to report code coverage stats is one of the most single requested features on this forum, so you can bet it will be happening in a future release :)

  5. "Build in progress" for extended periods?

    I was originally thinking to push 1.38b out around the middle of next month, but I may need to bring the release forward as this is quite a serious issue. I'll keep you posted.

  6. Recursive code being edited can sometimes cause NCrunch workers to die horriffically.

    Agreed. This is hard to fix because the CLR behaviour is to always terminate a process when it hits a stack overflow - there's no way to handle this exception. You'll notice other test runners behave the same way. I have some loose plans that may improve the experience around this in a later re…

  7. "Build in progress" for extended periods?

    Hi Jon - I've been getting this problem roughly once per day while working locally in the NCrunch solution, and I've narrowed it down to the code causing the problem. Thanks for your help in highlighting the issue, you can be sure I'll have a fix for it in 1.38b :) Cheers, Remco

  8. csproj imports

    Hi, thanks for posting about these issues. The postsharp problem is caused by a build dependency on a binary file that NCrunch isn't aware of. Right now NCrunch doesn't recognise the "UsingTask" MSBuild tag, so even though it is likely picking up the .targets import without problems, it isn't aw…

  9. "Build in progress" for extended periods?

    If there's an out of memory exception, then you're sure to get an explosion. If your system hangs with a build in progress, it's worth checking what's happening in the processing queue. If the queue itself doesn't show any data (or doesn't refresh), then this is the same issue shown above. If the…

  10. ETA of MSTest data driven tests?

    Hi John - Thanks for the suggestion. My original plan was to integrate with MSTest using Gallio, though I gave up after considerable effort when I found that the MSTest engine just didn't have enough hook points for NCrunch to work its magic. The problem isn't Gallio - it's MSTest :( Cheer…

  11. Code coverage for MVC app with IISExpress

    Hi Darren, Thanks for posting! At the moment, NCrunch isn't capable of analysing execution across multiple processes - though this is on the roadmap for releases further down the line :) Cheers, Remco

  12. New feature (cosmetical) request

    The hit boxes are deliberately made to be consistent across the marker types, so that the vertical line can still be easily selected. Is it only the X that you have trouble with? Are the other lines ok?

  13. v1.37b - Debug variables

    Thanks - I was having problems with reproducing this. This little piece of information is very helpful to me :)

  14. Add NCrunch.Framework to NuGet

    You are absolutely correct. And giving more space for people to create version inconsistencies will only make this worse... It may be the best solution would be to make the NCrunch.Framework code a bit smarter so that it can warn about version inconsistencies. I'll have a think about it.

  15. XUnit Assert.Equal message missing diagnostic info

    Thanks for reporting this. I'll take a look and will see what I can do.

  16. Minor display and mouse issues (high DPI settings)

    Hi Ylee, Thanks for reporting these - neither were on my radar. I'll see what I can do about getting them fixed. Cheers, Remco

  17. NCrunch Risk/Progress status as in NCrunch Tests

    Thanks for posting :) I have big plans in this area ... likely won't make it for 1.38, but it isn't far away :)

  18. NCrunch crashes when enabled

    Unfortunately it's the first time anyone has reported NCrunch failing at this particular point, so the log file isn't very verbose around the file that's actually causing the problem. From the stack trace I can establish that it's a reference to a non-code file that's written into the .proj file. …

  19. Add NCrunch.Framework to NuGet

    Hi Rory, Thanks for posting! I've been considering placing this DLL under nuget. My main concern is that it needs to be versioned alongside the installation of NCrunch consuming it, otherwise many of the features activated by it may not actually work. I'm glad your enjoying the tool :)

  20. "Build in progress" for extended periods?

    I've noticed this over the last week happening for me also. I did some investigation and it looks as though this is caused by a performance problem when making a large number of changes to a large source file. Basically, the individual changes (keystrokes) are bombarding the backend engine to wo…