On some use cases it's desirable to test inherited, accessible methods. Tests are being generated for inherited methods since it's usually easier to remove unwanted test methods from the generated test class rather than hand code these tests (or at least the boilerplate part of these tests). I think that giving the user the option to opt out of generating tests for inherited methods is an important feature. I'm not sure if I can push it in the up coming release, but I'll give it a high priority for the next releases. Thanks for raising this feature request. Tests will be generated for accessible methods, so if by design, it's possible for you to change the method access modifier ( i.e. private ) then that would do the trick.