Forum member

SeriousM

40 posts

Posts by SeriousM

  1. "Run all visible tests" != "Run all tests" behavior

    [quote=Remco;9412]This is now available with the NCrunch V3 release. [url=http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx]http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx[/url].[/quote] Awesome, thank you! Congratulations to the release!

  2. Build assemblies not optimiezed

    [quote=Remco;9278][quote=SeriousM;9277] @ramdisk: it's already 4 gb, that should be enough for 4 running threads, right?[/quote] It really depends upon the solution. NCrunch can make several workspaces for each project in your solution, depending on your change patterns and the number of work…

  3. "Run all visible tests" != "Run all tests" behavior

    [quote=Remco;9318] The next expected release at the moment is V3 due in a few weeks time. [/quote] Hmm, so an extension to the previous (not)estimation. ok. Thank you

  4. "Run all visible tests" != "Run all tests" behavior

    I know you hate this question but do you have an eta for that now? Its already 3 weeks ago and I really need this feature soon. Thank you

  5. "Run all visible tests" != "Run all tests" behavior

    [quote=Remco;9304]Hi, Yes this makes sense. I'll see what I can do. Thanks for bringing it to my attention.[/quote] I know you hate this question but do you have an eta for that? Is the execution still trigger-able via editor-mouse interaction? Thanks

  6. "Run all visible tests" != "Run all tests" behavior

    Hi Remco, the functionality of "Run all tests" and "Run all visible tests" should be more or less be the same. Especially in case of (nunit) explicit-marked tests. [img]https://i.imgur.com/BGKkVbQ.gif[/img] As you see, "run all visible tests" executes the explicit test. I assume that's a …

  7. Build assemblies not optimiezed

    I didn't found a pattern yet, but I will pay attention to that from now on. Will report back once I've found it. @ramdisk: it's already 4 gb, that should be enough for 4 running threads, right?

  8. Build assemblies not optimiezed

    I do see code coverage without any problems. I had/have the this particular problem with multiple project setups over the last couple of years and today I decided to ask you if there is a way to fix it :) The problem affects bigger solutions with multiple projects. Maybe thats the problem that the…

  9. Build assemblies not optimiezed

    Hi! When I debug a test it seems that the assembly is build with optimization turned on so that some of the symbols aren't available (inspection not available). When I debug with resharper I can inspect all the symbols no problem. Is there a flag where I can tell ncrunch to include/exclude op…

  10. Font is italic now

    I just noticed that resharper has the same issue in the code-preview window of "Find Results" as ncrunch in the output panel. one thing I also changed was installing the VS2015 SP3 hotfix (vs14-kb3165756) that was released a few days ago (suggested by the vs2015 ide), maybe this is the problem?

  11. Font is italic now

    The font is installed and used since months so there is no change on my machine. The only difference is that i used to use the version 2.23 and now using 2.24. I was not able to produce a workaround to get Hack working without Italic style.

  12. Font is italic now

    Hi, since the last update it seems that NCrunch is using the wrong Font for rendering the output. I have installed the hack font (https://github.com/chrissimpkins/Hack) in * Hack (Normal) * Hack BoldOblique (Italic) * Hack RegularOblique (Italic) It seems that it uses the last one in the l…

  13. NCrunch is not seeing some tests

    [quote=leadensky;8974]Success! I rolled NUnit back from 3.4.1 to 3.0.1, and suddenly all my tests are showing up and behaving (running) normally. [UPDATE]: NUnit 3.2.1 is also working.[/quote] Yesterday I tried to switch from MSTest to NUnit 3.4.1 and noticed that not all of the tests projects…

  14. Inconclusive tests sometimes not treated as passing

    [quote=Remco;8895][quote=SeriousM;8894]That also means that I could be your beta tester of V3 if you agree![/quote] Consider yourself on the list! :) [/quote] What's the roadmap for V3? Any date available?

  15. Inconclusive tests sometimes not treated as passing

    I'm currently the only one using ncrunch in my team so I just ignore the problem for now. That also means that I could be your beta tester of V3 if you agree!

  16. Inconclusive tests sometimes not treated as passing

    [quote=Remco;8891][quote=SeriousM;8888] Can you verify it on your side?[/quote] Yes! Thanks! I've reproduced this now. It looks like a compatibility hole in NCrunch's MSTest adapter. I'll see about getting it fixed. Thanks for taking the time to report it.[/quote] It's my pleasure, a…

  17. Inconclusive tests sometimes not treated as passing

    Ah, I found the bug: [code=csharp] public abstract class TestBase { [TestMethod, ExpectedException(typeof(Exception))] public virtual void SomeTest() { // all good Assert.AreEqual(1, 1); } } [TestClass] publi…

  18. Inconclusive tests sometimes not treated as passing

    One of a couple of inconclusive tests is executed and fails even with the setting [quote]<ConsiderInconclusiveTestsAsPassing>true</ConsiderInconclusiveTestsAsPassing>[/quote] with the lovely hint [quote]NCrunch: This test reported an inconclusive result. You can adjust whether NCrunch should tre…

  19. Way to see configuration difference to standard configuration

    Hi! Is it somehow possible to tell the difference from default settings to the already set settings? I need it because I have to write a small manual how to setup NCrunch with our project and the .ncrunch* files are binary and don't show changed settings. Thanks!

  20. Risk/Progress Bar State Indicator Problem

    Hi Remco, did you found time to fix the problem? Cheers