About this course
What you are signing up for
Every team ships bugs. The ones that ship fewer have somebody who knows how to look for them properly — not by clicking around hoping, but by reading a feature and knowing where it is likely to fall over.
This is that skill, from nothing. You will learn what testing actually is, how to write a test case somebody else can follow, how to find defects on purpose, and how to log one so clearly that a developer can fix it without asking you a single question. The last part matters more than people expect: a bug nobody can reproduce is a bug nobody fixes.
It is virtual and self-paced, so you fit it around your week. Several sections are practical — you test a real application and file real defect reports, rather than only reading about it.
By the end
What you will be able to do
✓Explain what software testing is, and where manual and automated testing each earn their keep
✓Read a requirement and write test cases that cover it — including the cases people forget
✓Tell the difference between a test case, a test scenario and a test plan, and write all three
✓Apply the core test design techniques: equivalence partitioning, boundary values and error guessing
✓Find defects in a real application on purpose rather than by accident
✓Write a defect report a developer can act on without coming back to ask you anything
✓Run through the software testing life cycle and say what happens at each stage
✓Know what a QA role actually involves day to day, and what to learn next
The plan
What we cover
-
01
Day 1 — What testing actually isWhy software fails, what a tester is really for, and the difference between QA, QC and testing. Manual vs automated, and why the answer is both.
-
02
Day 2 — The software testing life cycleRequirement analysis, planning, case design, environment setup, execution, closure. Where testing sits inside how software actually gets built.
-
03
Day 3 — Reading a requirement like a testerTurning a vague feature description into a list of things that could go wrong. The questions to ask before a single test is written.
-
04
Day 4 — Writing test cases (practical)Steps, expected results, preconditions, test data. You write a full set for a real feature and get it reviewed.
-
05
Day 5 — Test design techniquesEquivalence partitioning, boundary value analysis, decision tables and error guessing — how to cover more with fewer tests.
-
06
Day 6 — Types of testingFunctional, regression, smoke, sanity, integration, UAT. What each one is for and when it is run.
-
07
Day 7 — Hunting defects (practical)You are given a working application with real bugs in it. Find them.
-
08
Day 8 — Writing a defect report that gets fixedTitle, steps to reproduce, expected vs actual, severity vs priority, evidence. The single most valuable thing on this course.
-
09
Day 9 — Testing on the web and on a phoneBrowser and device coverage, responsive checks, and the basics of testing an API without writing code.
-
10
Day 10 — The QA role, and what to learn nextWhat the job looks like day to day, the tools teams actually use, and a route into automation from here.
A collaboration
Built together, by two teams.
Each side runs the part it is best at. You get one course.
How it works
Three steps, and none of them cost anything
- 1Create your Webbo3 account, or sign in to the one you have.
- 2Fill in one application form. It takes about three minutes.
- 3Admissions approves your place and your course dashboard opens.