Forum member

jarlelin

4 posts

Posts by jarlelin

  1. Bug with combination of catch-when and params arguments

    I tried to reproduce it in a new solution and couldn't. Not until I turned ON "Instrunment assembly outbut", but OFF "Analyse line execution times". So with those settings changed I managed to reproduce the failure of the last test in my example in a completely fresh solution on windows 10 under …

  2. Bug with combination of catch-when and params arguments

    Using ncrunch-specific code suppression comments is not going to cut it I'm afraid. The projects are running .NET 4.6.1, but I tried a couple more just to check. I'm running windows 10 (Ent). I'm afraid I won't be able to easily test this on other OSes.

  3. Bug with combination of catch-when and params arguments

    I'm running nCrunch 2.23.0.2 with Visual Studio 2015 Update 3 and using NUnit for my testing needs.

  4. Bug with combination of catch-when and params arguments

    I was getting the "System.InvalidProgramException : Common Language Runtime detected an invalid program" in some of my tests when running ncrunch, but I don't get that problem when using other test runners. Disabling "Instrument Output Assembly" works and the tests run, but I lose my code cover…