---
name: qe-playbook
description: "What a Quality Engineer reaches for in RBA Skills to define done, build test coverage, run UAT, and sign off on releases."
disciplines:
  - engineering
tags:
  - playbook
  - role-guide
  - qe
author:
  name: Kassie Gibbons
  url: https://rba.com
---

# Quality Engineer Playbook

QEs own quality assurance — defining what "done" means, writing and executing test plans, facilitating UAT, and making sure what goes to production works the way it was designed. A good QE catches the assumptions everyone else forgot to question. This is your RBA Skills toolkit.

## Create — build the coverage

| Reach for | Why |
|---|---|
| `uat-test-case-writer` skill | Client-executable test cases across happy path, edge cases, error states, and accessibility. |
| **qa-test-generator** (`qa-coverage-matrix`, `qa-edge-case-analysis`, `qa-gherkin-scenarios`, `qa-playwright-scripts`) | Coverage matrices, edge-case analysis, Gherkin scenarios, and automated Playwright scripts. |
| `test-data-generator` skill | Realistic test data for scenarios. |

## Test & Review — prove quality

| Reach for | Why |
|---|---|
| **accessibility-auditor** (`accessibility-wcag-scan`, `accessibility-aria-review`, `accessibility-vpat-acr`) | Accessibility coverage and ACR/VPAT evidence. |
| **security-readiness-reviewer** → `owasp-security-audit` | Security review as part of "done." |

## Deliver — sign off

| Reach for | Why |
|---|---|
| **release-notes-generator** → `release-notes-client` | Sign off on what's tested and what's known. |
| **project-management** → `project-closure-report` | Contribute the UAT summary. |

## QE Tips

- **Happy path + edge cases + error states + accessibility.** A suite missing any of these is incomplete.
- **The defect log is your negotiating tool.** Critical defects block release; high defects need a resolution plan. Document severity consistently.
- **UAT is client-executed, not client-managed.** You facilitate, they execute. Set that expectation in the kickoff deck.