Prerequisites Basic computer literacy and a willingness to document experiments.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Test levels and test types Equivalence classes and boundaries Risk and prioritisation Acceptance criteria and traceability Performance Testing specialization: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Tools Test management board Issue tracker Requirements checklist
Hands-on exercise Write test cases for normal, boundary and invalid input paths. Context for this route: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Suggested project A test plan with risk-ranked cases and acceptance coverage. The outcome must directly demonstrate Performance Testing, not merely list tools.
Learning resources Completion criteria Each test has preconditions, steps and expected results. Evidence must be reproducible and tied to Performance Testing.
Next: Exploratory & manual testing
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Exploratory charters State transitions and edge cases Reproduction steps and evidence Regression selection Performance Testing specialization: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Tools Browser/devtools Mobile or desktop test device Bug tracker
Hands-on exercise Perform a time-boxed exploratory session and file a reproducible defect. Context for this route: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Suggested project A bug report pack with severity and environment evidence. The outcome must directly demonstrate Performance Testing, not merely list tools.
Learning resources Completion criteria Another tester can reproduce the issue from the report. Evidence must be reproducible and tied to Performance Testing.
Next: API contracts & service testing
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn HTTP methods and status semantics Schema and contract validation Auth and permission testing Negative and idempotency cases Performance Testing specialization: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Tools Postman or curl OpenAPI API test runner
Hands-on exercise Automate positive and negative API checks against a test service. Context for this route: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Suggested project An API regression collection with environment-safe test data. The outcome must directly demonstrate Performance Testing, not merely list tools.
Learning resources Completion criteria The suite verifies contracts and never uses production secrets. Evidence must be reproducible and tied to Performance Testing.
Next: Browser/mobile automation architecture
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Page/component object patterns Selectors and wait strategies Fixtures, mocks and test data Cross-browser/device matrix Performance Testing specialization: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Tools Playwright/Selenium/Appium as relevant CI runner Test data factory
Hands-on exercise Automate a critical user flow and introduce one asynchronous UI delay. Context for this route: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Suggested project An end-to-end suite with readable fixtures and reports. The outcome must directly demonstrate Performance Testing, not merely list tools.
Learning resources Completion criteria The tests remain stable under expected timing variation. Evidence must be reproducible and tied to Performance Testing.
Next: Performance, load & resilience
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Load profiles and concurrency Latency percentiles and throughput Soak and spike tests Dependency degradation Performance Testing specialization: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Tools k6 or JMeter Browser performance tools Metrics dashboard
Hands-on exercise Run a bounded load test in a controlled environment and identify the first bottleneck. Context for this route: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Suggested project A performance report with workload, results and limitations. The outcome must directly demonstrate Performance Testing, not merely list tools.
Learning resources Completion criteria The report records reproducible conditions and meaningful percentiles. Evidence must be reproducible and tied to Performance Testing.
Next: Security, accessibility & compatibility
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn OWASP test cases Keyboard and screen reader paths Browser/device compatibility Privacy and permission checks Performance Testing specialization: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Tools OWASP testing guidance Accessibility inspector Device/browser matrix
Hands-on exercise Test a form for keyboard, labels, access control and unsafe input handling. Context for this route: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Suggested project A cross-cutting quality checklist with actionable findings. The outcome must directly demonstrate Performance Testing, not merely list tools.
Learning resources Completion criteria Critical security and accessibility findings have reproducible evidence. Evidence must be reproducible and tied to Performance Testing.
Next: CI quality gates & defect analytics
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Pipeline test stages and artefacts Flaky test diagnosis Coverage and escaped defects Release risk signals Performance Testing specialization: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Tools GitHub Actions/Jenkins JUnit report format Test dashboard
Hands-on exercise Add a test stage that blocks a known failing build and preserves results. Context for this route: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Suggested project A CI quality gate with ownership and flake policy. The outcome must directly demonstrate Performance Testing, not merely list tools.
Learning resources Completion criteria Failures are actionable and releases cannot bypass required checks accidentally. Evidence must be reproducible and tied to Performance Testing.
Next: Capstone: quality engineering system
✓ Mark this node as complete
Prerequisites Completion of the previous stage and a working local practice environment.
Learning objectives Explain the stage-specific model and its limits Apply the listed concepts using a controlled exercise Record results, failure cases and a reproducible evidence trail
Topics to learn Risk-based strategy Manual, API and automated coverage Performance/security/accessibility Release readiness and reporting Performance Testing specialization: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Tools Chosen test stack CI service Test environment
Hands-on exercise Run a release-readiness session and present the risk-based go/no-go decision. Context for this route: Track-specific focus: Performance Testing. Use the tools and standards named in this path; avoid treating this route as a generic overview of QA & Software Testing.
Suggested project A test strategy, automation suite, performance evidence and defect summary. The outcome must directly demonstrate Performance Testing, not merely list tools.
Learning resources Completion criteria The quality decision is traceable to evidence and known residual risk. Evidence must be reproducible and tied to Performance Testing.
End of roadmap: Complete the final project and build your portfolio.
✓ Mark this node as complete