Organize your tests such that one group is testing the functionality of the class's public interface, and another group is testing the internal implementation. The internal implementation tests are more likely to become broken as the implementation evolves, but the public interface tests should be quite stable. And by separating them into different groups, it's easier to determine if the result of a change will be acceptable without a deprecation cycle.