Forum member

samholder

100 posts

Posts by samholder

  1. IndexOutOfRange exception when running project on build server

    Hi. We have a project which when we build on TC throws: [16:43:11][Step 17/27] NCrunch build: PolicyLine.Definition.Tests.Specifications [16:43:11][Step 17/27] [Core-101] ERROR (Internal): System.IndexOutOfRangeException: Index was outside the bounds of the array. [16:43:11][Step 17/27] [Cor…

    18 Sep 2019 08:03 UTC

  2. How are tests scheduled on the Grid Nodes?

    I'd like a bit of insight into how NCrunch goes about queuing up tests on the grid nodes as I'm seeing some behaviour which is undesired and I'm wondering what my options are for mitigating it. Setup: 3 grid nodes, each running UI tests of a windows app with embedded web components. Each node …

    04 Dec 2018 14:46 UTC

  3. Re-run specific tests

    I solved this problem by collecting the failed tests via the TC HTTP API in a powershell script and then parsing out the names and creating a piece of text which matches NCrunchs definition for running specific tests like so: (FullNameMatchesRegex 'failed test 1' OR FullNameMatchesRegex 'failed t…

    04 Dec 2018 14:30 UTC

  4. Extra tests reported in TC.

    When we run the tests in TC (we use console tool and grid nodes to run the tests) we get extra tests reported, which seem to be the test fixture. We use specflow with MSTest to run the tests. an example will be InsurerAddOnsFeature. _​Fixture_​ (Cashmere.UI.Specifications.Testing:Cashmere.UI.Sp…

    24 Nov 2018 00:30 UTC

  5. Re-run specific tests

    Hey Remco, thanks for the quick reply as ever. I had considered this after playing with the Engine mode options a bit, but its not 100% clear to me which cache file will be in play here. The Ncrunch console tool gets invoked on the TC build agent. This is done with 0 threads, so the tests can't be r…

    23 Nov 2018 23:18 UTC

  6. Re-run specific tests

    Hi. We have some UI tests which we are running on grid nodes. The build runs a particular engine mode which runs tests in a specific category. This is working ok, but sometimes the tests fail for some random reasons, mainly due to selenium/UI testing infrastructure intermittent issues. I'd li…

    23 Nov 2018 12:36 UTC

  7. Tests don't run on the grid from TC after upgrade

    So rebooting the machine seems to cured the ills. Not sure what was going on

    12 Sep 2018 14:55 UTC

  8. Tests don't run on the grid from TC after upgrade

    Enabling verbose logging doesn't tell me what the build issue is on the failing servers. The HTML reports say that building was successful (it only seems to report from the one successful node). The errors/warnings tab doesn't have anything in it. it looks like ss far as its concerned everything …

    12 Sep 2018 13:11 UTC

  9. Tests don't run on the grid from TC after upgrade

    So there seems to be some issue still. Firstly although it claimed to have connected to 3 grid nodes, it only ever gave tests to one of them. secondly although it ran all the tests successfully it reported the build as failed. This was in the logs at the start: [21:50:39][Step 16/25] [Co…

    11 Sep 2018 21:52 UTC

  10. Tests don't run on the grid from TC after upgrade

    Ah, think I figured this out. when I looked at the overall build (and not just focussing on the build log), it said > The NCrunchCacheStoragePath must be set when using the console tool. and adding this to the config seems to have made it happy again.

    11 Sep 2018 20:53 UTC

  11. Tests don't run on the grid from TC after upgrade

    I've just upgraded all our grid nodes from 3.09 to 3.20. I also updated all corresponding console tools on the TC build agents. I updated the licence on the console tools. When I run the builds which should use the grid nodes I get this output in the TC build log: [20:53:18][Step 16/25] [Initi…

    11 Sep 2018 20:09 UTC

  12. How to determine what is causing NCrunch to die?

    it was indeed a StackOverflowException and it happened under some circumstances in the running of the app, which lead us to identifying it, and this fixed the tests Thanks for the help

    04 Jul 2018 15:11 UTC

  13. How to determine what is causing NCrunch to die?

    we have some tests that have started failing randomly on the grid nodes (and occasionally locally) with this: NCrunch was unable to retrieve a meaningful result from this test looking around it seems that something is happening to cause the NCRunch process to die, and indeed locally when it ha…

    02 Jul 2018 15:38 UTC

  14. Tests returning error 5 after upgrade, can we suppress this?

    Hi, We recently upgraded for an old v2 version to v 3.9 for our console tool. Now we are getting failures every time we run the tests as some tests are not run. Is there some way we can determine which tests are not running and causing this issue and tell NCrunch to ignore the fact that those tes…

    24 Jul 2017 15:46 UTC

  15. Console runner passes all tests, but returns failure

    We are running our tests in TC using a grid of 3 machines. The tests all run successfully (there are no failures) but yet the console runner always returns an output code of 1 which causes team city to think that the step failed. The end of the log has this in it: [12:09:55][Step 13/20] [1…

    04 Jul 2017 12:30 UTC

  16. Issue running tests which use embedded event store

    Hi, We are trying to get our integration tests to use event store's embedded option, but these tests fail saying this as part of the message when we try and get the status of a projection we have just created: "status": "Faulted", "stateReason": "The projection subsystem failed to load a …

    12 Jun 2017 13:39 UTC

  17. Adding tracesource configuration to ncrunch processes

    We use TraceSource logging in our application. Sometimes it would be useful to enable logging whilst the tests are running. Usually this involves adding some config to the application exe.config. If I want to add this to the NCrunch config files so that output is picked up by the tests which config …

    16 May 2017 19:04 UTC

  18. Ncrunch doesn't seem to be highlighting the start of tests in scenario outlines in feature files

    Hi, I've just updated my VS2013 to the latest build and can confirm that the markers show in 2013 but not in 2015, so not sure if this is a regression or a change in behaviour between versions of VS or because the VS integration of Specflow has been updated for 2015. Leave it with me for now whilst …

    07 Jul 2016 13:30 UTC

  19. Ncrunch doesn't seem to be highlighting the start of tests in scenario outlines in feature files

    I don't know if this is a regression or not, but I added a fix to specflow to include an additional #line pragma which enabled the starting markers to show up in the feature files when using scenario outlines: https://github.com/techtalk/SpecFlow/pull/372 I've noticed that this is no longer work…

    07 Jul 2016 08:53 UTC

  20. Aborted tests leaving behind running selenium processes

    This is a good idea for a solution, thanks!

    10 May 2016 17:19 UTC