Stage 2 of 8 · 8 lessons · ~6 weeks
Manual testing done well
Turn requirements into test ideas with proven techniques, test with charters as well as cases, and write bug reports that developers can reproduce and fix.
Start: Analysing requirements and acceptance criteriaLessons· one lesson for each topic, in this order
- 1Analysing requirements and acceptance criteriaLesson
- 2Partitions, boundaries and decision tablesLesson
- 3Test cases and checklistsLesson
- 4Exploratory testing with chartersLesson
- 5Bug reports that get fixedLesson
- 6Severity, priority and the bug life cycleLesson
- 7Smoke, sanity and regression testingLesson
- 8Test management and tracking toolsLesson
Do this
- Take three user stories from an app you know and write the questions you would raise before testing.
- Design tests for two input rules with equivalence partitioning and boundary values.
- Build one decision table for a rule with at least two conditions.
- Write 15 test cases or checklist items for one feature of a practice site.
- Run two 60-minute exploratory sessions with written charters and notes.
- Write five bug reports with steps, expected and actual results, environment and a screenshot or video.
- Ask a friend to reproduce one report using only what you wrote, and fix what confused them.
- Set up a free Jira or spreadsheet board with your cases, a test run and linked bugs.
Start with
- GuideFreeISTQB Certified Tester Foundation Level (CTFL) v4.0
ISTQB · Beginner
Chapter 4 of the free syllabus covers partitions, boundaries, decision tables and state transitions with worked examples
Practise
Keep handy
Also worth your time
A plain, proven checklist for titles, steps and expected results from one of the largest open bug trackers
Before moving on: A test pack for one feature of a practice app: 15 to 20 test cases or checklist items built with partitions and boundaries, notes from two 60-minute exploratory sessions, and five well-written bug reports with evidence.
Manual testing is not the lesser half of QA. The testers I see hired fastest can take a vague story, ask the right questions and write a bug report a developer reproduces in a minute. Practise on the-internet and Restful-booker, which contain bugs on purpose, and get someone to try reproducing your reports.