Baking in reliability
How can we try to enforce reliability and make sure that these changes are picked up early?
We could ask our developers to run the tests before every push, but sometimes people forget. Maybe they didn't forget, but it's a small change and it doesn't seem worth going through a full test run for something so minor (have you ever heard somebody say, "It's only a CSS change...?"). Making sure that the tests are run, and pass before every push to the centralized source code repository, takes discipline.
What do we do if our team lacks discipline? What if we still keep getting failures that should have been easily caught, even after we have asked people to run the tests before they push code to the central repository? If nothing ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access