Can a test class become an “object of God”?

I am working on a backend for ORM with open source Python. The library includes a set of 450 test cases for each backend, all of them are combined into one giant test class.

This sounds a lot to me for one class, but I have never worked on a project with 450 test cases (I believe there are ~ 2000 test cases in this library, not including test cases for each backend). Do I feel right that this is a bit on a high level (given that there really isn’t any magic number that you have to break something over), or is it just not such a big deal for the test class to have so much tests?

And even if this is not so many test cases, how could a too large class of tests be processed? Most of my refactoring knowledge is checking that there are tests for code that is being refactored. I have never had to deal with a situation where he himself is testing what needs to be reorganized.

EDIT . I used to say that these were single tests, which is not entirely true. These are more suitable terminological tests.

+5
source share
5 answers

450 , , , . , - , .

, , , Obscure Test, , General Fixture Irrelevant Information ( - ).

. Testcase , Testcase Testcase .

, , . , . TDD () .

, xUnit Test Patterns: , . , TDD, , , .

+4

, , , . , , ? borked, ; , , .

, , , - . , , > 1 ,

+2

, . TDD, ( tetris: , ..).

, , . - .

, - , . , , , , . , , . , , . , , .

450 . , ? ( ), 1:1? , .

+2

Framework . . ORM.

, . X, , , DDL/, , ..

+2

Yes, but the test class, which is an "object-god" does not seem to me a problem.

0
source

All Articles