Systematically verifying and assuring software quality. Encompasses test design, automation, and process building to prevent defects and ensure product reliability.
QA Engineering verifies that software meets requirements and operates reliably for users. It spans manual testing through automated test design, performance and security testing, CI/CD pipeline integration, quality metrics management, and organization-wide quality strategy. From writing your first bug report to architecting enterprise quality engineering culture, it has clear growth stages mapped to the ISTQB certification scheme and SFIA 8 testing responsibility levels.
You learn the Software Testing Life Cycle (STLC) and write simple test cases based on requirements, including preconditions, steps, and expected results. You perform manual testing to find defects and write bug reports with reproduction steps, expected vs. actual results, and screenshots. You understand the difference between testing and QA, and can classify defect severity and priority. Corresponds to the SFIA Follow stage.
What Comes Next
If you've checked off most of this list, you're ready for the Systematic stage, applying systematic test design techniques and managing requirements traceability. Bandura(1977)'s Social Learning theory suggests watching test case writing demonstrations and studying bug report examples builds the confidence to test effectively on your own.
A global ICT/digital competency framework defining testing skills across 6 responsibility levels (Follow→Initiate), directly used to design autonomy, influence, and complexity boundaries between QA Engineering levels.
A three-tier certification scheme (Foundation→Advanced→Expert) defining the official competency progression path for QA professionals, providing the basis for level boundaries and checklist items.
Defines core tasks, skills, and knowledge areas for QA roles with importance scales, providing specific behavioral and competency evidence for checklist items.
The canonical textbook authored by ISTQB syllabus co-developers, detailing the testing knowledge body at each tier (Foundation → Advanced → Expert), providing scholarly evidence for level-specific competency scope and checklist difficulty.
An IEEE-defined software engineering competency model that specifies 5 proficiency levels (Technician → Leader) across competency areas including testing, used as scholarly cross-validation evidence for QA level boundaries.
