The biggest lesson for me this week was actually more like a reminder. We should lean into smaller, faster tests whenever we can, but we should thoughtfully layer in larger tests to validate realistic, end-to-end behavior. That way we acknowledge the lesson of the test pyramid and and avoid relying too heavily on either extreme to our own disadvantage. Like so many other things, there's a balance.
I imagine working at a startup with out the big budget of a huge legacy enterprise, or anything to fall back on. Deploying large tests without first working out a test coverage strategy could waste vital resources and delay delivery. Leaning too far in the opposite direction and focusing on the faster unit tests could create test escapes that only surface in end-to-end scenarios. Striking a balance between test methods makes absolute sense and should be a point of focus.
No comments:
Post a Comment