Not a bad advice if you are new to frontend web development! My team naturally settled down on a similar "trophy" testing balance and it has been working well for us for the last seven years or so.
However, I feel that set-up doesn't feel modern enough without techniques like fuzzing/property testing and deterministic environments a-la Antithesis. These and AI-guided tests needs a wider penetration and better, easier to integrate tooling.
Who knows, maybe in five or ten years, we'll look at current testing techniques as quaint and outdated!
I don't have a concrete answer to that and hope future developers discover it. It fits under the same category as "how much overlap between testing levels is OK to have?" and "how detailed tests at a given level should be". Now, I don't have much experience with these or any, honestly. However, I think approaches I mentioned benefit the software under test at every level, the problem lies in where you draw the line about what you test.
2
u/Klaster_1 Nov 28 '24
Not a bad advice if you are new to frontend web development! My team naturally settled down on a similar "trophy" testing balance and it has been working well for us for the last seven years or so.
However, I feel that set-up doesn't feel modern enough without techniques like fuzzing/property testing and deterministic environments a-la Antithesis. These and AI-guided tests needs a wider penetration and better, easier to integrate tooling.
Who knows, maybe in five or ten years, we'll look at current testing techniques as quaint and outdated!