the_testing_pyramide
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| the_testing_pyramide [2025/09/02 19:22] – created plida | the_testing_pyramide [2025/09/03 13:11] (current) – plida | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| [[https:// | [[https:// | ||
| - | The testing pyramide is a conceptual model that shows how to correctly distribute unit, integration and end-to-end tests. | + | The [[software_testing|testing]] pyramide is a conceptual model that shows how to correctly distribute |
| + | |||
| + | {{ https:// | ||
| ==== Main takeaways ==== | ==== Main takeaways ==== | ||
| Line 9: | Line 11: | ||
| - The more high-level you get, less tests you should have. | - The more high-level you get, less tests you should have. | ||
| - Write tests with different granularity. | - Write tests with different granularity. | ||
| + | |||
| ==== Benefits ==== | ==== Benefits ==== | ||
| Line 16: | Line 19: | ||
| - Ensures a balance between speed of feedback and complete verification. | - Ensures a balance between speed of feedback and complete verification. | ||
| - | {{ https:// | + | ==== Typical mistakes |
| + | |||
| + | * ice cream cone (reversed pyramid) | ||
| + | * high-level tests repeat low-level ones. | ||
| + | * isolation break: unit tests access the database or network and become integration testing. | ||
| + | |||
the_testing_pyramide.1756840961.txt.gz · Last modified: by plida
