Testing is all about confidence
Testing - manual or automated - is about building confidence.
If we deploy this change or release this feature, are we confident it will work as expected and not cause regressions elsewhere?
What if someone asked you on a scale between one and ten?
From an automated perspective, have you written enough tests for the feature to be confident it works?
If you're fixing a bug, do you have a test that reproduces the bug that was originally failing but now passing since you've added the fix?
Do the tests have enough assertions, and have you covered enough use cases and scenarios?
Here's the thing
You can utilise code coverage metrics, but no hard rule says that the feature will work once x percentage is covered. Something with 100% coverage can still contain bugs.
For me, it's about the answer to the question:
If we deploy this change, how confident are you that it will work as expected?
- Oliver
