Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. MSTest tests that are inconclusive are still "failing"

    Hi, thanks for sharing this problem. This looks like a compatibility hole. I've just managed to reproduce it myself. I'll see what I can do about getting it fixed. Thanks again for taking the time to report it.

  2. Theory based tests doesn't execute on distributed processing nodes

    [quote=eriove;10569] Adding the invariant culture in the ToString() will really help us. The grid node is in a data center in Norway (where IT sets Norwegian settings) and we share the grid node between between the Swedish and Lithuanian office.[/quote] Will do. You can expect this in the nex…

  3. Color bullets are not updated

    [quote=jotto;10573]Thanks -- seems like that did the trick![/quote] Awesome, thanks for confirming!

  4. Theory based tests doesn't execute on distributed processing nodes

    I'm impressed you've managed to narrow this down as far as you have. What you're observing makes perfect sense. When NCrunch constructs an identifier for a testcase, it performs a .ToString() on the arguments without specifying any culture preference (oops). So if your decimal separator is differ…

  5. Local variables unavailable when debugging

    [quote=eriove;10563]After a couple of restarts of the computer and then it started working. With the latest release (3.9) I've reverted to the files installed by nCrunch and it still works.[/quote] NCrunch v3.9 introduced more structurally correct integration with Xunit2, so I hope we should no l…

  6. nunit TestCase not working with ExpectedResult

    Hi Henrry, Thanks for sending through the sample project. I've tested this at my end and I can confirm that it works with the latest release of NCrunch (v3.9). I believe the problem you are experiencing is due to a compatibility issue that has been fixed in a later release than the one you ar…

  7. Color bullets are not updated

    Thanks for confirming this. This smells very much like cache file corruption. I'd be interested to know if clearing the cache file resolves the issue. You don't need to wait for it to reappear - I'd recommend nuking the cache file immediately.

  8. NUnit Testoutput does not contain Lines Written by TestContext.WriteLine()

    Hi, thanks for sharing this issue. This looks like a potential integration issue. NUnit is probably capturing the text within the TextContext, then outputting this in an area that NCrunch doesn't capture. I've made a note to review the integration to see if it can be resolved. For the time bei…

  9. Framework Utilisation Types missing Xunit v2+

    v3.8 of NCrunch contained a defect where it was not correctly calling .ToString() on the contents of array parameters being used for test cases. This meant that the parameters you were passing in were actually being converted to a different value, which would have had the unintentional side-effect …

  10. Theory based tests doesn't execute on distributed processing nodes

    Hi, thanks for sharing this problem. Could you confirm that you also upgraded the version of the grid node so that it is running v3.9? Also make sure that it isn't loading the xunit module from a prior version. You can check this by inspecting the version stamp of the nCrunch.Module.XUnit2.dll fi…

  11. Framework Utilisation Types missing Xunit v2+

    Thanks for sharing the code sample. This is being caused by a compatibility problem between NCrunch and AutoFixture. The code you're using above uses AutoFixture to generate random test data that is used in test parameters and therefore the physical name of each of the test cases is completely r…

  12. Color bullets are not updated

    Does the pattern seem to be consistent, or intermittent? If you right click on the test and choose to run it individually, does the problem go away for the targeted test? Could you try clearing your NCrunch cache file? This is stored under the _NCrunch_SOLUTIONNAME directory adjacent to your .s…

  13. FileNotFoundException UTFResources

    I really think that something is wrong with the Microsoft.VisualStudio.QualityTools.UnitTestFramework binary that you are using. I wonder if this might be a development version of this file. Was it perhaps taken from an RC branch of VS? It seems very strange that this file is referencing Micros…

  14. FileNotFoundException UTFResources

    Ok, let's try installing the missing assembly into the GAC. Hopefully this will work around the issue. You'll probably need to use an administrator command prompt, and to chase down gacutil if it isn't in your path. Try: gacutil /i "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterpri…

  15. Framework Utilisation Types missing Xunit v2+

    The static analysis code itself has been physically removed. You should be able to confirm this by checking for the existence of the 'Analyse assembly' tasks in the NCrunch Processing Queue. The 'Analyse assembly' task is used to execute dynamic analysis. Are you able to share with me the test …

  16. Framework Utilisation Types missing Xunit v2+

    Hi, thanks for posting. NCrunch v3.9 included significant changes to the Xunit integration. I'll post the details here from the release notes: Significantly restructured NCrunch's integration with Xunit v2. Previously, NCrunch would include the runtime binaries for xunit in its own install…

  17. FileNotFoundException UTFResources

    Thanks for the code sample. I think the environment is highly suspect - the sample worked correctly for me :( Are you able to share the full stack trace of the exception? Something else we can try is to turn on fusion logging and see where/how its looking for the dependency. [url=https://sta…

  18. Color bullets are not updated

    Hi, thanks for sharing this. This looks to me like you have a coverage filter set in your configuration settings. This could be attached to your engine mode, or defined at global/solution level. Can you check [url=http://www.ncrunch.net/documentation/reference_solution-configuration_show-covera…

  19. v3.9.0.1 & Avast

    Hi, thanks for sharing this. Usually AV systems have a way to report false positives. Is there any chance you could ping them and let them know?

  20. VS 2017 and VS SDK

    Hi Micha, Check that there aren't any files being implicitly referenced on a relative path through the build system. If there is a tool that is required by the build tasks that is stored near your project/solution structure, you might need to specifically include it for NCrunch. See here for mo…