← Volver al examen

Guía de estudio gratuita

Quality Assurance (QA) Engineer — Free Curriculum

This free curriculum covers every domain assessed in the Oxford Certified QA Engineer examination: testing principles, test levels and types, static testing, test design techniques, planning and risk, test cases and defects, regression and automation, API, performance, security and accessibility testing, data and environments, agile and DevOps testing, and quality metrics. Read each chapter, note the key points, and then sit the 75-question examination.

¿Listo? Haz el examen gratis 95 min · 75 preguntas
Capítulo 1

Testing principles and quality

Quality assurance focuses on processes that prevent defects; quality control finds defects in products. A human error introduces a defect in code, which may cause a failure when executed. Testing shows the presence of defects but cannot prove their absence, and exhaustive testing is impossible.

Defects cluster in a few modules; repeating the same tests stops finding new defects (the pesticide paradox); testing is context dependent; and early testing is cheaper. Independent testers find defects authors overlook, while QA engineers help the whole team build quality in.

  • QA vs QC
  • Error, defect, failure
  • Seven testing principles
  • Independence and collaboration
Idea clave: Quality is built in, not tested in — but testing reveals the truth.
Capítulo 2

Test levels and types

Unit testing checks components in isolation; integration testing checks interfaces; system testing evaluates the integrated system against requirements; acceptance testing confirms the system meets business needs.

Functional testing checks what the system does; non-functional testing evaluates performance, usability, reliability and security. Confirmation testing verifies a fix; regression testing checks that changes have not broken existing functionality. Smoke tests quickly confirm a build is stable enough to test.

  • Unit, integration, system, acceptance
  • Functional vs non-functional
  • Confirmation vs regression
  • Smoke tests
Idea clave: Each test level catches different kinds of defects.
Capítulo 3

Static testing

Static testing examines requirements, designs and code without executing them, through reviews and static analysis. Early reviews find ambiguities and missing requirements, reduce rework and improve shared understanding.

Static analysis tools detect coding issues automatically, complementing dynamic testing.

  • Reviews of requirements and code
  • Static analysis tools
  • Cheapest defects to fix
  • Shared understanding
Idea clave: The cheapest defect is the one never coded.
Capítulo 4

Test design techniques

Black-box techniques include equivalence partitioning (one value per group), boundary value analysis (edges such as 17, 18, 65 and 66 for an 18–65 range), decision tables for combinations of rules, and state transition testing for state-dependent behaviour such as account lockouts. Pairwise testing covers every pair of parameter values with fewer combinations.

White-box techniques measure statement coverage and branch (decision) coverage; full statement coverage does not guarantee correctness. Experience-based techniques include error guessing and exploratory testing — simultaneous learning, design and execution guided by charters. Mutation testing assesses test suite effectiveness.

  • Equivalence partitions and boundaries
  • Decision tables and state transitions
  • Statement and branch coverage
  • Exploratory testing and error guessing
  • Pairwise and mutation testing
Idea clave: Good techniques find more defects with fewer tests.
Capítulo 5

Test planning and risk

Test plans define scope, objectives, approach, resources, schedule, risks, and entry and exit criteria. Entry criteria might require a stable build and environment; exit criteria might require coverage and no open critical defects.

Risk-based testing prioritises by likelihood and impact — a payment module change gets more attention than help-page text. Release decisions are business decisions informed by test results and risk.

  • Test plan contents
  • Entry and exit criteria
  • Risk-based prioritisation
  • Informing release decisions
Idea clave: Test where failure would hurt most.
Capítulo 6

Test cases and defect management

Test cases include preconditions, steps, data and expected results; traceability links them to requirements to show coverage and change impact. Defect reports include reproduction steps, expected versus actual results, environment details and evidence, written objectively.

Severity describes impact; priority describes business urgency — a misspelled logo before a launch is low severity but high priority. The defect lifecycle moves from new to assigned, fixed, retested and closed or reopened. Root cause analysis prevents similar defects.

  • Well-structured test cases
  • Traceability
  • Clear, objective defect reports
  • Severity vs priority
  • Defect lifecycle and root causes
Idea clave: A good defect report gets defects fixed faster.
Capítulo 7

Test automation

The test automation pyramid favours many unit tests, fewer API/integration tests and the fewest UI end-to-end tests. UI tests can be flaky because of timing, environment or locator changes. Good automation candidates are repetitive, stable, high-value and frequently run — such as regression suites.

The Page Object Model separates page structure from test logic. Slow suites should be restructured, parallelised and split so fast tests run on every commit.

  • The test pyramid
  • Avoiding flaky tests
  • Choosing what to automate
  • Maintainable automation design
Idea clave: Automate to get fast, reliable feedback.
Capítulo 8

API, performance, security and accessibility testing

API testing checks business logic and integrations directly: status codes, data, error handling, authentication and performance. Contract testing ensures services agree on request and response formats.

Load testing checks behaviour under expected load; stress testing goes beyond capacity to find breaking points and recovery. Results are compared with non-functional requirements. Security testing covers authentication, authorisation, input validation and sessions. Accessibility testing checks usability for people with disabilities against WCAG, and usability testing observes real users achieving goals.

  • API and contract testing
  • Load vs stress testing
  • Security focus areas
  • Accessibility and usability
Idea clave: Users experience the whole product, not just its features.
Capítulo 9

Test data, environments and pipelines

Test data copied from production needs controls; synthetic or masked data protects personal data while staying realistic. Test environments should resemble production and be controlled and documented.

Continuous integration runs automated tests on every change for fast feedback. Shift-right practices — canary releases, feature flags and observability — extend quality into production.

  • Synthetic and masked data
  • Production-like environments
  • Tests in CI pipelines
  • Shift-right monitoring
Idea clave: Reliable environments make reliable results.
Capítulo 10

Agile, DevOps and quality metrics

In agile teams, testers collaborate throughout the sprint, refining acceptance criteria and testing continuously. BDD uses Given–When–Then examples to align business and technical teams; TDD writes a failing test before code, then refactors. The Definition of Done includes agreed quality activities.

Metrics include defect density (defects ÷ size) and defect leakage (defects found after release versus before). Test summary reports state what was tested, results, open risks and a release recommendation.

  • Whole-team quality
  • BDD and TDD
  • Definition of Done
  • Defect density and leakage
  • Clear test summary reports
Idea clave: Measure quality to improve it, not to blame people.
Capítulo 11

The QA mindset and communication

Effective QA engineers combine curiosity, scepticism and empathy for users. They ask "what could go wrong?" when reviewing a story, explore unusual paths and data, and think about the people who will rely on the product. At the same time, they collaborate closely with developers, product owners and designers, because quality is a whole-team responsibility.

Communication matters as much as technique. Defects are described objectively, focusing on behaviour and impact rather than on people. Risks are explained in business terms so decision-makers can weigh them. Testers share knowledge about tools, techniques and product areas, and continuously improve their own skills through practice, reflection and learning from escaped defects.

  • Curiosity and healthy scepticism
  • Whole-team ownership of quality
  • Objective, impact-focused communication
  • Explaining risk in business terms
  • Learning from escaped defects
Idea clave: Great testers make quality visible and help everyone improve it.

¿Listo? Haz el examen gratis

Haz el examen y obtén tu insignia digital gratis. Después de aprobar podrás pedir el certificado oficial.

Empezar examen gratis