Forum member

jnm236

57 posts

Posts by jnm236

  1. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    Just to be clear, ReSharper does actually correlate test results between runs like that. It's not sequential. Thanks for the explanation. I hear you on the endless problems. What is your opinion on using the test name rather than the ID? That includes the parameter and is required to be unique…

  2. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    Also, when I'm not right click+rerunning but I am editing code and affecting the number of test cases, NCrunch's Tests window can get so far off it's mixing up the test cases with test case from completely different test methods.

  3. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    Also I was wrong about needing to click Resynchronize, rebuild and rerun every time. I'm not sure why right clicking and rerunning the test class wasn't working for me yesterday but it's working now.

  4. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    I know that ReSharper doesn't have a problem identifying the tests between changed assemblies. ReSharper also groups dynamic tests by method which is helpful and would be cool to see in NCrunch. NCrunch 2.20.0.4, NUnit 3.2.0. I'm not sure what a sliding build delay is, but the changes I'm making …

  5. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    I use the TestCaseSource attribute to generate a dynamic number of tests. NCrunch works well with this except when the number ([b]or order[/b]) of tests changes. NCrunch seems to identify the dynamic tests by order. If I change some code which changes the number or order of the dynamic test cases…

  6. Exception message column hides the critical part of the contents

    That's a perfectly reasonable constraint. On the flip side, that information clarifies the problem at hand. Exception objects aren't strictly the domain of what we are interested anyway. The domain is text. All I need is to be able to trim the beginning so the message portion is visible. With tha…

  7. Exception message column hides the critical part of the contents

    [quote=Remco;8463]I know it looks easy, but of course, there's always hidden bits. Trust me. It isn't as simple as you think it is. I would need to see solid demand for such a feature to warrant implementing it.[/quote] What's the risk? Worst case, the column is unusable. But the column wasn…

  8. Exception message column hides the critical part of the contents

    [quote=Remco;8461]Hi, Thanks for the feedback on this. Unfortunately, this is now becoming much more complicated, as NCrunch now needs to pick apart exception data to try and construct this report. There are also edge cases to consider (i.e. what about aggregate exceptions that have their own…

  9. Exception message column hides the critical part of the contents

    This may be a more appropriate place to follow up with issues, since the [url=https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/12883974-add-short-exception-message-column-in-tests-window]UserVoice suggestion[/url] has been completed. Unfortunately this feature is not usabl…

  10. Projects using NuGet v3 do not build in NCrunch, error about global.json

    Good to know!

  11. Benefits of NCrunch vs Other Test Tools

    This guy says it really well: http://blog.iannelson.systems/one-reason-why-ncrunch-is-worth-the-cost/

  12. Benefits of NCrunch vs Other Test Tools

    I don't use NUnit, only NCrunch. For me it's very simple. 1. It runs constantly and smoothly. With ReSharper and Visual Studio I just plain didn't remember to take the time to run tests very often. NCrunch stays out my way. It doesn't use up any of my time or mental process, but it gives me all t…

  13. Projects using NuGet v3 do not build in NCrunch, error about global.json

    Installed NCrunch_VS2015_2.20.0.3.msi, everything works as expected. Thanks for the amazing turnaround time!

  14. Projects using NuGet v3 do not build in NCrunch, error about global.json

    Because NuGet packages are coming out that make the old NuGet v2 (packages.config) much less desirable to use than the NuGet v3 (project.json) system, we migrated our projects. (See [url=https://oren.codes/2016/02/08/project-json-all-the-things/]Project.json all the things[/url] by Oren Novotny.) …

  15. Tests that use await randomly time out

    I was successful in putting together a bare-bones demo. To repro, open the .sln and type a space in Program.cs and erase it, just to trigger a build. TaskCompletionSourceAwait fails every time. DelayAwait does not fail in the demo project, only in the full project. In case it's relevant: NCrunch …

  16. Tests that use await randomly time out

    I did a little more digging. It seems like thread pool starvation. On a hunch, I turned off parallel execution for the solution. With parallel execution off, I'm still getting timeouts on similar tests but not for these particular tests. Also with parallel execution off, it takes an unbearably long …

  17. Tests that use await randomly time out

    These tests are hitting the 60 second timeout randomly. All of them complete within milliseconds when run from Visual Studio or ReSharper. In the large project I'm working on, it happens almost every time I type in a different project and cause a background rebuild. I tried to put together a tin…