Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. File not found exception

    Hi, Yes, your assumption is correct. NCrunch should normally identify the file as being a part of the project, and copy it to the workspace so that the tests can run as usual. It's possible that the markup being used to include this xml file in the .proj isn't being recognised by NCrunch and …

  2. Liveness extended with enabled timing

    It's taken a while, but I've finally managed to get to the bottom of this issue after unintentionally reproducing it. It seems that the .NET 4.5 installer introduces a subtle change in the garbage collection behaviour of the CLR, which affects not only .NET 4.5 but also other installed versions o…

  3. vbc.exe issue on build

    What happens if you try running MSBuild.exe directly against the project as it exists in its original project directory? (i.e. outside the workspace). Do you receive the error when you do this? Is this a project that you're able to share in any capacity? I can probably be of much more help if I…

  4. MbUnit SetUp method not being run when it is an override and base also marked SetUp

    Thanks. I have a feeling that this issue may be related to cross-assembly resolution during test discovery (which is something that NCrunch does handle slightly differently to other test runners). It would be great to hear if moving the base class makes any difference for you.

  5. Could not load file or assembly error, unittest project not build

    Thanks, glad you managed to work it out! And nice going for removing the private accessors. They are problematic for reasons far beyond NCrunch.

  6. Unimplemented tests in MSpec treated as failed

    Hi Jeff - There are conflicting views on what should be the correct behaviour of NCrunch in this specific situation. A [url=http://forum.ncrunch.net/yaf_postst255_MSpec-empty-tests-should-be-reported-as-FAILED-not-PASSED.aspx]previous forum thread[/url] should hopefully provide some more details…

  7. Excessive shadow copies of solution assemblies

    Hi Bob, Thanks for posting! This is definitely not normal behaviour. There have been reports of an intermittent issue that can result in DLLs being somehow built or copied to the root directory of a solution or project directories underneath it, but this is the first time I've heard it landing …

  8. Go to selected test doesn't work for MSpec

    Hi Jeff, Thanks for posting! Do you experience this problem with all tests? Does it also happen for other test frameworks on your system? Also, does it appear to be specific to any one solution, or all solutions you use NCrunch on?

  9. Issue with NUnit SetUpFixtureAttribute

    Hi, thanks for posting! Up until now, I haven't heard reports of this problem resurfacing. Can you provide any details of how you are using SetupFixture? Note that NCrunch will never show code coverage inside the SetupFixture code as it has no active test to associate them with.

  10. vbc.exe issue on build

    Hi, thanks for posting! This is the first time I've seen this issue reported, and the error message does appear most unhelpful. Are you making use of any build customisations or 3rd party frameworks that may interface with your build process? Something that may be worth trying is to attempt t…

  11. Could not load file or assembly error, unittest project not build

    Hi, thanks for posting! I wish I could give you a better solution than needing to enable the 'Copy referenced assemblies to workspace' option (which you've already discovered), but unfortunately there is a very solid technical limitation around the way that MSTest accessors work during the build …

  12. Tests with custom ExpectedException attribute are failing

    Sorry, but right now it doesn't look likely that support for custom ExpectedException attributes will be added in the near future. Very few users make use of these, and the effort required to reliably implement them is considerable (they are very tightly integrated in the MSTest framework). I wish…

  13. Path.GetFullPath not returning consistently with MsTest or resharper test runners

    Thanks. This suggests that NCrunch is setting the AppDomain base directory correctly, though the question is how this is not being recognised by your existing code. Would you be able to share any of the code you're using to identify the working directory of the test? My original thoughts were t…

  14. Just Installed, All Test Markers Stay Black. No Testing

    Thanks for trying this. Can you share any details about the setup you're running? Which test framework are you using? Do you have an existing test runner that you make use of right now? Beyond this, the next thing we need to do is to identify whether this issue is specific to the solution you'…

  15. Path.GetFullPath not returning consistently with MsTest or resharper test runners

    Hi Johan, NCrunch should normally set the AppDomain.CurrentDomain.BaseDirectory to be equal to the build output directory. Can you try the following test with NCrunch and let me know of the result that it gives you? Thanks! [code=csharp]using System; using System.IO; using Microsoft.Visual…

  16. nCrunch.TestHost.x86.exe has stopped working

    Hi Mark - Thanks for taking the time to share this issue. Stack overflows are a serious problem for continuous testing as the .NET framework itself treats them as a catastrophic failure that results in immediate termination of the test runner process. The default behaviour of the .NET framework…

  17. Unusual behaviour messages..

    Hi Tom, This is effectively a catch-all warning that appears when NCrunch notices abnormalities in the resolution of assembly references inside the test domain. The code that raises this warning works by inspecting the file paths of the assemblies that exist in the test domain after tests have f…

  18. DeploymentItem with Environment Variable not working

    Hi, thanks for posting! It's true that NCrunch currently doesn't parse environment variables specified in the DeploymentItem. Thanks for making me aware of this issue, I'll note it down for a fix in a future revision. Cheers, Remco

  19. Tests with custom ExpectedException attribute are failing

    Hi Vlad, Thanks for posting! NCrunch uses its own custom-built test runner to execute MSTest tests, and at the moment this test runner does not support custom ExpectedException attributes. Where working with tests that require this behaviour in NCrunch, I recommend introducing the exception f…

  20. Inscrutable build error

    Thanks. If you manage to create a smaller shareable reproduction of the issue, please do let me know.