Every test class on my org that has a
TestSetup annotated method shows 0/n lines covered in the developer console (Where n is the number of lines in the annotated method).
I thought maybe this was just something it showed and didn't count against test coverage. But then I pulled out a calculator and added up all the lines showed/covered and got what the org is telling me my coverage was.
So I then took out the
TestSetup lines from the total and divided again. I gained a few percentage points for org wide code coverage.
I feel like this is something obvious that shouldn't count against an orgs code coverage. So I am here checking to see if I am missing something.
I did find this earlier post, but I think the question was mis-understood.