Forum member

KrisVH

9 posts

Posts by KrisVH

  1. Coverage shows black when tests cover code

    Just installed it. I thought I had the issue again because 2 lines in a constructor were black while they were actually covered by 3 tests (that all passed.) The lines before them were all green. All the lines just do an assignment, so nothing complicated. Pushing the Reset button seems to have f…

  2. Updating NCrunch.Framework.dll

    It would be nice if upgrading the NCrunch.Framework dll would be easier. Having to extract the dll from the GAC isn't that bad (well, it's not pleasant either), the problem is that the dll isn't updated in any of my projects. I don't know how easy it would be to make a NuGet package for it, but I…

  3. Coverage shows black when tests cover code

    It's probably relevant that I didn't exactly copy the solution, but cloned it through my source control system. This means that all ignored files (which includes all cache files and compiled files and VS user options) were not copied with it.

  4. Coverage shows black when tests cover code

    Ok cool. I have some more information though (and a bug report/feature request): I copied my solution to another location to try and isolate the problem. Interestingly, everything immediately looked fine: all code that is covered is also indicated as covered. (Well, I didn't check everything, …

  5. Coverage shows black when tests cover code

    [quote=Remco;2046]Hi Kris, Make sure your test project is referencing the project under test through the use of a <ProjectReference> tag in the .proj file, and not using a <Reference> to the project's output DLL. This is called a 'lost reference' and it prevents NCrunch from knowing about the re…

  6. Coverage shows black when tests cover code

    Hi. I have several methods that show black dots while the tests that cover them show green dots. Unfortunately, I don't really have a lot of extra info to give you :-/ They're not particularly complicated methods either, just a bunch of extension methods and some others that access a webser…

  7. Test metrics

    Or, as I see now, maybe ignoring entire functions could be useful as well. And since we're already tagging functions with the ExclusivelyUses attribute, ignoring functions for metrics could perhaps work the same way. Edit: did I say useful? I meant very useful. :-)

  8. Test metrics

    Yeah, that would probably work. Maybe it would be more elegant to find a way to keep it out of the source code files, like you do with ignoring entire files, but I can't think of a good way to indicate what lines you want to ignore then. Line numbers wouldn't really do it :-)

  9. Test metrics

    First off, I find NCrunch totally brilliant. The new test metrics screen is awesome as hell, it's clean and clear, showing exactly what you need to see and nothing more. Props too for how you managed to only count lines that aren't generated by designers. One question: excluding files from metric…