Forum member

Marqus

38 posts

Posts by Marqus

  1. Very long initalization time

    I'm still experiencing hangs during using nCrunch (not only during initialization). Devenv.exe goes up, and nCrunch is working very slowly (sometimes on build task, sometimes on running tests). When devenv fully loads one core, Configuration and Queue windows are empty. We doesn't have tests that us…

    30 May 2012 06:51 UTC

  2. MetricsExclusions saved as absolute paths

    In *.ncrunchsolution paths in MetricsExclusions are absolute - IMHO they should be relative. We keep this file under source control, developers has different paths to their local workspaces, so we are getting conflicts all the time, and this conflicts aren't resolvable. Another suggestion: Metric…

    25 May 2012 10:04 UTC

  3. Compile Errors Hyperlinking.

    - If you move the horizontal scrollbar far to the right so that the code is no longer visible (add lots of spaces if you have to), then try to navigate to the test, does the horizontal scrollbar move in any way? When I've tried to do this, I had to turn of WordWrap (Ctrl+E,W) - I don't know why I h…

    25 May 2012 09:16 UTC

  4. Compile Errors Hyperlinking.

    - Which version of Visual Studio are you running? 10.0.40219.1 SP1Rel - Does the problem occur on other solutions too? (i.e. if you just create a small dummy C# project with 1 test, does it work?) I've created new solution, with one TestFixture. I've created several tests (copy&paste) so they t…

    25 May 2012 07:38 UTC

  5. Compile Errors Hyperlinking.

    There's no collapsed regions in this file. More tests: 1. ContextMenu -> Outlining -> Stop Outlining 2. Disable extensions : - Feature Extension Feature - PowerCommands for Visual Studio 2010 - Productivity Power Tools - Regex Tester Scrolling still isn't working

    25 May 2012 06:03 UTC

  6. Compile Errors Hyperlinking.

    After clicking on hyperlink, carret is moved to the correct line, but screen isn't scrolled. Same behavior when using "Go to selected test" in test window. I've found: http://forum.ncrunch.net/yaf_postst201_-v1-37b--Issue--go-to-test-does-not-work.aspx - I don't have any region in this particular f…

    24 May 2012 09:39 UTC

  7. new column in code coverage window

    Another vote for "Uncovered Lines" in Metrics window

    24 May 2012 09:25 UTC

  8. Very long initalization time

    Clearing .cache file solved the problem - thanks.

    24 May 2012 05:33 UTC

  9. Very long initalization time

    After few days of using 1.39b, nCrunch started to take very long time on "NCrunch engine is initialising". Previously it took several seconds, now it takes several minutes. I've looked into Task manager, and it shows, that devenv.exe fully loads one core, several nCrunch.TaskRunner40.x86.exe are idl…

    23 May 2012 13:37 UTC

  10. workspaces taking a lot of disc space

    I've moved my 'Workspace base path' to ramdisc (currently 512 MB) and NCrunch can 'eat' this space in under one minute of code editing:) My tested assembly has many dependencies on my own components and 3rd party component which has dependecies to many C++ dll's. My assemblies are copied by ncrun…

    06 Mar 2012 10:18 UTC

  11. Add Pin/Unpin tests on assembly level

    Thanks for reply "Run all tests" will work :) Customised engine modes sounds interesting, I will wait for them.

    24 Feb 2012 09:48 UTC

  12. "Risk/Progress" - distinction beetwen "failed this run" and "failed last run"

    Or maybe only FTR number?

    24 Feb 2012 07:48 UTC

  13. "Risk/Progress" - distinction beetwen "failed this run" and "failed last run"

    Another way would be showing two numbers, but I'm not sure about this soultion - it can be too difficult to understand

    24 Feb 2012 07:35 UTC

  14. Add Pin/Unpin tests on assembly level

    I've started using pinning because of the problem described in: http://forum.ncrunch.net/yaf_postst212_-Build-in-progress--for-extended-periods.aspx - pinning only interesting tests makes this problem less frequent. But this is using pinning as a workaround, and pinning should be used for something …

    24 Feb 2012 07:33 UTC

  15. "Risk/Progress" - distinction beetwen "failed this run" and "failed last run"

    'NCrunch Risk/Progress' window shows number of failing tests, but without distinction beetwen "failed this run" and "failed last run" (but not executed in this run yet). Without this distinction, we have to wait for all red tests to pass. With this distinction, during test run we will have two scena…

    23 Feb 2012 14:23 UTC

  16. Add Pin/Unpin tests on assembly level

    And one more: "unpin all tests"

    23 Feb 2012 11:39 UTC

  17. Add Pin/Unpin tests on assembly level

    I've got solution with many projects, so I pin only those test that I need at this moment. If I want to pin all tests from assembly, i have to expand this assembly, select all test and pin them. I would like to pin assembly - all tests in this assembly should be pinned/unpinned automatically.

    23 Feb 2012 08:21 UTC

  18. "Build in progress" for extended periods?

    I've got same problem, but I'm not a fast typist, so maybe it's some other, but very similar scenario. Problem occurs very frequently, so nCrunch is almost unusable. Some more information about my environment: - solution with 15 projects (8 production assemblies + 7 test assemblies) - in one solut…

    22 Feb 2012 08:00 UTC