Forum member

ljohnston

32 posts

Posts by ljohnston

  1. Completely ignoring tests based on category

    This is essentially a request to revisit this past rejected feature request: https://forum.ncrunch.net/yaf_postst1296_Ignore-categories-of-tests.aspx We also have various groups of tests requiring manual configuration or access to specific resources (credentials, an IP, a specific device being on…

    15 Aug 2025 21:55 UTC

  2. With optimized instrumentation generic MSpec behavior fails with "This test was not executed..."

    All our behaviors are behaving as expected now. Thanks!

    22 Apr 2020 22:49 UTC

  3. With optimized instrumentation generic MSpec behavior fails with "This test was not executed..."

    Sorry about the delay, I didn't get a notification for your latest reply (I think I must have viewed the previous one without logging in/using the link from the email). Here's an updated sample (which appears to fail in the same way as the previous one did): [code=csharp] // Everything works as…

    20 Apr 2020 17:51 UTC

  4. With optimized instrumentation generic MSpec behavior fails with "This test was not executed..."

    Hi, Thanks for working on this. This fixed behaviors with one generic argument, but behaviors with two generic arguments are still broken (I haven't tried more than two). This can be reproduced using the code in the original post by changing TestBehavior<T> to TestBehavior<T, U> and passing th…

    08 Apr 2020 16:34 UTC

  5. With optimized instrumentation generic MSpec behavior fails with "This test was not executed..."

    With Instrumentation Mode set to Optimized I'm seeing MSpec behaviors with generic types fail when instrumented with a custom type (though not with .NET types such as Object or String). After changing the instrumentation mode to Legacy everything works as expected. Requirements: Latest Machine.S…

    26 Mar 2020 18:27 UTC

  6. Tests excluded by filter are considered to be ignored by Console tool

    Hey Remco, https://forum.ncrunch.net/yaf_postst2508_Console-tool-and-impacted-tests--failed-tests-becomes-ignored.aspx [quote] Where tests are excluded using the 'Tests to execute automatically' filter, the engine won't queue them for execution. Thus they won't have a result reported by the r…

    09 Apr 2019 16:59 UTC

  7. MSpec test fails intermittently due to state being maintained between runs

    I'm seeing an MSpec test fail intermittently due to what seems like either an MSpec or NCrunch bug. I've simplified the actual test down to this version: [code=csharp] public class test { Establish context = () => { _strings.ShouldBeEmpty(); // This line fails?! _strings =…

    24 Oct 2018 18:48 UTC

  8. NUnit "System.InvalidOperationException: The context has already been initialized"

    Thanks Remco. I will dig in deeper when I have time/depending on how often we see it.

    06 Sep 2018 22:54 UTC

  9. NUnit "System.InvalidOperationException: The context has already been initialized"

    Hey, I searched our code for "Parallelizable" and confirmed the attribute is not present anywhere. Is there anything else I can look into to help troubleshoot this? If there is multi-threaded code interacting somehow I don't think it's within the failing tests themselves, as the second set …

    31 Aug 2018 20:05 UTC

  10. NUnit "System.InvalidOperationException: The context has already been initialized"

    We just saw this again with a completely different set of tests (again all tests in a single file). Here's just the exceptions from the new failure: [code] System.InvalidOperationException: Invalid attempt made to decrement the event's count below zero. at System.Threading.CountdownEvent.…

    28 Aug 2018 22:10 UTC

  11. NUnit "System.InvalidOperationException: The context has already been initialized"

    Hi, We're occasionally seeing the below error failing a build on our CI server running NUnit tests via the console runner. I'm not aware of anybody seeing it running the tests using NCrunch locally. It seems like every test in one file failed, but everything else was fine. I'm not sure if this…

    28 Aug 2018 16:36 UTC

  12. Error message: ERROR (Internal): System.Exception: Failed to extract test from its task

    Hi, I had a build fail with the error message below and would like some help troubleshooting it since it seems to be an internal NCrunch error message. The tests are being run from TeamCity using NCrunch Console v3.18.0.2. Re-running the build fixed the issue, but obviously it would be bett…

    16 Aug 2018 00:00 UTC

  13. Unable to get correct test timings using the Console Tool with TeamCity without duplicated tests

    Thanks for your response and your honesty about when this can be addressed. It works well enough for our purposes for now. It would be great if you could take a look at improving it when things settle down.

    13 Sep 2017 20:29 UTC

  14. Unable to get correct test timings using the Console Tool with TeamCity without duplicated tests

    We're moving from using separate NUnit and MSpec testing steps in TeamCity to using the NCrunch Console Tool, mainly because the MSpec runner does not support running tests in parallel so we get a significant performance increase even taking into account NCrunch doing its own build of the entire pro…

    12 Sep 2017 17:53 UTC

  15. Configuration/UseBuildConfiguration not supported by console tool?

    We're moving to using the console tool to do our CI testing and ran into this as well. We would like to ensure we're building in release configuration for CI but use the default elsewhere. We could (and may) use the workaround you mentioned but it seems odd that this isn't supported. Did you ever lo…

    11 Sep 2017 20:48 UTC

  16. Impact detection does not detect added constructor required by Moq

    Here's another impact detection issue I came across. The way Moq creates mocks may make it difficult/impossible to detect this case but I wanted to make sure you were aware of it regardless. Create a project with Machine.Specifications, Machine.Specifications.Should, and Moq Nuget packages. E…

    16 May 2017 19:48 UTC

  17. "Run impacted tests automatically, other manually" does not detect changes in MSpec tests.

    It works great so far. I'll keep using it and let you know if I run into any issues. I appreciate the fix, the impacted test detection is such a useful feature.

    10 Apr 2017 16:40 UTC

  18. "Run impacted tests automatically, other manually" does not detect changes in MSpec tests.

    No worries, thanks for all your hard work on NCrunch.

    30 Mar 2017 16:06 UTC

  19. "Run impacted tests automatically, other manually" does not detect changes in MSpec tests.

    Any update on this? Impact detection is a great feature especially for our larger solutions but I can't use it if it doesn't detect changes to tests.

    28 Mar 2017 22:57 UTC

  20. "Run impacted tests automatically, other manually" does not detect changes in MSpec tests.

    Thanks Remco. I found some additional evidence that it is caused by the lambdas as you suspect by making the following changes: [code=csharp] public static class SystemUnderTest { private static Func<Int32, Int32, Int32> _adder = (first, second) => first + second; pub…

    23 Jan 2017 23:48 UTC