senior-qa_skill

This skill helps you design risk-based QA plans, optimize test layer choices, and triage flaky tests to ensure reliable releases.

Python

3

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill vadimcomanescu/codex-skills --skill senior-qa

LICENSE.txt1.1 KB
SKILL.md950 B

Overview

This skill codifies a senior QA workflow to maximize confidence per unit effort when planning and validating releases. It guides risk-based testing, layer selection (unit/integration/E2E), exploratory testing, and regression planning. Use it to create focused test plans, reduce flakiness, and define clear release sign-off criteria.

How this skill works

The skill inspects product risk areas and recommends test layer decisions: unit tests for logic, integration tests for boundaries, and E2E for critical user journeys. It helps produce a release test plan that separates must-pass automated checks from targeted manual checks and includes strategies for exploratory testing and regression scope. It also surfaces flaky-test triage steps, treating recurrent flakiness as actionable product debt.

When to use it

Creating a release test plan for feature launches or patches
Reviewing test coverage to balance unit, integration, and E2E effort
Triaging flaky or intermittent tests before a release
Defining minimal must-pass criteria for release sign-off
Prioritizing tests based on user-impact and business risk

Best practices

Focus automated coverage on fast, deterministic tests and reserve E2E for critical paths
Identify and document the riskiest user journeys early (payments, auth, data loss)
Pair a small must-pass automated suite with a concise exploratory/manual checklist
Treat flakiness as a product issue: trace root cause, fix or quarantine, and add prevention
Use risk and effort trade-offs to decide what to automate vs. test manually

Example use cases

Scaffold a release test plan that lists must-pass automated tests and a manual testing checklist
Evaluate current test pyramid and recommend shifting tests to more appropriate layers
Triage recurring flakiness by classifying root causes and proposing remediations
Plan regression scope for a patch: decide which E2E paths must run and which can be sampled
Define sign-off criteria that map business risk to test requirements

FAQ

Prioritize flows that impact revenue, account access, data integrity, or core user retention. Use usage metrics and business impact to rank them.

When should I add a new E2E test?

Add an E2E when a journey cannot be reliably validated by unit or integration tests and its failure has high user or business impact.

What if tests keep flaking after fixes?

Quarantine the test to avoid noise, add instrumentation to capture failure context, and track flakiness as technical debt until root cause is eliminated.