It's not about that imo. It's about having tests that are limited in scope as much as possible, so if they fail it's much easier to understand the problem. Ide

It's not about that imo. It's about having tests that are limited in scope as much as possible, so if they fail it's much easier to understand the problem. Ideally tests should be run in a specific order, from most low level to most high level. So tiny basic functions first, then functions that use those functions, then functions that use THOSE functions, etc until you have end-to-end tests. Unfortunately I know of no testing system that has such a hierarchy.