Test Cases and Bug Reports in Plain English

Why this matters

Vague bugs (“login broken”) waste days. Clear steps, expected vs actual, and environment details help developers in Pune or remote teams fix faster — and show interviewers you can communicate.

What you will learn

You will use a simple template: id, title, preconditions, steps, expected, actual (for bugs), severity. No enterprise tool required — Markdown or a sheet is enough.

How to do it

Keep language respectful. Never put real customer OTP or passwords in screenshots you share outside the team.

Steps (do these in order)

1. Step 1 — Case template. TC-ID, Title, Preconditions, Steps (numbered), Expected result. One behaviour per case.
2. Step 2 — Write three cases. Valid login, wrong password, blank email. Use LearnKart as the product name.
3. Step 3 — Bug template. Title, Steps to reproduce, Expected, Actual, Environment (browser/OS), Severity (blocker/major/minor), Attachments.
4. Step 4 — Rewrite a bad bug. Turn “pay button weird” into a full report with steps and a fictional order id.
5. Step 5 — Bilingual note. If your team mixes Hindi/Marathi/English, keep Steps in simple English and add one clarifying line in the local language if needed.

Practice

• Save TC-001…003 in docs/test-cases.md.
• File one practice bug for “error message shows technical stack trace to user”.