… or tell us about a time when your tests destroyed you.
For further actions, you may consider blocking this person and/or reporting abuse
… or tell us about a time when your tests destroyed you.
For further actions, you may consider blocking this person and/or reporting abuse
Ramon Borges -
Madhawa Awishka -
Ben Halpern -
Alex Lohr -
Top comments (3)
We were using a statistics library developed by another team in the company. Since that other team couldn't be bothered to write tests, we had an extensive integration test suite on that library (that's about all the tests we had, our project manager and architect thought we shouldn't bother to test our own code, but that is a story for another time). Every time they released an update on that library, we would discover half a dozen breaking changes thanks to our integration tests.
During the very extended 2 years of 'final testing' of our satellite code, during which time we changed a piece of hardware (the EPS - electrical power system) that could have failed the mission:
Pre-conditions:
Critical code:
Fatal change:
Impact discovered during full deployment test 1 month before launch:
Fix:
Outcome:
When I update a package from 6.1.1 -> 6.2.1 and think, "that couldn't . have broken anything, right?"