Good afternoon everyone, normally I tend to group all the unit testing per class of coverage. For example all the unit tests related to a class named FooBar will be in a class named FooBarTest. So far so good, it gives me a quick understanding of what I am looking at.
Now I have some test classes that reaches the heights of 3k lines. IMO worth the effort of splitting those in multiple classes for better maintenance an reading. Do we have any (in)formal rules around this topic? Do anyone think I should not split the tests in separate classes? Cheers D.
