Skip to content

Commit 223282f

Browse files
authored
Typos
1 parent 3fce283 commit 223282f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

practices/testing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,13 +40,13 @@
4040
- Design for reproducibility
4141
- Tests should be idempotent and easily repeatable in any environment (local, test, staging, production).
4242
- Shift right, aka test in production
43-
- Testing does not stop at deployment-continuous validation in production is essential.
43+
- Testing does not stop at deployment: continuous validation in production is essential.
4444
- Implement real-time monitoring, synthetic checks, health probes, and user behavior tracking.
4545
- Use canary deployments and feature flags to support testing changes as they are deployed.
4646
- When safe to do so, employ chaos engineering to test system resilience under real-world failure conditions.
4747
- Instrument systems to detect anomalies, performance degradation, or unexpected behaviors automatically - to support good quality canary deployments.
4848

49-
In a high-throughput environment-where deploying at least once a day is the norm, adhering to the design for testability principle is paramount. The benefits include: 1) *faster feedback loops* – early testing catches issues when they are cheapest to fix, while testing later in the cycle ensures real-world readiness; 2) *increased confidence* – testing at all stages validates assumptions, improves system reliability, and supports safe, frequent releases; and 3) *higher quality by design* – systems built for testability are easier to maintain, scale, and evolve.
49+
In a high-throughput environment where deploying at least once a day is the norm, adhering to the design for testability principle is paramount. The benefits include: 1) *faster feedback loops* – early testing catches issues when they are cheapest to fix, while testing later in the cycle ensures real-world readiness; 2) *increased confidence* – testing at all stages validates assumptions, improves system reliability, and supports safe, frequent releases; and 3) *higher quality by design* – systems built for testability are easier to maintain, scale, and evolve.
5050

5151
- **Quality is the whole team's responsibility**
5252
- Education on testing and testing principles should be important to the whole team.

0 commit comments

Comments
 (0)