Forum member

devdept

53 posts

Posts by devdept

  1. Slow unit test runs forever

    Unfortunately, most of our unit tests have high algorithmic complexity... What it is not clear to me, is if we would not be able to trust impacted test information once we add suppress code coverage tracking for many of them. Thanks, Alberto

    25 Feb 2019 11:03 UTC

  2. Hiding NUnit unit test with the Ignore attribute

    Thanks Remco, Here is our syntax. Does it tell you something? As mentioned earlier we still have both MStest and NUnit enabled. [NUnit.Framework.Ignore("Wrong curve in original Brep representing number 3")] [TestCategory("Step"), TestMethod, NUnit.Framework.Test] publ…

    25 Feb 2019 07:45 UTC

  3. Hiding NUnit unit test with the Ignore attribute

    Hi There, How can we remove from the NCrunch Tests window the failed test with the NUnit Ignore attribute? Thanks, Alberto

    24 Feb 2019 13:31 UTC

  4. Slow unit test runs forever

    Oh yes, without code tracking all the timings are fine and we benefit from parallel execution and distributed processing. That's a big step ahead. It's a pity for code coverage, it was a great feature. Tomorrow I will discuss with the DEV team about this discovery. Just a confirmation: should …

    24 Feb 2019 13:25 UTC

  5. Slow unit test runs forever

    Here is the proof: https://www.screencast.com/t/rb5T24ijrxx

    23 Feb 2019 18:11 UTC

  6. Slow unit test runs forever

    I've to say that some unit tests are simply way to slow. Leaving the machine alone during the week-end I got all the test completed successfully. Some of them took 2 hours instead of 10 minutes. Does this tell you something? Thanks, Alberto

    23 Feb 2019 17:56 UTC

  7. Slow unit test runs forever

    Now I see that clicking the Test category the tab is showing some data: https://www.screencast.com/t/HVyRy6ACqtQ https://www.screencast.com/t/rFSgUyLFP77g

    23 Feb 2019 11:27 UTC

  8. Slow unit test runs forever

    Hi Michael, Here I am again. The additional tab does not show anything for all these problematic unit tests: https://www.screencast.com/t/o20pVKNjUrxS I'm leaving them run for all the day to see if they will complete but more than once I was forced to stop them after a long time.

    23 Feb 2019 11:11 UTC

  9. Slow unit test runs forever

    Hi Michael, In this image, we were executing the same test (alone) on the same machine without any debugging. https://www.screencast.com/t/YlpGliwG I will try with the extra tab you recommended and let you know. Thanks, Alberto

    22 Feb 2019 15:09 UTC

  10. Slow unit test runs forever

    Another image regarding these problematic unit tests: https://www.screencast.com/t/YlpGliwG How is it possible that on the same machine, we get such different timing? We are ready to buy a number of licenses but there are 20 unit tests on 2000 that don't work as expected. Thanks again, …

    22 Feb 2019 11:13 UTC

  11. Slow unit test runs forever

    Another interesting message from a different unit test: https://www.screencast.com/t/1ysOFSuJyZm

    21 Feb 2019 15:54 UTC

  12. Slow unit test runs forever

    Trying to go ahead I got this one: https://www.screencast.com/t/A3q7LqxxY We are constantly opening files from a remote folder that starts with \\backup\openshare\... to run our unit tests. Does it tell you something? Thanks, Alberto

    21 Feb 2019 15:25 UTC

  13. Slow unit test runs forever

    Hi Michael, The test does not seem blocked, it seems extremely slow. After a while, I got this exception: https://www.screencast.com/t/uWPIcsolAThW Does it tell you something? I executed one of these problematic tests manually at debug from NCrunch and added System.Diagnostics.Debugger.L…

    21 Feb 2019 15:10 UTC

  14. Slow unit test runs forever

    Hi Remco, Regarding: I'd suggest hooking a debugger onto these hung processes to see what they're doing. Can you provide more instructions? Normally do you use Visual Studio for this purpose? Actually, these unit tests work fine in all our DEV machines. So we don't know what to look. …

    21 Feb 2019 13:06 UTC

  15. Slow unit test runs forever

    Hi Remco, We have almost completed our evaluation. I have to say that NChrunch is great. The last open issue is the following. Check the image below. There are a number of unit test (most of them slow) that run forever and prevent developers to check-in their changes. https://www.screencast…

    20 Feb 2019 21:20 UTC

  16. Forcing NUnit

    Thanks Remco, Yes, we decorate the tests with the following attributes that enable both MStest and Nunit. It's time to make a choice. [TestCategory("Surf"), TestMethod, NUnit.Framework.Test] Thanks again. Alberto

    19 Feb 2019 06:26 UTC

  17. Forcing NUnit

    Hi Remco, Inside Visual Studio, we can manually run tests using VStudio Test Explorer (MStest) or Resharper(NUnit). I was wondering if we could specify a preference with NCrunch. Thanks, Alberto

    18 Feb 2019 10:43 UTC

  18. Forcing NUnit

    Hi There, How do I force NUnit over MSTest in NCrunch? Thanks, Alberto

    18 Feb 2019 09:54 UTC

  19. 5GB of dataset needed by unit tests

    Resolved, one project had the Configuration = RELEASE missing. Thanks! Alberto

    18 Feb 2019 09:53 UTC

  20. 5GB of dataset needed by unit tests

    Hi There, Yes, most of our unit tests need to load data files and perform tests against them. The data file folder size is beyond 5GB and I don't believe it's a good idea to copy everything to NCrunch workspace at each run. Should I try or is there a more convenient way to access these files? …

    17 Feb 2019 21:18 UTC