English Cho QA

Title Formula: [Module] Action/State — Impact

Phrases hay dùng trong bug report:

• Steps to Reproduce"Navigate to / Open / Click / Enter / Select / Submit / Verify" — dùng imperative form, rõ ràng, từng action riêng lẻ
• Expected vs Actual"Expected: User should be redirected to dashboard. Actual: User remains on login page with no error message."
• Reproducibility"Consistently reproducible." / "Intermittent — reproduced 3 out of 5 attempts." / "Reproduced once, unable to reproduce again."
• Environment details"Tested on: Chrome 120 / Windows 11 / Staging environment / Build v2.5.1 / Account: qa-test@example.com"
• Impact statement"This blocks users from completing checkout, directly impacting revenue." / "Cosmetic issue, no functional impact."

Testing Terms:

• reproduce / repro"I can consistently reproduce this on Chrome." / "Unable to repro with provided steps."
• intermittent / flaky"Intermittent issue — occurs approximately 30% of the time." / "Flaky test — passes locally but fails in CI."
• workaround"As a workaround, users can clear cache and retry." / "No workaround available."
• regression"This is a regression — feature worked correctly in v2.4." / "No regression observed in related areas."
• blocker / showstopper"This is a release blocker — checkout is completely broken." / "Critical blocker preventing QA sign-off."
• scope / out of scope"Search optimization is out of scope for this sprint." / "Accessibility testing is in scope per test plan."
• sign off / sign-off"QA has signed off on Sprint 12." / "Awaiting PM sign-off before deployment."
• edge case / corner case"Edge case: what happens when cart quantity exceeds available stock?"
• as per spec / per design"Per spec (AC-003), the system should display an error — this behavior is a bug." / "Working as designed — confirmed with BA."
• deferred / backlogged"This minor issue has been deferred to the next sprint by PM decision."

Process Terms:

• kick off"Let's kick off Sprint 5 testing Monday morning." / "Kick-off meeting: 9 AM tomorrow."
• sign off"QA has signed off on the build." / "Need PM sign-off before deployment."
• triage"Let's triage these bugs and decide priority." / "Bug triage meeting: Wednesday 2 PM."
• loop in / loop someone in"Please loop in the dev lead on this critical bug." / "I'll loop Sarah in on this conversation."
• escalate"I need to escalate this — it's been 3 days without a fix." / "Escalating to leadership given the release impact."

Standup Template:

Ví dụ standup variations:

• "Yesterday I completed testing for US-234 (search filters) — found 2 bugs, both logged. Today I'm testing US-235 (cart persistence). No blockers."
• "Yesterday I finished regression for Sprint 14 — 142 tests passed, 3 failed (minor). Bugs logged. Today I'll verify yesterday's hotfix. Blocker: hotfix hasn't been deployed to staging yet."
• "No testing yesterday — spent time reviewing Sprint 15 user stories and writing test cases. Today continuing test case writing. I have a question about US-240 acceptance criteria — can we discuss after standup?"

Meeting Phrases:

• Clarifying requirements"Could you clarify the expected behavior when...?" / "I'm not clear on the acceptance criteria for... Can you walk me through the expected flow?"
• Raising concerns"I'd like to flag a risk here..." / "I'm concerned that with the current timeline, we may not have enough time to..."
• Disagreeing professionally"I see it differently — according to the spec..." / "I respectfully disagree — here's my evidence..."
• Asking for more time"I need another day to complete thorough testing of the payment flow — can we adjust the timeline?"

Go/No-Go Recommendation Structure (5 phút):

1. Summary (30s): "Testing for Sprint 15 is complete. My recommendation is Go / No-Go."
2. Numbers (1 min): "We ran 180 tests. 171 passed (95%). 9 failed — 0 Critical, 1 Major, 8 Minor."
3. Key Issues (2 min): "The Major bug [PROJ-460] affects search filtering for users with premium accounts. It has a workaround but impacts UX."
4. Risk (1 min): "If we deploy with this bug, approximately 15% of premium users will experience degraded search. Risk level: Medium."
5. Recommendation (30s): "My recommendation: deploy with the known bug, monitor customer support tickets, and prioritize fix in Sprint 16."