Forum member

otac0n

51 posts

Posts by otac0n

  1. Copying large files using [DeploymentItem] is a race condition?

    About 50% of the time, I have tests failing, because one of our deployment items is very large. This appears to be because copying the file takes longer than starting up the test engine, as we are getting a FileNotFound.

  2. Config file manipulations fail

    DeploymentItem can be applied per-class, as well.

  3. workspaces taking a lot of disc space

    I had a 4GB ramdisk, and it kept getting filled up. I would have to disable/reenabe NCrunch (or restart the solution) to get it to clean up.

  4. Aggressive Caching on Forum Giving incorrect Read/Unread indicators.

    No problem. My guess is that it is cached in a cookie, and that reading a post does not invalidate the cookie for the parent forum.

  5. Aggressive Caching on Forum Giving incorrect Read/Unread indicators.

    I don't know if you are aware or not, but it appears that the indicators on the forum software you are using are broken. After reading a thread, it seems like I have to clear my cookies to get it to show up as read. *EDIT* Actually, it seems that if you read the last unread thread in a forum,…

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

    You could just have the number count down as tests from the last run are fixed (or deleted).

  7. Recursive code being edited can sometimes cause NCrunch workers to die horriffically.

    I don't mind the processes getting torn down, but I would like to avoid the "Windows Error Reporting" boxes from popping up in front of Visual Studio. Possibly helpful: http://stackoverflow.com/a/1599236/57986

  8. Recursive code being edited can sometimes cause NCrunch workers to die horriffically.

    When working with some recursive code, you can get into a situation where the code is infinetly recursive, and the resulting StackOverflowException crashes the workers. Just as a contrived example: [code=csharp][Test] Example_DoesNotStackOverflow() { Example("abc"); } private void E…

  9. Add NCrunch.Framework to NuGet

    Respectfully, I don't see how putting the assemblies on NuGet "will only make this worse". People "create version inconsistencies" by upgrading NCrunch to the next version, NOT by referencing a new Framework version. The framework version is only going to be updated when the NEW version of NCrun…

  10. ETA of MSTest data driven tests?

    At this point, I'm willing to pay many of my dollars, or spend many hours of my time to get this feature.

  11. New feature (cosmetical) request

    For me, it is all of them, but especially the vertical line. It appears as though the vertical line does not coincide with the hit-box at all.

  12. New feature (cosmetical) request

    As a side note to this, I have to say that it is very difficult for me to hover over the X to even click it. The hit-box is quite small, and I don't think that it changes when you switch the marker style (that is, switching to the Rectangle or VerticalLine still has the same, small click area.)

  13. v1.37b - Debug variables

    I'm getting these results in iterator blocks (methods with `yield return` in them).

  14. Add NCrunch.Framework to NuGet

    The same problem would arise when more than one person are sharing a solution as well, so I'm not sure how that affects the decision to use NuGet.

  15. Problem with NUnit TestCase attribute

    Yeah, I see your points. I guess that a success for ignored tests is acceptable. At least it would get 99% of people up and running.

  16. Problem with NUnit TestCase attribute

    It doesn't really make sense to consider the tests as passed, either. It would be better if they show up as though they never ran. Ideally, they should show up as though they are ignored (this probably applies to calls to Assert.Ignore() as well).

  17. Problem with NUnit TestCase attribute

    It looks like [Theory] and [TestCase] are working, but I believe that the behavior of Assume is incorrect. Assume.That(false) should never cause an individual test case to fail, it should instead be considered inconclusive (or ignored, if that is easier). Right now, my solution shows 137 "fail…

  18. ETA of MSTest data driven tests?

    I was excited to see that a big release of NCrunch was out today, great work. However, I have subsequently been disappointed when it turned out that MSTest data driven tests were still unsupported. This is a feature I like to use on almost all of my tests, since it reduces the amount of test c…

  19. TreeView / DataGrid Hybrid control

    [quote=Remco;700]I wish I could say it was free, but I did have to pay for it.[/quote] I suppose that is the main reason that it is closed source, then? It seems to be pretty pricy.

  20. TreeView / DataGrid Hybrid control

    Just out of curiosity, what control are you using for the "NCrunch tests" window, and the "NCrunch Processing Queue"? I've been looking everywhere for a control that had those capabilities (tree / grid), but could not find anyone who knew about them.