Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. The NCrunch task process was unexpectedly terminated during Analyze Assembly

    I'm glad to hear this resolved the issue for you. [quote=Marcello;16700] It's not so easy to keep SDK versions synched because in developers' machines, it's updated with Visual Studio updates... I hope you understand this, but I'm not sure you can do something about this, is that so?[/quote] …

    26 Jun 2023 23:52 UTC

  2. The NCrunch task process was unexpectedly terminated during Analyze Assembly

    Hi, thanks for sending through the report. Unfortunately, the report didn't include any detail about the error. Taking another look at the message, this actually makes sense, since it would have occurred on your grid node. I strongly suspect this issue is caused by an SDK missing on the node.…

    26 Jun 2023 09:18 UTC

  3. Support for central Package Management & Simplified output path

    Hi Manuel, Thanks for getting these features on our radar. Looking at the description of them and inferring how they must function under the hood, I think it's a safe bet that we'll need to do some work on NCrunch before we are able to support these features. For the time being, please cons…

    25 Jun 2023 04:57 UTC

  4. Two Bug Reports concerning Specflow

    I've taken a close look at the impacted tests not being run issue. This issue appears because of the mechanics involved. SpecFlow is using reflection to identify the step definitions referenced by the feature files. If the step definitions don't exist, the reflection call does not return it for…

    25 Jun 2023 00:28 UTC

  5. Two Bug Reports concerning Specflow

    Thanks for these extra details. I'll take a look at this problem over the coming week and will update you with what I find. Can you confirm for me whether these issues are new for you, or whether they may have existed for a while?

    24 Jun 2023 00:03 UTC

  6. The NCrunch task process was unexpectedly terminated during Analyze Assembly

    Hi, thanks for sharing this issue. Usually, this is caused by critical assembly resolution issues in the analysis environment. Would you be able to submit a bug report after you've had this happen to you? Usually the report will contain more detail about the problem.

    24 Jun 2023 00:00 UTC

  7. Two Bug Reports concerning Specflow

    Hi, thanks for sharing these issues. I would need to see the exact steps and code involved to be certain, but I suspect that with this particular scenario you've hit an edge case where the impact detection doesn't work reliably. Impact detection works by performing hash comparisons between ver…

    23 Jun 2023 13:12 UTC

  8. Cannot run due to Import in C# Project file

    Thanks for sharing this problem. I've managed to squeeze a fix for this in the version of NCrunch released today (v4.17). Could you give it a try and let me know if this solves the problem for you?

    23 Jun 2023 02:15 UTC

  9. Grid nodes are requiring latest version of the SDK

    [quote=samholder;16678] So that implies that if the console tool machine is not updated then the grid nodes should not need updating? [/quote] In theory, yes. If they all stay on the same version, all should work fine. [quote=samholder;16678] Interestingly I updated the grid nodes first an…

    19 Jun 2023 13:59 UTC

  10. Grid nodes are requiring latest version of the SDK

    Hi, thanks for sharing this issue. The grid node will always try to use the version of .NET that matches that of the NCrunch client (which in this case is the console tool). As such, when .NET is updated on the client machine, it also needs to be updated on any grid nodes that service this cli…

    19 Jun 2023 12:28 UTC

  11. Dependency tests with NetArchTest failing

    [quote=talbrecht;16672] I've always thought that NCrunch enhances the code for testing with NCrunch somehow, e.g. for tracking code lines hit by tests. Therefore the added code must reference NCrunch and breaks your NetArchTest test code which looks at the referenced assemblies during test executio…

    12 Jun 2023 12:33 UTC

  12. Insufficient granularity of test results

    Hi, thanks for posting. The issue you've encountered here is due to technical constraints. The tests are discovered in a different environment to the one they are executed in, which results in the need for the test parameters to be serialized between domains. This creates consistency problems w…

    08 Jun 2023 08:28 UTC

  13. What is "Log Summary" window for?

    [quote=GreenMoose;16668][v4.14.0.7] In "NCrunch tests" we have Trace Output (e.g. console output), Execution Steps, Log Summary and Hot Spots. For my tests the "Log Summary" is empty. What is it supposed to show? Thanks.[/quote] Sorry - this isn't supposed to be showing yet. It's still …

    31 May 2023 19:48 UTC

  14. DataRow issue with MSTest 3

    [quote=jschreuder;16665]Looks like another change here broke your test discovery (v3.0.3)[/quote] Thanks for the heads up on this. I'll check it out. Dynamic analysis should hopefully be a workaround for the time being.

    29 May 2023 08:27 UTC

  15. Dependency tests with NetArchTest failing

    Can you confirm the exceptions you're seeing? Are these assembly resolution issues? If so, is there a specific assembly they are having trouble resolving?

    25 May 2023 00:16 UTC

  16. Dependency tests with NetArchTest failing

    [quote=gwholdom;16661] I have both [Pre-load all assembly references into test environment] and [Copy referenced assemblies to workspace] set to true but still no dice. [/quote] Sorry for the confusion ... I just want to confirm. Does NCrunch not work when the 'Copy referenced assemblies to wo…

    23 May 2023 08:33 UTC

  17. Dependency tests with NetArchTest failing

    Hi Grant, Thanks for sharing this issue. Looking at this particular framework and from what you've described, my expectation here is that the framework is taking responsibility for its own assembly loading, and as such would be fundamentally incompatible with NCrunch's optimisations. It mig…

    23 May 2023 05:15 UTC

  18. Tests discovery uses ALL memory available, without running tests

    Thanks for these extra details. I think this was caused by some kind of display issue. It may be related to the saved UI layouts in the config files. If the problem is no longer bothering you, I'm happy to leave this be unless it appears for you again.

    16 May 2023 12:24 UTC

  19. Tests discovery uses ALL memory available, without running tests

    Hi, thanks for sharing this issue. Can you confirm which physical process is responsible for the memory overrun? Task manager tends to aggregate memory usage for the entire tree, but there are many processes involved in an NCrunch session. If you expand the tree, it should be possible to see wh…

    15 May 2023 23:24 UTC

  20. Using NCrunch to test Blazor WASM using BUnit

    Hi Jim, Thanks for opening up the sample project. I'm not sure if the sample project is fully representative of the project you're working in, but the source of the problem appears to be in your NCrunch configuration. The primary project has the 'Ignore this project completely' configuration …

    15 May 2023 00:42 UTC