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
Inheritance of Categories #558
Comments
If the |
I have cloned your repo and implemented the functionality with an optional Parameter "inherited" in Category that defaults to false. I further changed the Categories-Runner to evaluate this Parameter and support inheritance. This does not change the current behaviour but supports optional inheritance. Im just too dumb to understand how to ask you to merge it back :) |
@gaffa, there should be a "Pull Request" button at the top of your fork. That should get you on your way to creating an official pull request. Thanks! |
Perfect. Thank you! |
@other people interested in this: http://tech.groups.yahoo.com/group/junit/surveys?id=3125322 |
It looks like this issue can be closed as it has been resolved by pull request #566 |
Agreed. |
I need to Annotate all our IntegrationTests. As I realized they all inherit from only like 3 different abstract tests I felt like maybe I am ready already because I simply can annotate the abstract class. Just that this behaviour is not as expected.
Example:
@category(IT.class)
public class A{
@test
public void testInAnnotatedClass() {
System.out.println("inheritance: method in annotated class ran.");
}
}
public class B extends A{
@test
public void testInInheritingClass() {
System.out.println("inheritance: method in inheriting class ran.");
}
}
Running this will result in only testInAnnotatedClass() being ran.
The text was updated successfully, but these errors were encountered: