Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. MSpec Tags are ignored with custom build engine.

    Hi! The first thing to check is whether or not NCrunch has detected the categories that you've assigned to the tests. In the Tests Window, right click the column headers and select the 'Field Chooser'. Drag the category field into the Tests Window. This field should show any category that NCru…

  2. Projects won't build

    Welcome! Thanks for your patience in sticking through this. It seems to me that you have some very complex environments (at least from an NCrunch perspective), which do tend to make an NCrunch implementation challenging .. but it is also very rewarding. You are helping to make NCrunch a better an…

  3. Getting build errors after a delay - project builds and runs fine

    Hi Jay, Thanks for getting back to me on this. Modifying the project file in its original solution location is something I'm not sure if I want to tangle with - as so far NCrunch has managed to avoid any situation where it actually manipulates your original source code. I might have a bit of a …

  4. Test fails without error message

    There's a lot going on in this solution. I'm wondering if the fix you found in the other thread related to DLLs being referenced in the Bin\Debug directories may have also had an impact on this. Can you let me know if it happens again now that you've solved the other issue? I'm hoping that this p…

  5. Test fails without error message

    Which files were they that you had locked and how were they locked?

  6. Projects won't build

    Great to hear! Yes, I agree that this should be made MUCH more obvious. Normally this kind of behaviour doesn't create obscure problems like you've described above, but I think it would be better to warn people when this happens. NCrunch already tracks direct DLL references to outputs from projec…

  7. Pricing

    Hi Dadhi, Sorry, but if I were to offer licenses at the price of $120 this would be extremely unfair to those that have paid full price for their licenses and are supporting the product. I'm sorry if the licenses are too expensive for you, but this is the price. Thanks for your constructive com…

  8. Disabled tests should not use black icon

    Thanks Ollie, I'll see what I can do.

  9. Disabled tests should not use black icon

    Thanks Ollie - this does make sense, and actually it is a common problem, as it is easy to ignore tests by accident and not realise why NCrunch isn't executing them. What would you think about perhaps a change in the symbol describing the first line of the test? A different colour is probably ov…

  10. Exceptions appear twice

    It looks as though this problem can be broadly reproduced. I'll see what I can do about fixing it in the upcoming minor release. Thanks again!

  11. Exceptions appear twice

    Thanks for reporting this. Do you experience this in every Xunit solution you work in, or just this one?

  12. Test fails without error message

    Is this the same solution that you've been experiencing intermittent xunit.dll build issues with? The bug report shows NCrunch is failing to map the coverage data derived from the workspace, which suggests this may be a symptom of the same problem causing the xunit.dll build issue.

  13. Projects won't build

    The .sln and .csproj files would certainly help. There may not be anything specific in the solution that changes itself - this can also be caused by the files NCrunch is referencing within the solution and whether these files are derived or not. For example, if the xunit.dll file is being referenc…

  14. Disabled tests should not use black icon

    Hi Ollie - Thanks for posting! Ignored tests under NCrunch are completely ignored in every way. They are not executed at any stage by NCrunch, and any data associated with them is thrown away as soon as they are ignored. To have an ignored test storing coverage state (i.e. as different colou…

  15. Projects won't build

    There are two things that jump into my mind when thinking about this problem: 1. Your build is (temporarily?) changing the state of your solution in a way that confuses NCrunch 2. You have a workspace isolation problem After NCrunch has completed an entire cycle (and is sitting idle), what ha…

  16. DeploymentItem results are inconsistent

    Great to hear that you found a solution. NCrunch is modelled from the behaviour of MSTest (not Resharper), so there may be some differences here in the way it works. Another approach I often recommend to people is to reference test resource files outside the MS Test sandbox (i.e. not using deplo…

  17. Xunit Theory and Code Coverage Markers

    For an Xunit theory, this is quite possible. Also have a read of the difference between Logical and Physical code coverage, as depending upon the nature of your code, this may also have an impact on your code coverage.

  18. Test fails without error message

    Is the 'include static references in workspace' configuration setting disabled? Other than absolute file path references, this is the only way that it can be possible to have locking problems between VS and NCrunch. If you have this setting disabled for any of your projects, try turning it on - th…

  19. Test fails without error message

    Is it the same test that is failing consistently? Does it also fail if you run it directly via the UI (via clicking the 'run' option on the tests window)? Is there anything you would consider to be unique about the structure of this test?

  20. Pricing

    Hi Wise, Sorry but this is the pricing for NCrunch. There are no plans to change the pricing tiers. Indeed, it is very common in this industry to have different tiers for different classes of user. If the price is too high for you, then maybe this is not the product for you.