Testing & QA

Unit tests, integration tests, E2E, QA, validation, and test automation

skills in category: 31,543
pages available: 1,315

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse testing & qa skills

Showing 5,833–5,856 of 31,543 skills

React TestingAТестирование React-компонентов — Testing Library + Vitest/Jest, поведенческие проверки от лица пользователя, MSW для мокинга сети. Use при написании или ревью тестов фронтенда.testingreacttestingVotes: 0GitHub stars: 2
Visual Research VorclAМногошаговый анализ скриншотов через Task Master с документацией, live-проверкой и доказательным ответом.testingVotes: 0GitHub stars: 2
TestingAПерсона «Testing & Verification Engineer» — пишет и прогоняет unit (Vitest/Jest), интеграционные (Supertest/`inject`, testcontainers) и e2e (Playwright) тесты, снимает покрытие, лечит flaky. Исполняет testStrategy задач Task Master и выносит вердикт «готово/не готово» строго с выводом прогонов — замыкает цикл «реализация → проверка → done». Use when нужно написать тесты, верифицировать задачу перед done, снять покрытие или вылечить нестабильный тест.testingtypescriptreactVotes: 0GitHub stars: 2
Testing VorclAЦель тестирования через Task Master — покрытие/верификация до готового, зелёные прогоны как доказательство (роль testing). Use when дана цель по тестам и её нужно довести через задачи.testingnodetestingVotes: 0GitHub stars: 2
Testing VerifyAНезависимая read-only верификация claimed задачи по testStrategy. Checker не меняет implementation, acceptance tests или статусы; возвращает evidence-based ГОТОВО/НЕ ГОТОВО Orchestrator-у.testingtestingdatabaseVotes: 0GitHub stars: 2
Testing UnitAUnit-тесты (Vitest/Jest) для файла/модуля — happy path + границы + ошибки, с реальным прогоном и выводом (роль testing). Use when нужно покрыть функцию/модуль модульными тестами.testingnodetestingVotes: 0GitHub stars: 2
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Testing StrategyAСтратегия тестирования — пирамида unit/integration/e2e, что мокать (границы I/O) а что нет (домен, своя БД в integration), осмысленные пороги покрытия, AAA/given-when-then, критерии хорошего теста, причины flaky → фиксы. Use при проектировании/ревью тестов, выборе уровня и лечении нестабильных.testingnodetestingVotes: 0GitHub stars: 2
Testing FlakyAДиагностика и лечение нестабильного (flaky) теста — race/timing/shared state/моки; фикс первопричины до 10 зелёных прогонов подряд (роль testing). Use when тест падает «иногда» или только в CI.testingtestingVotes: 0GitHub stars: 2
Testing E2eAPlaywright e2e-сценарии критического пути — селекторы по ролям, fixtures/auth-state, web-first assertions, trace при падении (роль testing). Use when нужно проверить пользовательский сценарий в реальном браузере.testingtestingVotes: 0GitHub stars: 2
Testing CoverageAОтчёт покрытия с находками — что критично не покрыто, задачи на закрытие дыр (роль testing). Use when нужно понять реальное покрытие и спланировать его рост.testingtestingVotes: 0GitHub stars: 2
React TestingAТестирование React-компонентов — Testing Library + Vitest/Jest, поведенческие проверки от лица пользователя, MSW для мокинга сети. Use при написании или ревью тестов фронтенда.testingreacttestingVotes: 0GitHub stars: 2
Frontend TestAГенерация тестов компонентов (роль frontend). Use when нужно покрыть React-компоненты/хуки поведенческими тестами (Testing Library + Vitest); готово = прогнанный зелёный набор, не текст тестов.testingreacttestingVotes: 0GitHub stars: 2
Expo Mobile TestAСоздать и реально прогнать Expo tests: domain unit, React Native Testing Library и Maestro critical flows.testingreactnodeVotes: 0GitHub stars: 2
E2e PlaywrightAE2E на Playwright — селекторы (getByRole > testid > css), fixtures/auth-state (storageState), web-first assertions без sleep, trace/screenshot при падении, параллельность/шардинг, CI-конфиг, Page Object. Use при написании, ревью или стабилизации браузерных e2e-тестов.testingapiVotes: 0GitHub stars: 2
Test Driven DevelopmentAApply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.testingpythongoVotes: 0GitHub stars: 3
Technical Debt AuditAAudit the project's technical health and identify "high-interest" debt. Load when the user asks to check code quality, find TODOs, assess project health, or prepare for a refactoring sprint. Also triggers on "technical debt audit", "where is the code messy", "assess project health", "find my hacks", or "identify tech debt". Essential for maintaining velocity in growing projects.testinggorefactoringVotes: 0GitHub stars: 3
Split SkillAReduce an oversized SKILL.md by checking whether an existing skill already covers the excess sub-workflow before creating a new child skill only when none fits. Load when a skill exceeds 200 lines and compress-skill determines excess content is genuinely CORE, when the same sub-workflow appears in multiple skills, or when universal-skill-creator or improve-skills identifies a coherent sub-capability. Also triggers on "split this skill", "extract a sub-skill", "this skill is doing too much", o...testinggobashVotes: 0GitHub stars: 3
Spec CrosscheckAHard readiness gate before implementation begins — cross-checks the constitution, feature spec, plan, and tasks for consistency, traceability, and unresolved ambiguity. Returns PASS or FAIL with specific findings. Load when the spec-driven-development orchestrator routes /analyze, when the user asks to cross-check spec vs plan, audit traceability, verify spec readiness, gate-check before implementation, or says "is this spec implementation-ready", "trace requirements to tasks", "/analyze", "s...testinggoawsVotes: 0GitHub stars: 3
Safe ChangeAApply one logical code change with mandatory impact mapping, git snapshot, verification, and automatic revert on failure. Load when the user asks for a safe edit, verified change, one change at a time with rollback, or codespine-style edit loop. Also triggers on "safe change", "edit with verification", "don't break the build", "revert if tests fail", or any non-trivial code edit where blast radius matters. Always runs dependency-mapping first. Pairs with incremental-implementation for multi-s...testinggobashVotes: 0GitHub stars: 3
Reality CheckAEvaluate any project, product, or system's claims against its actual implementation — scoring each claim for truth, identifying architectural gaps, assessing competitive positioning, proposing creative solutions, and producing an actionable roadmap. Load when the user asks to evaluate claims, reality-check a project, assess what this project actually does vs what it says, validate product claims, or score a system's credibility. Also triggers on "is this real", "does this work as claimed", "e...testinggosqlVotes: 0GitHub stars: 3
Project ConstitutionAAuthor the project's non-negotiable engineering rules — the constitution that every feature spec, plan, and implementation must satisfy. Load when the user asks to write a constitution, define project rules, set engineering invariants, write project standards, define non-negotiables, capture agent guardrails as policy, or when spec-driven-development orchestrator routes here. Also triggers on "project constitution", "engineering invariants", "non-negotiable rules", "project policy", "set our ...testinggonextjsVotes: 0GitHub stars: 3
Problem To PlanATactical fast path: turn a small problem, bug report, edit request, or narrow refactor into three deliverables — a brief change-spec (docs/specs/), a detailed implementation-ready plan (docs/plans/), and a TODO.md with agent-pickable tasks and milestones. Load when the user describes a tactical problem and wants quick planning artifacts, says "plan this change", "create a TODO", "write a plan for this", "problem to plan", "break this into tasks for agents", "I want to change X — plan it", or ...testinggotestingVotes: 0GitHub stars: 3
Performance OptimizationAMeasure, profile, and fix performance bottlenecks — Core Web Vitals, backend latency, bundle size, and database queries. Load when performance requirements exist, users report slowness, profiling reveals bottlenecks, or the user asks to optimize load time, LCP, INP, CLS, or response time. Not for premature optimization without evidence. Pairs with browser-testing-with-devtools and ci-cd-and-automation for regression guards.testingrustgoVotes: 0GitHub stars: 3
Model SelectionAPlan which model tier handles which work BEFORE execution begins — a high-cognition model deeply understands the problem, lays the foundations, then emits a modular plan assigning each module the cheapest tier that can safely execute it, with escalation tripwires and one-way-door protection. Advisory only: it announces "next module → tier X / model Y" at each boundary and the HUMAN switches models — harnesses like Cursor cannot switch mid-run. Load when the user asks which model to use, wants...testinggorailsVotes: 0GitHub stars: 3