What this course is
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.
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
What you will cover
1 level, taught in order.
Explain how websites, apps, servers, APIs and databases fit together — and trace what really happens when a user clicks LoginOpen DevTools on any page and read the Elements,...
Who teaches it
Apply for this course
Apply for this courseApplying is free. You choose how to pay on the next screen, and your tutor decides on your place.