Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Enable NCrunch menu option is disabled

    Hi Calvin - I'm wondering if you might be able to try downloading the latest version of NCrunch for VS11. Shortly after 1.38b was released, this problem was reported and I put up a new build revision with a fix for it ... it's quite possible that you were in the early batch of people to download…

    26 Mar 2012 21:22 UTC

  2. Navigate previous/next broken test using keyboard shortcuts

    Hi Ylee - I've been thinking a bit about this feature, particularly the navigation one. The interesting question around this is what should be considered a failure point. Naturally NCrunch has information on both build failures and test failures, and the navigation to a failing test could be …

    24 Mar 2012 21:32 UTC

  3. Enable NCrunch menu option is disabled

    Hi Calvin, Thanks for posting! I've had a look through the bug report you sent through, and it appears like an initialisation problem of some kind. Are you able to let me know which version of Visual Studio you are using? Also, does the problem occur if you open your solution directly from…

    24 Mar 2012 03:25 UTC

  4. Don't Build/Run when editing .js files

    Hi Douglas, Thanks for posting! NCrunch will automatically run a build as soon as any change is made to a file that is part of the solution. This is intentional behaviour as NCrunch needs to keep its workspaces updated and it can only be prevented by disabling NCrunch. As for your tests, it so…

    24 Mar 2012 03:19 UTC

  5. Integration with SpecFlow

    Hi, thanks for posting! NCrunch doesn't have any special code or integration with SpecFlow, though as you've described it does recognise the NUnit tests that specflow generates. Because NCrunch isn't aware of the custom tool, it will simply kick off tests whenever a change is made to one of the …

    21 Mar 2012 20:57 UTC

  6. Test Using DeployItem attribute throw errors

    If all is working correctly, you should see the files in both your NCrunch workspace and in the MSTest workspace (the 'Out' directory). If you set your 'log verbosity' to detailed (NCrunch global configuration), then clicking on the test task in the processing queue should give you detailed infor…

    20 Mar 2012 21:42 UTC

  7. v1.37b failing to build project that v1.26 did

    Thanks, this makes good sense. I'll see what I can do about implementing a fix.

    20 Mar 2012 21:40 UTC

  8. xUnit tests with FSharp are not recognized

    Thanks. I'll take a look at it and will see what I can do :)

    20 Mar 2012 21:39 UTC

  9. Stalling at: Running (First time run)

    Hi, thanks for posting! This is a rare problem that is caused by something in the security configuration of your workstation/user account. You may also find that other libraries or tools that you use could exhibit similar problems. Have a look at [url](- BROKEN LINK -)[/url] for more informatio…

    20 Mar 2012 21:38 UTC

  10. Test Using DeployItem attribute throw errors

    Hi, thanks for posting! NCrunch does support the DeploymentItem attribute, though it needs to be used in combination with the 'additional files to include' or while including the test resources in your project file. So basically, you need to do both of the above things you mentioned to make this…

    20 Mar 2012 21:30 UTC

  11. xUnit tests with FSharp are not recognized

    Hi, Thanks for reporting this. Does it make any difference if you set your 'Framework utilisation type' for XUnit/Gallio to 'DynamicAnalysis' for this solution?

    20 Mar 2012 09:16 UTC

  12. no stack traces when test fails

    Would you be able to submit a bug report after the error happens? I'll then be able to take a look at the log file this sends through.

    19 Mar 2012 22:25 UTC

  13. v1.37b failing to build project that v1.26 did

    It looks to me as though you have a derivative of NUnit.Framework.CategoryAttribute that takes an integer value in its constructor? What happens if you change your 'Framework utilisation type for NUnit' NCrunch solution setting to 'UseDynamicAnalysis' ?

    19 Mar 2012 20:50 UTC

  14. Failure reading resource file

    Excellent thanks! Hopefully others will also find this useful :)

    19 Mar 2012 20:41 UTC

  15. Test category not working with MSTest

    It's already there :) You can create a custom engine mode that will exclude tests from automatically execution by their category - [url]https://www.ncrunch.net/documentation/concepts_engine-modes[/url]

    19 Mar 2012 20:40 UTC

  16. Move coverage markers slightly to avoid conflicts with R# jewels

    Thanks! Your feedback is very welcome. The way I prioritise features takes a range of factors into account, but generally speaking when more people request a feature it does go much higher on the list. Most of the constraints are usually around performance and stability, as these are very easy to…

    19 Mar 2012 20:36 UTC

  17. System.InvalidProgramException: Common Language Runtime detected an invalid program

    I've just tonight heard from TypeMock that they have a new version out with a fix for the above. Hopefully this will solve the issue! Cheers, Remco

    19 Mar 2012 09:08 UTC

  18. Extension methods not present when debugging

    Hi, This is interesting. NCrunch does do some wizardry in order to build your test/debug environment inside its workspace, so I'm wondering if something here may be messing up the resolution in the debugger. Does the ToList() extension method work if you try it inside the immediate window?

    19 Mar 2012 08:34 UTC

  19. no stack traces when test fails

    Hi, thanks for coming back to this! My suspicion is that there is something in your test environment that is causing the test runner to bomb out. The easiest way to identify the cause of this problem is to turn on the logging in NCrunch. You should find a setting to control this under your NCrunc…

    19 Mar 2012 08:33 UTC

  20. Nested xUnit tests ignored

    Hi Larsw - The cause of this problem sits between the integration with Gallio and Xunit - it isn't actually part of NCrunch. Sadly this means that the most effective way to fix the problem would be to introduce an integration point directly between NCrunch and Xunit, which would require quite a …

    19 Mar 2012 08:30 UTC