Forum member

whirly

5 posts

Posts by whirly

  1. Move coverage markers slightly to avoid conflicts with R# jewels

    Well, personally I've no complaints about performance at the moment - the heuristics of only running tests that need be run seem to work well and I've not suffered. The machines I am using though are quite fast (a Core i7 2600 @ 3.4Ghz and a Core i7 2700K @ 4.8Ghz) with plenty of memory. (I'm curren…

    19 Mar 2012 15:36 UTC

  2. Continouous Testing Tools Feedback

    I've evaluated the field and definitely like NCrunch the best. Here's my feedback: MightyMoose: The graph display is flashy rather than helpful, simple tooltips work better. The risk indicators are presumptuous and often innapprioriate. Having red and yellow lights that aren't warranted is just a…

    19 Mar 2012 13:45 UTC

  3. RedGate .NET Demon

    I've evaluated the field and definitely like NCrunch the best. Here's my feedback: MightyMoose: The graph display is flashy rather than helpful, simple tooltips work better. The risk indicators are presumptuous and often innapprioriate. Having red and yellow lights that aren't warranted is just a…

    19 Mar 2012 13:40 UTC

  4. Move coverage markers slightly to avoid conflicts with R# jewels

    [quote=Remco;1476]The big question would be where to move them to ... if they go further to the right, they may interrupt the code .. if they go further to the left, a new tray will be needed to hold them :)[/quote] I don't think a new tray is a bad idea you know. I guess you're worried about scr…

    17 Mar 2012 17:50 UTC

  5. WaitHandle.WaitAll() on STA thread

    Here's a repo, in case it helps. This test will fail in NCrunch, but works elsewhere (eg. Resharper, other continuous testing tools): [code=csharp] [Test] public void TryWaitAll() { Func<TimeSpan, ManualResetEvent> runThread = t => { var mre = new ManualResetEvent(false); …

    15 Mar 2012 09:49 UTC