QA Exercise 1

Buggy Login Form

Exercise · Bug Reporting (Buggy Login)

QA · Speaking

Oral task: investigate a buggy login demo and present a spoken bug report using target QA vocabulary.

Scenario:
You have a demo login page. First try:
  Email: test@example.com
  Password: password123
Then try a wrong password, e.g., 12345.

Goal:
Prepare an oral bug report with:
1) Title
2) Steps to reproduce
3) Expected result
4) Actual result
5) Severity / Priority

🎯 Instructions (Oral) task flow

Open the buggy login page and attempt to log in with the valid credentials above.
Attempt again with a clearly wrong password.
Speak your bug report to the class using clear transitions: First, then, next, finally.
Conclude with your assessment of severity and priority and a short recommendation.

📖 Vocabulary definitions

bug / defect / issue — an error or flaw in software that causes incorrect behavior.
steps to reproduce (STR) — the exact sequence needed to trigger the bug.
expected result — what should happen if the system works correctly.
actual result — what really happens when you test.
severity — how serious the impact is on the system or users (e.g., critical, major, minor).
priority — how quickly the bug should be fixed (e.g., P0, P1, P2).
blocker — a defect that prevents testing or release from proceeding.
reproducible — a bug that can be triggered consistently with the same steps.
regression — a feature that breaks after a change or release.
environment — the context where testing runs (browser, OS, version).
negative test — a test using invalid or unexpected input to ensure correctness.
edge case — a rare or extreme input/condition revealing hidden issues.
input validation — checks that data entered by users is acceptable and safe.
authentication — verifying a user’s identity (e.g., login).
authorization — verifying a user’s permissions after login.
sanitization — cleaning inputs to prevent security risks.
test case — a defined check with preconditions, steps, and expected result.
acceptance criteria — conditions a feature must meet to be accepted as done.

🧩 Collocations natural pairings

reproduce a bug / consistently reproduce the issue
log or raise a ticket (in Jira, GitHub, etc.)
set severity / assign priority
capture screenshots / collect logs
verify the fix / retest after a patch
run smoke tests / execute regression tests
meet acceptance criteria / sign off a release
escalate a blocker / triage defects

🗣️ Idioms & Phrasal Verbs natural speech

run into (a bug) — encounter unexpectedly.
track down — find the source of a problem.
narrow down — reduce the possible causes.
rule out — eliminate a suspected cause.
roll back — revert to a previous version.
spin up (an environment) — start a new instance quickly.
lock down (security) — make more secure or restricted.
on the same page — sharing the same understanding.
fall through the cracks — get overlooked or forgotten.
iron out the bugs — fix remaining problems.

🎤 Model Answer (spoken style) example

Spoken delivery:
“I ran into a critical security bug. When I try to log in with the wrong password, the system still authenticates me. I expected an error message instead. I can reproduce this consistently, so I’m logging it as a blocker with P0 priority. We should roll back the last change or ship a hotfix to lock down authentication, then verify the fix with negative tests and a short regression suite.”