Use when implementing any feature, fixing any bug, or changing behavior in TypeScript or Python — and whenever the user mentions TDD, test-first, test-driven, red-green-refactor, "write tests", "add tests", unit/integration tests, pytest, vitest, jest, mocking/test doubles, coverage gates, or retrofitting tests onto a legacy codebase. Teaches the full TDD discipline (the Iron Law, red-green-refactor, the Three Laws, FIRST, AAA/GWT, triangulation), with extensive runnable TypeScript (Vitest) and Python (pytest) examples, test-double/mocking guidance and anti-patterns, how to bootstrap TDD into a new OR existing repo, advanced patterns (outside-in, double-loop, property-based, controlling time/IO), and WHY test-first produces better software specifically when an AI agent writes the code. This is the comprehensive companion to the terse `superpowers:test-driven-development` enforcer — use both: that one to stay disciplined in the loop, this one for depth, examples, and setup.
Use this skill for Pest PHP testing in Laravel projects only. Trigger whenever any test is being written, edited, fixed, or refactored — including fixing tests that broke after a code change, adding assertions, converting PHPUnit to Pest, adding datasets, and TDD workflows. Always activate when the user asks how to write something in Pest, mentions test files or directories (tests/Feature, tests/Unit, tests/Browser), or needs browser testing, smoke testing multiple pages for JS errors, or architecture tests. Covers: test()/it()/expect() syntax, datasets, mocking, browser testing (visit/click/fill), smoke testing, arch(), Livewire component tests, RefreshDatabase, and all Pest 4 features. Do not use for factories, seeders, migrations, controllers, models, or non-test PHP code.
Use when a request must be converted into testable constraints and an owned decision for Software testing and release assurance: contract testing for version migrations. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Verify forward and recovery paths on disposable data, including compatibility and partial-failure behavior. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Use when a solution needs a coherent structure before implementation or production for Software testing and release assurance: unit testing for cross-platform behavior. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Record browser, operating system, device, runtime, locale, and architecture for each matrix result. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Deliver feature work, frontend test design, and refactors in this Academic Events repository with tests or explicit validation. Use when changing behavior, adding features, fixing regressions, updating tests, reviewing missing coverage, validating browser interactions, or documenting testing gaps across api/ and web/.
Generate executable test automation code from test case specifications (default target: opendatahub-tests; override with --target-repo). Skips TC-UI-*. Use after test cases are reviewed to create production-ready pytest code that follows repository conventions.
MCP server for TestCollab test management. Lets AI coding assistants (Claude Code, Cursor, Windsurf, Codex) create, update, and query test cases, create test plans, and suite hierarchy. Connect your AI workflow to your QA process.
Gera estrutura completa de testes automatizados (unitários, integração e edge cases) com base no código existente. Use para "escrever testes para este arquivo", "aumentar cobertura" ou "criar mocks".
Generates NUnit 3 tests in C#. Covers Assert.That constraint model, parameterized tests, setup/teardown, and Moq mocking. Use when user mentions "NUnit", "[TestFixture]", "[Test]", "Assert.That", "C# unit test". Triggers on: "NUnit", "[Test]", "Assert.That", "C# test", "NUnit3".
Generates NUnit 3 tests in C#. Covers Assert.That constraint model, parameterized tests, setup/teardown, and Moq mocking. Use when user mentions "NUnit", "[TestFixture]", "[Test]", "Assert.That", "C# unit test". Triggers on: "NUnit", "[Test]", "Assert.That", "C# test", "NUnit3".
Operately test layout, naming (.projections.json), factories, feature/e2e steps, external query/mutation auth specs, and how to run Elixir/API/JS/EE tests. Use when adding, renaming, splitting, or reviewing tests; choosing where a test belongs; writing Factory/TurboCase/FeatureCase or ExternalApi QuerySpec/MutationSpec tests; or running make test / feature tests.