daily-email: add 2023-07-24
Testing is all about confidence
This commit is contained in:
parent
e58540eee6
commit
e2c4fdb100
30
src/content/daily-email/2023-07-24.md
Normal file
30
src/content/daily-email/2023-07-24.md
Normal file
|
@ -0,0 +1,30 @@
|
|||
---
|
||||
title: >
|
||||
Testing is all about confidence
|
||||
pubDate: 2023-07-24
|
||||
permalink: >
|
||||
archive/2023/07/24/testing-is-all-about-confidence
|
||||
tags:
|
||||
- automated-testing
|
||||
- test-driven-development
|
||||
---
|
||||
|
||||
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?
|
Loading…
Reference in a new issue