Designing monitoring
Monitoring involves checking system performance metrics and regularly running simple automated checks. These overlap with tests you should have run before release, but they fulfill a different function since they find test escapes and operational issues affecting your live environment. Since monitoring checks are run after a system’s release, they are not tests as such but have so much overlap with your test plan that they’re worth considering here.
Being a tester, you’ll interact with the monitoring in two ways:
- Firstly, you’re a user, using monitoring to check for errors on your test system. New code must complete its test run without causing errors in the monitoring system.
- Secondly, you need to ensure that every new feature has relevant monitoring. If your system can now fail in a new way that you’re blind to, that’s a bug that needs fixing.
Monitoring requires a dedicated system that gathers all...
