qa-engineer

Define QA strategy with acceptance criteria and risk assessment for ETYB workflows.

9|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/e-t-y-b/etyb-skills --skill qa-engineer-e-t-y-b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/e-t-y-b/etyb-skills/tree/main/skills/qa-engineer
Command: npx skills add https://github.com/e-t-y-b/etyb-skills --skill qa-engineer-e-t-y-b

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA teams struggle to design robust testing strategies and maintain reliable automated tests across fast-moving software projects. This Skill provides a structured approach to plan-time QA, align stakeholders, and tailor test types for unit, integration, E2E, performance, API, and governance so teams ship with confidence.

Core Features & Use Cases

  • Plan-time test strategy guidance for Plan gate, including shape selection and acceptance criteria.
  • Cross-skill reference access with Unit Test Specialist, Integration Test Specialist, E2E, Performance, API, and Test Strategy Architect to tailor recommendations.
  • CI/CD integration planning and risk-based testing considerations across startup to enterprise scale.

Quick Start

Describe your project goals and constraints so I can tailor a plan-time test strategy.

Frequently Asked Questions about qa-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a QA strategy that covers unit, integration, and E2E testing?

A comprehensive QA strategy aligns stakeholders by tailoring test types across unit, integration, E2E, performance, API, and governance. It provides plan-time guidance, acceptance criteria, and risk assessment to ensure teams ship reliable software.

What is plan-time test strategy guidance and when do I need it?

Plan-time test strategy guidance defines testing approaches during the planning stage before development begins. You need it to establish acceptance criteria, assess risks, and select appropriate test shapes to prevent flaky tests and align cross-functional teams.

How do I integrate automated testing and risk assessment into CI/CD pipelines?

Integrate automated testing into CI/CD by applying risk-based testing considerations tailored to your scale. This involves defining deployment gates and governance rules that validate unit, integration, and E2E tests across development and deployment stages.

Does this QA approach work for both startup and enterprise scale projects?

Yes, this QA strategy approach scales from startup to enterprise environments. It tailors risk-based testing considerations, CI/CD integration planning, and governance gates to fit the specific constraints and goals of your project scale.

What's the best way to reduce flaky tests in E2E and integration automation?

Reducing flaky tests requires a structured test strategy that aligns E2E and integration automation with clear acceptance criteria and risk assessment. Cross-skill references to E2E, Integration, and Unit Test Specialists help tailor reliable automation recommendations.

How do I define acceptance criteria and data-management recommendations for software testing?

Defining acceptance criteria and data-management recommendations involves establishing plan-time QA gates for implement and verify phases. This structured approach delivers risk assessment and tailored test strategy to govern data usage across testing workflows.