Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trait grouping not working for class-level categories #118

Open
MelGrubb opened this issue Feb 19, 2016 · 2 comments
Open

Trait grouping not working for class-level categories #118

MelGrubb opened this issue Feb 19, 2016 · 2 comments

Comments

@MelGrubb
Copy link

First of all, let me say that this project is great, and I'm excited to see community support for coverage tooling. I only just started looking at it today, and it's already 95% of what I need. I got red/green highlighting and a usable report. The installation process is a little... weird, but I figured it out.

I have decorated my test classes with Category attributes, which works just fine in Visual Studio's built-in test explorer. The are not, however, picked up by OpenCover's test explorer. If I put the category attributes on the individual tests, then they are properly categorized.

If someone looks into this, I would also suggest that you make sure to look at inherited attributes. I normally add my category attributes to an abstract class that applies to an entire area. For instance, I may have an abstract FooControllerTests base class, from which I would inherit a When_Getting_the_Index_view class, which would have a Then_the_blah_blah_blah method. This way, the category applies to a whole group of tests automatically, and I can re-categorize them easily if I wanted to.

Of course, project/namespace hierarchy grouping would obviate the need for trait grouping altogether in my case. I see that's already been requested. I second that request.

@pver pver added this to the Release 0.8.x milestone Feb 19, 2016
@pver
Copy link
Contributor

pver commented Feb 19, 2016

Good suggestion indeed, thanks! 👍 I'll add it as planned for the next release

@lorenh
Copy link

lorenh commented Sep 8, 2016

This would be a great addition we could really use. Is there any sort of timeline for pulling together another release with all of the fixes since 0.8.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants