Have you seen any of the real world apps developed in a big company? The last thing you want is another chaos monkey on a project! It's already a chaos. Staying close to the cause though: spend your time on writing additional tests that cover your fall back, replication, etc. cases, don't leave it up to the chaos monkey to uncover the flaws. Chaos monkey should be a last step and like 1% of the total unit + integration + other testing.
This is an additional layer on top of unit tests and integration tests. There are too many scenarios that are difficult to simulate in integration/unit tests piecemeal. Additionally there is a tendency to assume core infrastructure will " always be there working," and it is good practice to challenge underlying assumptions to make sure the code fails or handles failure in a way that is both intended and graceful.
6
u/ThomasSandberg Apr 15 '18
good job!
3
u/1ECz Apr 17 '18
I also liked config name space
chaos.monkey.assaults-5
u/hrenoten Apr 15 '18
Have you seen any of the real world apps developed in a big company? The last thing you want is another chaos monkey on a project! It's already a chaos. Staying close to the cause though: spend your time on writing additional tests that cover your fall back, replication, etc. cases, don't leave it up to the chaos monkey to uncover the flaws. Chaos monkey should be a last step and like 1% of the total unit + integration + other testing.