Source: Levelica Canonical: https://www.levelica.com/en/guides/qa-engineering # QA Engineering ## Summary Assuring software quality through test design, automation, and process building that prevents defects. ## Description 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. --- ## Level Overview | Level | Proficiency Stage | Hashtags | | ----- | ----------------- | ----------------------------------------------------------------- | | Lv.1 | Foundation | #TestCase #BugReport #ManualTesting #STLC | | Lv.2 | Systematic | #TestDesign #BoundaryValue #EquivalencePartitioning #Traceability | | Lv.3 | Automated | #TestAutomation #UIAutomation #CICD #ISTQB-CTFL | | Lv.4 | Analytical | #PerformanceTesting #SecurityTesting #RiskBasedTesting #Metrics | | Lv.5 | Strategic | #QAStrategy #TestArchitecture #Mentoring #ISTQB-CTAL | | Lv.6 | Organizational | #QualityEngineering #ShiftLeft #OrgTransformation #ISTQB-Expert | | Lv.7 | Visionary | #ContinuousTesting #QAMethodology #ISO29119 #QALegacy | > Proficiency stages are an expanded mapping of the ISTQB certification scheme (Foundation→Advanced→Expert) cross-referenced with SFIA 8 testing responsibility levels (Follow→Initiate) to 7 levels. > **Cross-Validation:** Three independent reference frameworks converge on the same level boundaries. (1) ISTQB's Foundation→Advanced transition and SFIA 8's Follow→Apply transition align at the L2↔L3 boundary (systematic test design→automation framework building). (2) O\*NET's intermediate→advanced task complexity transition and IEEE SWECOM's Practitioner→Leader competency transition converge at the L4↔L5 boundary (non-functional testing→QA strategy establishment). (3) ISTQB Expert level and SFIA's Initiate/Set Strategy level align at the L6↔L7 boundary (organizational quality engineering→methodology creation). > **Integrated Framework:** This guide's 7-level structure is not a mapping of a single rating system but the integration of four independent axes. The ISTQB syllabus provides the **test technique axis** (complexity of test methodology, from manual testing to non-functional and security testing). SFIA 9 software testing competency provides the **automation maturity axis** (maturity of test infrastructure, from script writing to CI/CD-integrated automation). The TMMi process maturity model provides the **quality culture axis** (organizational approach to quality, from individual testing to organizational quality strategy). And practitioner expertise provides the **risk judgment axis** (quality intuition not captured by frameworks, including defect instinct, release risk judgment, and quality metric misuse detection). Each level boundary is determined at the intersection of these four axes. --- ## Level 1 #TestCase #BugReport #ManualTesting #STLC ### Summary Writing test cases and clearly reporting defects to begin in QA. ### Description 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. ### Checklist - [ ] Can write test cases with preconditions, steps, and expected results based on requirements documents - [ ] Can write bug reports including reproduction steps, expected results, actual results, and screenshots - [ ] Can classify defects by severity (Critical, Major, Minor, Trivial) and priority - [ ] Can explain the phases of the Software Testing Life Cycle (STLC) - [ ] Can register defects in a bug tracking tool (e.g., Jira, Bugzilla) and update their status - [ ] Can distinguish between positive testing (happy path) and negative testing (error path) and perform both > 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. --- ## Level 2 #TestDesign #BoundaryValue #EquivalencePartitioning #Traceability ### Summary Applying systematic test design and managing traceability. ### Description You apply black-box test design techniques such as Equivalence Partitioning, Boundary Value Analysis, and Decision Tables to systematically achieve test coverage. You create a Requirements Traceability Matrix (RTM) to ensure no requirement goes untested. You write test plans and compile test execution results into structured reports with metrics. ### Checklist - [ ] Can apply Equivalence Partitioning to design test cases using representative values from input domains - [ ] Can apply Boundary Value Analysis to write tests that detect defects at boundary conditions - [ ] Can use Decision Tables to exhaustively test combinations of complex conditions - [ ] Can create a Requirements Traceability Matrix (RTM) to verify that all requirements are covered by tests - [ ] Can write test plans including scope, schedule, resources, and risks - [ ] Can compile test execution results into reports with metrics such as pass rate and defect density > If you've checked off most of this list, you're ready for the Automated stage, building test automation frameworks and integrating automated tests into CI/CD pipelines. Kolb(1984)'s Experiential Learning theory suggests repeating the cycle of designing tests, observing execution results, reflecting, and applying improved test strategies builds deeper QA skill. --- ## Level 3 #TestAutomation #UIAutomation #CICD #ISTQB-CTFL ### Summary Building test automation frameworks and integrating them into CI/CD. ### Description You use test automation tools such as Selenium, Cypress, or Playwright to automate UI and API tests. You apply maintainable test code patterns like Page Object Model. You integrate automated tests into CI/CD pipelines so that regression tests run automatically on every code change. You possess ISTQB CTFL-level testing knowledge. Corresponds to the SFIA Apply stage. ### Checklist - [ ] Can write and execute UI automation tests using a UI automation tool (e.g., Selenium, Cypress, or Playwright) - [ ] Can automate REST API tests to verify status codes, response structures, and error handling per endpoint - [ ] Can apply maintainable test code patterns such as Page Object Model - [ ] Can integrate automated tests into CI/CD pipelines to run regression tests on every commit - [ ] Can manage test data independently to ensure stable execution without interference between tests - [ ] Can generate automated test execution reports and analyze failure root causes - [ ] Can explain test types (unit, integration, system, acceptance) and test levels at ISTQB CTFL level > If you've checked off most of this list, you're ready for the Analytical stage, performing performance testing, security testing, risk-based testing, and analyzing quality metrics. Vygotsky(1978)'s Zone of Proximal Development suggests tackling automation framework building or CI/CD integration tasks just beyond your current ability, with senior QA engineer review, builds skill fastest. --- ## Level 4 #PerformanceTesting #SecurityTesting #RiskBasedTesting #Metrics ### Summary Performing performance and security tests and prioritizing by risk. ### Description You design and execute load and stress tests using tools like JMeter, k6, or Gatling to measure system performance limits. You run security vulnerability tests based on the OWASP Top 10. You apply Risk-Based Testing strategies to prioritize tests by business impact. You collect and analyze quality metrics such as defect escape rate and automation coverage to support quality decisions. Corresponds to the SFIA Enable stage. ### Checklist - [ ] Can design load tests using a load testing tool (e.g., JMeter, k6, or Gatling) and measure concurrent users, response time, and throughput - [ ] Can perform security vulnerability tests for web applications based on OWASP Top 10 items - [ ] Can apply Risk-Based Testing strategies to prioritize tests by business impact and defect probability - [ ] Can collect quality metrics (defect escape rate, automation coverage, test execution time) and visualize them on dashboards - [ ] Can perform accessibility testing to verify compliance with WCAG 2.1 AA criteria - [ ] Can structure exploratory testing sessions to detect defects that scripted tests may miss - [ ] Can analyze test result data to identify defect hotspots and recommend test strategy adjustments > If you've checked off most of this list, you're ready for the Strategic stage, establishing QA strategy, designing test architecture, and mentoring junior QA engineers. Ericsson(1993)'s Deliberate Practice theory suggests training specifically on your weak areas like performance test design, security test execution, and risk-based test prioritization. --- ## Level 5 #QAStrategy #TestArchitecture #Mentoring #ISTQB-CTAL ### Summary Setting QA strategy, designing test architecture, mentoring juniors. ### Description You establish QA strategy at the project or product level and design test architecture aligned with the test pyramid. You lead technical decisions for automation frameworks, test environment strategy, and test data management. You mentor 3 or more junior QA engineers and manage test code quality through code reviews. You collaborate with development teams to improve testability through dependency injection and contract testing. You possess ISTQB CTAL-level expertise. ### Checklist - [ ] Can evaluate automation framework tech stacks and select technologies matching project requirements - [ ] Can automate test environment provisioning to ensure independent and reproducible test execution - [ ] Can mentor 3 or more junior QA engineers and review their test designs and automation code - [ ] Can collaborate with development teams to propose testability improvements such as dependency injection and contract testing - [ ] Can define release quality gates and establish quality criteria for deployment decisions - [ ] Can write data-driven QA process improvement proposals and measure their effectiveness after implementation - [ ] Can intuitively predict areas likely to have defects from code changes and achieve a 50% or higher discovery rate in exploratory testing - [ ] Can assess the severity and fix cost of defects found just before release, make the judgment between delaying release and post-release patching, and document the reasoning > If you've checked off most of this list, you're ready for the Organizational stage, building organization-wide quality engineering culture and embedding shift-left strategies. Schön(1983)'s Reflective Practice theory suggests improving team quality standards by reflecting in real time as you establish QA strategy and design test architecture. --- ## Level 6 #QualityEngineering #ShiftLeft #OrgTransformation #ISTQB-Expert ### Summary Embedding enterprise quality engineering culture and shift-left. ### Description You lead the organizational transformation from QA as a late-stage verification activity to quality engineering embedded throughout the SDLC. You introduce shift-left strategies to embed quality from the requirements phase. You design QA organization structure, hiring criteria, and competency evaluation frameworks. You share QA knowledge with the industry through conference talks and technical blogs. You possess ISTQB Expert-level expertise and exert influence at the industry level. ### Checklist - [ ] Can introduce shift-left strategies and establish processes that embed QA perspectives into requirements and design reviews - [ ] Can design QA organization structures (centralized, embedded, hybrid) and recommend the model suited to organizational context - [ ] Can define QA engineer competency evaluation criteria, growth paths, and design hiring processes - [ ] Can present QA topics at external conferences or publish case studies on technical blogs - [ ] Can introduce chaos engineering to proactively verify fault tolerance in production environments - [ ] Can design organization-wide quality metrics frameworks and report quality status quantitatively to executives - [ ] Can identify cases where quality metrics (code coverage, defect density) are being misused, explain the limitations of these metrics to teams, and propose alternative indicators > If you've checked off most of this list, you're ready for the Visionary stage, creating new QA methodologies and establishing industry standards. Argyris & Schön(1978)'s Double-Loop Learning theory suggests questioning the assumptions behind quality engineering culture and shift-left strategy to innovate your organization's quality approach. --- ## Level 7 #ContinuousTesting #QAMethodology #ISO29119 #QALegacy ### Summary Creating new QA methodologies and standards, leaving a legacy. ### Description You push beyond the boundaries of existing testing paradigms to create new QA methodologies, tools, or frameworks. You participate in the development of international standards (ISO/IEC 25010, IEEE 829) or contribute to ISTQB syllabus revisions. Through books, papers, and open-source projects, you exert lasting influence across the entire QA field. You set the direction for QA engineering across generations. ### Checklist - [ ] Can create or co-design a new testing methodology or framework that gains industry adoption - [ ] Can participate in the development or revision of international standards (ISO/IEC 25010, IEEE 829) or ISTQB syllabi - [ ] Can publish books on QA or papers in peer-reviewed journals - [ ] Can create or make leading contributions to an open-source testing framework recognized as a standard tool by the community - [ ] Can deliver keynote speeches at international conferences or serve on program committees - [ ] Can design an organizational quality culture (shift-left testing, defect prevention vs detection balance, distributed quality ownership) and demonstrate reduced defect escape rates with quantitative evidence > If you've checked off most of this list, you're at the forefront of QA engineering, shaping how future generations of practitioners approach software quality. Bloom(1956)'s Taxonomy suggests that creating new testing methodologies or quality frameworks represents the highest cognitive level of Create, defining the field's direction through lasting standards. --- ## References - [SFIA 8 — Testing (TEST)](https://sfia-online.org/en/sfia-8/skills/testing) — SFIA Foundation - [ISTQB Certified Tester Scheme](https://istqb.org/certifications/) — International Software Testing Qualifications Board (ISTQB) - [O*NET — Software Quality Assurance Analysts and Testers (15-1253.00)](https://www.onetonline.org/link/summary/15-1253.00) — U.S. Department of Labor / O*NET - [Foundations of Software Testing: ISTQB Certification, 4th Edition](https://www.amazon.com/Foundations-Software-Testing-ISTQB-Certification/dp/1473764793) — Dorothy Graham, Rex Black, Erik van Veenendaal (Cengage) - [IEEE SWECOM — Software Engineering Competency Model](https://ieeecs-media.computer.org/media/education/swebok/swecom.pdf) — IEEE Computer Society