Forum member

gravypower

13 posts

Posts by gravypower

  1. Code coverage missing when using dynamic keyword

    Hey, FYI: I am able to step trough the code. Aaron

  2. Code coverage missing when using dynamic keyword

    Worked out the issue. It was the Roslyn CTP. I am working with it in the project I originally found the issue, and when I created a simple project with the above test I had the same problem. This got me thinking that it could be Roslyn as I assume you did not have it installed. Removed it …

  3. Code coverage missing when using dynamic keyword

    I will put something together this evening (morning your time) Aaron

  4. Code coverage missing when using dynamic keyword

    Forgot, Using VS 2013 with NCrunch 2.7.0.5

  5. Code coverage missing when using dynamic keyword

    Hello, I am having an issue when using the dynamic keyword. When I have test like this: [Test] public void DynamicKeyword() { dynamic o = new ExpandoObject(); o.Foo = "Bar"; Assert.That(o.Foo, Is.EqualTo("Bar")); } …

  6. Test Icons not updating

    Hey Remco, Just though I would let you know that my test icons sometime don't update to a tick: [img=http://blog.gravypower.net/content/images/2014/Feb/2014_02_27_10_36_38.png]Icons [/img] NCrunch looks to have finished but some of the tests still show the clock. Aaron

  7. MS Fakes cause slow tests

    Finally got around to Blogging about this and thought I would share it here. http://blog.gravypower.net/ncrunch-sharepoint-and-microsoft-fakes/ Hope that helps someone :D Aaron

  8. MS Fakes cause slow tests

    Also Remco, thanks you so much for ncrunch. It has helped me to use Red Green Refactor all the time. Aaron

  9. MS Fakes cause slow tests

    That is so much better, I included all the files in the 'FakesAssemblies' directory(this is a sub direct of the project where fake assemblies have been added). As far as I can tell this is where VS puts the generated assemblies. Thanks Aaron

  10. MS Fakes cause slow tests

    That is a very good idea, I will give that a go and let you know.

  11. MS Fakes cause slow tests

    Thanks Remco, I will keep an eye on the build times and let you know. I will have to do a bit more investigation if this is a good idea, but would it be possible to have fake assemblies compiled once and coped around to the workspaces? Aaron

  12. MS Fakes cause slow tests

    Hey all, I am wondering if anyone else is having issues with the speed of ncrunch when using MS Fakes. I am using it to shim out SharePoint for TDD but the tests take a very long time to run. I think this might have something to do with the faked assembly being generated each time by ncrunch? …

  13. Give feedback for test in a collapse region

    I have been trying out writing some hierarchical tests and it has been nice to organise them into regions. It would be cool to show a collective feedback of the tests in that region.