Testing is not just technical — it is human
How testers communicate, how developers receive feedback, and how teams view failure directly impacts defect detection and product quality. Ignoring the psychology of testing leads to defensiveness, hidden defects, and poor collaboration.
// example: github pull request review
CTFL 4.0.1 Psychology of Testing
- Independent testing is valuable — Testers not involved in development bring a fresh perspective and reduce author bias.
- Constructive communication — Focus on the product, not the person. Use facts and observations, not blame.
- Tester mindset — Testers should be curious, critical, and detail-oriented, while remaining collaborative and professional.
- Author bias — Developers may overlook defects in their own code due to familiarity and unconscious assumptions.
- Courteous reporting — Defect reports should be clear, objective, and respectful to encourage open communication.
// tip: Exam Tip: Remember that "independent testing" does not mean "adversarial". Independence improves objectivity, but collaboration remains essential.
| Element | Poor Example | Improved Example | Psychology Principle |
|---|---|---|---|
| Title | "Checkout is totally broken" | "Payment button unclickable on Safari 16.4 mobile" | Specific, factual, not emotional |
| Steps | "Just try to pay, it fails" | "1. Add item to cart 2. Proceed to checkout 3. Tap Pay on Safari iOS 16.4" | Reproducible, clear |
| Expected | "It should work" | "Payment modal should open and accept card input per REQ-PAY-03" | Tied to requirement |
| Actual | "Doesn't work" | "Tap has no effect; console shows 'undefined is not a function'" | Objective evidence |
| Tone | "This is a critical bug, fix now" | "Severity: High. This blocks mobile Safari users from completing purchase." | Professional, impact-focused |
Independence
Fresh perspective reduces author bias; choose level based on context
// Exam insight
Independence has trade-offs; context determines the right level.
| Independence Level | Who Tests | Pros | Cons |
|---|---|---|---|
| No independence | Developers test their own code | Fast feedback, deep technical knowledge | Author bias, may miss own defects |
| Some independence | Developers test each other's code (peer testing) | Fresh eyes, knowledge sharing | Still within dev team mindset |
| More independence | Dedicated testers within dev team | Professional testing skills, closer collaboration | May still be influenced by team goals |
| Full independence | Separate test team or external testers | Maximum objectivity, user perspective | Potential communication gaps, slower feedback |
// warning: Exam Trap: "Independent testing is always better" is FALSE. CTFL teaches that independence has benefits but also trade-offs. The right level depends on context, risk, and project constraints.
Exam Practice Questions
// ctfl 4.0.1 style — select an answer to reveal explanation