Define plan-driven QA guidance and test-code strategies for automated testing.
npx skills add https://github.com/ace3/skills --skill qa-engineer-ace3
Please help me install this Agent Skill. Skill: qa-engineer Source: https://github.com/ace3/skills/tree/main/skills/qa-engineer Command: npx skills add https://github.com/ace3/skills --skill qa-engineer-ace3
QA engineering for report-only automated test design and test-code authoring guidance. Use for TDD strategy, unit test patterns, integration tests, contract tests, BDD, E2E test code, mobile automation, framework selection, test framework migration, and CI/CD test pipeline planning across common stacks such as Jest, Vitest, pytest, JUnit, RSpec, PHPUnit, xUnit, NUnit, Playwright, Cypress, Selenium, WebdriverIO, Appium, Cucumber, and Robot Framework. Not for running tests as QA evidence — use qa-tester.
Describe a plan for implementing plan-driven QA guidance in a project, including required inputs, recommended workflows, and handoff artifacts.
High-intent search queries and answers about installing and using this skill.
Test strategy design for TDD and BDD workflows defines plan-driven guidance to structure quality-first development. It provides test-pattern guidelines and architecture planning to map unit, integration, and contract tests across common stacks.
Planning E2E test automation and framework migration involves defining plan-driven QA guidance for test-code strategies. It targets E2E planning and mobile automation to structure test designs without running executable test evidence.
Yes, CI/CD test pipeline planning across common stacks is supported by defining output-contract patterns and guidelines. It structures QA plans and handoffs for audits using frameworks like Jest, pytest, Playwright, and Cypress.
Mobile automation and contract testing design are covered by encapsulating guidelines for test-code authoring. It targets Appium for mobile automation and contract test architecture to improve non-executable quality assurance design.
Plan-driven QA design structures test-code strategies and handoff artifacts for audits, whereas running tests directly generates executable evidence. Use this approach for architecture planning and framework selection rather than test execution.
No specific framework is required, but the guidance targets common stacks including JUnit, RSpec, NUnit, Selenium, WebdriverIO, Cucumber, and Robot Framework. It provides framework selection and migration planning tailored to your stack.
bbolek-apGenerate a test automation strategy document from architecture and NFR inputs.
emcconnellCoordinate QA team execution to produce test plans, cases, bug reports, and sign-off reports.
heaptracetechnologyAutomate API contract testing with schema validation and OpenAPI checks.
AlexanderVilla47Automate deterministic AdsKiller workflow testing for n8n with preflight and evidence capture.
