Forum member

nrjohnstone

12 posts

Posts by nrjohnstone

  1. Running tests manually while engine mode is in Impacted does not run all tests

    I've installed it using the 30 day trial and it definitely seems to have fixed the issue... time to talk to the boss man now about upgrades... Although, we have around 16000 tests across 100+ projects in our solution, and when you hit the "run all" button it has a noticable hang in VisualStudio n…

    21 Mar 2016 02:37 UTC

  2. Running tests manually while engine mode is in Impacted does not run all tests

    actually... I can't test it as I've just gotten a message that our licence key is now 1 year out of date... that's a bit harsh isn't it? Not being able to manually run the tests reliably is a show stopper, should I really have to purchase a new licence for this Remco ??

    21 Mar 2016 02:25 UTC

  3. Running tests manually while engine mode is in Impacted does not run all tests

    downloading right now :-) fingers crossed

    21 Mar 2016 02:21 UTC

  4. Running tests manually while engine mode is in Impacted does not run all tests

    I've noticed recently that NCrunch is not running all the tests when I right click on a node and run all selected tests. The enging mode is set to "Impacted tests and others manually" I have the test output window grouping by Namespaces, Fixture, Test and if I right click on say a top level name …

    18 Mar 2016 01:55 UTC

  5. Integration tests, creating databases with SetUpFixture

    Excellent advice.. NCrunch is fairly addictive and I am maybe taking things a bit far by wanting our integration tests to also be continuously run :-) I had my blinkers on with regards to uniqueness and hadn't considered using the process ID. I have tried the static boolean to prevent multiple…

    08 Nov 2015 21:39 UTC

  6. Integration tests, creating databases with SetUpFixture

    We are running our integration tests using NCrunch, and have a SetUpFixture at the namespace to create the databases before the first test runs, with a GUID in the name so each NCrunch process gets a unique database. This is all working fine (and thanks for sorting out the issue the other day Rem…

    08 Nov 2015 19:29 UTC

  7. SetUpFixture for specific namespace gets executed when running a single test in different namespace

    Brilliant Remco, that fixes the issue :-) Thanks again for an excellent product !

    06 Nov 2015 01:40 UTC

  8. Can NCrunch be improved in the "analyze stage" somehow?

    I think this has something to do with the way that in order to find out all of the test case names, all instances where you use TestCase or TestCaseSource are executed to find out the names, even if you are only running a single test from a different fixture that does not have a test case ! At le…

    05 Nov 2015 19:48 UTC

  9. SetUpFixture for specific namespace gets executed when running a single test in different namespace

    I've also confirmed that using the NUnit test runner to run an explicit test from a namespace outside of the one with SetUpFixture attribute and it does not get run, the same with Resharper v10. It only seems to be NCrunch that executes the SetUpFixture when running tests outside of the namespace wh…

    05 Nov 2015 19:29 UTC

  10. SetUpFixture for specific namespace gets executed when running a single test in different namespace

    Hi Remco, I'm using NUnit 2.6.3 with Visual Studio 2013 Update 4 and NCrunch 2.16.0.13

    05 Nov 2015 19:26 UTC

  11. SetUpFixture for specific namespace gets executed when running a single test in different namespace

    The documentation for NUnit states that a class with the SetUpFixture will run once before any tests in the namespace execute. Our integration project has a separate namespace for the databases tests and has a class with SetUpFixture to create and drop the databases as required. However we not…

    04 Nov 2015 22:52 UTC

  12. Inconclusive result in NUnit TestCaseSource

    Hi guys, I thought I'd mention that I've started using AutoFixture and was using the AutoData attribute to supply data to a NUnit test and was bumping into this same issue. However, adding the [Frozen] attribute to the parameters that were being randomized fixed the problem as this locks the value i…

    01 Jul 2015 19:56 UTC