Test a real website
Explore a public website for an hour, then write a test plan and three well-formed bug reports.
Find problems before users do, then automate the checks so quality keeps up with every release.
You have reached the end of the beginner stages. Prove what you learned with a project.
You have reached the end of the intermediate stages. Prove what you learned with a project.
You have reached the end of the advanced stages. Prove what you learned with a project.
Explore a public website for an hour, then write a test plan and three well-formed bug reports.
Design boundary and equivalence tests for a sign-up form and explain why each one matters.
Automate the five most important user journeys of a demo shop and run them headless.
Test a public API for success, errors and missing permissions, with checks on every response.
Run unit, API and browser tests in CI with a readable report and screenshots on failure.
Load test a demo API, find where it slows down and recommend what to fix.
The same roadmap as a reading list: every stage, what each topic covers, and which ones are optional.
What testing can and cannot prove, test levels, and the balance between fast and slow tests.
Equivalence classes, boundary values and decision tables: fewer tests that catch more bugs.
Clear steps, expected and actual results, and evidence a developer can act on.
Agile, Scrum and where testing fits in each sprint.
Learn the product while testing it, guided by risks and a time-boxed mission.
Decide what to test, write repeatable cases and track coverage of the requirements.
Inspect pages, read console errors and watch network requests while you test.
Keyboard use, contrast, labels and screen reader basics.
JavaScript/TypeScript or Python: enough to write and maintain automated tests.
How pages are built, so you can find elements and understand UI bugs.
Keep tests in version control and review them like product code.
Check what the application really saved and set up test data.
Drive real browsers, wait for the right things and keep tests stable.
A popular alternative for front-end end-to-end and component tests.
The long-standing standard, common in existing test suites.
Test small pieces of code quickly, close to where bugs are made.
Check endpoints directly: status codes, data, errors and permissions.
Real devices, emulators, flaky networks and app store builds.
Reliable, isolated data and environments so tests do not depend on luck.
Check that services agree on their APIs without running everything together.
Run the right tests on every change and report results the team will read.
Measure response times under load and find the breaking point.
Common web weaknesses and how to check for them safely.
Decide what to automate, measure quality and fix tests that fail at random.
They plan and run tests, report bugs clearly, automate repeated checks and help the whole team build quality into each release.
You can start with manual testing, but most roles now expect some automation. Learning one language and one automation tool greatly widens your options.
No. Certifications such as ISTQB Foundation can help a CV, but employers value practical skill and a portfolio of test work more.
© 2026 KamerLink. All rights reserved.