T4MVC messing with my coverage

Question

We're using t4mvc in our project which requires min 85% coverage

since adding in t4mvc our coverage has bombed! I don't see the point in testing generated code - is there a way to ommit this stuff from our coverage?

we're using xunit fwiw

Could you modify the templates to include the DebuggerNonUserCode attribute? similar/duplicate question: http://stackoverflow.com/questions/3337887/how-to-ignore-generated-code-from-code-coverage-data — G_P, Mar 07 '12 at 17:13

jim tollan · Answer 1 · 2012-03-07T17:59:30.947

3

exactly as I was going to say G_P re your comment. the way to approach this is to add the DebuggerNonUserCode attribute, either at class level or at method level.

[DebuggerNonUserCode]
public partial class MyClass
{
    [DebuggerNonUserCode]
    public string SomeMethod
    {

    }

    public bool Anothermethod
    {

    }
}

see also:

should get you started...

edited Mar 07 '12 at 17:59

answered Mar 07 '12 at 17:53

jim tollan

22,305
4
49
63

1

T4MVC already adds DebuggerNonUserCode in most places, so I would think that should be enough! – David Ebbo Mar 07 '12 at 18:02
ncover seems to be ignoring it. – Mar 07 '12 at 21:01
it also seems to ignore the ExcludeFromCodeCoverage attribute!! arrrr – Mar 08 '12 at 09:07
mayby David (ebbo) as author might be able to step in and give guidence on that for you.. fingers xx'd – jim tollan Mar 08 '12 at 09:35

T4MVC messing with my coverage

1 Answers1