Testing Trophy
A software testing methodology variant proposed by Kent C. Dodds that advocates increasing the proportion of integration tests relative to other testing layers. The model holds that verifying how modules work together more closely reflects real user needs than unit-level logic verification alone, and is considered well-suited to modern front-end and microservices architectures.
Timeline (last 90 days)
The industry usually uses the "testing trophy" to strike a balance: few but refined unit tests, integration tests covering real dependencies, and end-to-end tests catching critical paths, avoiding the test pyramid being inverted into an "ice cream cone".
The Testing Trophy was proposed by Kent C. Dodds and advocates for further increasing the weight of integration tests.
All Facts (2)
The industry usually uses the "testing trophy" to strike a balance: few but refined unit tests, integration tests covering real dependencies, and end-to-end tests catching critical paths, avoiding the test pyramid being inverted into an "ice cream cone".
50%UnverifiedThe Testing Trophy was proposed by Kent C. Dodds and advocates for further increasing the weight of integration tests.
50%