Selenium Testing
Lab Curriculum.

BUG FOUND: testers who write scripts but cannot reproduce or stabilise real failures.

$ step-01 brushup // weeks 1–2 — Topics taught:

1. Selenium WebDriver locators: id, CSS, XPath, and when each breaks.
2. Explicit vs implicit waits, and flakiness caused by timing.
3. Page Object Model structure for a maintainable suite.
4. TestNG/JUnit basics, assertions, and test data setup.
5. Reading application logs and screenshots to reproduce a failure.
6. Writing a clear bug report: steps, expected vs actual, evidence.

$ step-02 debug // weeks 3–4 — Production Debugging. Tools: Selenium WebDriver, TestNG/JUnit, browser DevTools, Git.

• BUG #1: Reproduce a reported checkout bug from a ticket with incomplete steps — record exact reproduction steps and evidence.
• BUG #2: Fix a flaky suite that fails 1 in 5 runs — find the timing / data cause, stabilise it, show 10 consecutive clean runs.
• BUG #3: Repair broken selectors after a UI change — update locators to stable ones, not brittle absolute XPaths.
• BUG #4: Triage 10 failures and classify each as app bug, test bug, or environment/data issue, with evidence.

$ step-03 navigate // weeks 5–7 — Codebase / System Navigation:

• Navigate a large test suite plus the application codebase; for each failure, decide app code vs test code vs data.
• Refactor a duplicated, hard-to-maintain suite into Page Objects with shared helpers.
• Add regression coverage for a previously escaped bug, with data setup that does not leak between tests.
• Review a peer's test code for false positives, missing assertions, and brittle locators.

$ step-04 ship // weeks 8–9 — Shipping Features: capstone — a stable automation suite for a real application flow, with a bug report pack and an execution summary.

$ ship → PROOF — exact output: automation suite repo, execution report (10 clean runs), and a bug report pack with reproduction evidence for each bug found.

$ run --lab selenium-testing → ✓ SHIPPED, job-ready