501 tagged Unit testing, measured the same way as everything else here.
Browse within: ai-assistant 11code-quality 10agentic-coding 9agentic-workflow 9Autonomous Agents 8agent-orchestration 8claude-ai 7claude-code-skills 7copilot 7gemini-cli 7china 6china-access 6Multi-Agent 5agent-harness 5
Agent Claude Code
Use this agent when you need to design, implement, review, or improve test suites and testing strategies. This includes writing unit tests, integration tests, end-to-end tests, setting up test infrastructure, debugging flaky tests, improving test coverage, or evaluating code for testability. Also use when reviewing…
CodelyTV/agentic_programming-course
Agent Codex
Use when creating or modifying tests: unit tests, Object Mothers for test data, or hand-written Mock Objects for domain interfaces. Follows the project's testing conventions with jest, should pattern mocks, and faker-based mothers.
Agent
Authors new AgentCompass scoring rules end-to-end: registers a @rule in the right src/airx/rules/ .py module, adds pass/fail/N-A unit tests in tests/testrules .py, and regenerates docs/RULES.md. Use this skill when adding a new rule, extending a pillar with a new check, or fixing a rule's false positives. Trigger when…
Agent Claude Code
Use this agent when you need to write real-world integration or unit tests for NuGuard's key capabilities (SBOM generation, analysis, policy, redteam, CLI, configuration, etc.). Invoke this agent after implementing new features, refactoring existing code, or when test coverage is insufficient for a module.\n\n…
Agent
Generate focused pytest tests for a target function by studying reference implementation. Use during test curation (phase 2) after test discovery.
Agent Codex
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality. Familiar with GitScape's pytest + FastAPI TestClient setup.
girijashankarj/cursor-handbook
Agent Cursor
Agent "testing-agent" from girijashankarj/cursor-handbook, covering testing agent, invocation, scope, expertise and test pyramid.
Agent Claude Code ✓ vendor
Use this agent when you need to evaluate the test coverage of code changes, identify missing test scenarios, or assess the quality of existing tests. This agent should be invoked when: Context: User has implemented a feature and wants to ensure adequate testing. user: "I've implemented the new…
vinvcn/addyosmani-agent-skills-zh
Agent
A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.
Agent
QA specialist writing/fixing tests. Black-box tester: public API surface, expectations from docs not implementation. NOT for linting (foundry:linting-expert), implementation (foundry:sw-engineer), test perf (foundry:perf-optimizer), non-Python frameworks. TRIGGER: "write tests for", "add unit tests". SKIP: read-only…
Agent Claude Code
Test generation agent for tests/ — writes and updates vitest test files for all source modules.
magendooro/n98-magerun2-performance-review
Agent Claude Code
Write PHPUnit tests for Performance Review analyzers. MUST BE USED when user says "create tests", "write tests", "add test coverage", or "need tests" for an analyzer. Use when new analyzers are created or existing ones are modified. Creates comprehensive unit tests covering happy paths, edge cases, and error…
Agent Claude Code
Creates Vitest unit and component tests. Use when writing tests for components or functions.
Agent
The behavioral corpus for the text tool-call parser, migrated from 4900 lines of Rust unit tests into executable conformance fixtures for the harn#5142 parse re-platform. Every baseline was generated from the observed stdout of the built binary, never from reasoning and never from the Rust assertions, so the corpus…
Agent
Generates and hardens the test suite — unit AND end-to-end — for a change, runs it, and validates the behavior actually works (not just that assertions pass). Use as the SAFETY GATE before any autonomous fix is approved or merged: no adequate tests, no green light. The thing that makes the autonomous loops safe.
Agent Claude Code
Test suite (pytest), golden files, integration tests, and quality assurance for Spectra. Ensures everything works correctly.
Agent
Writes tests and runs verification for a Ralph user story that has already been implemented by ralph-coder. Creates unit/integration/e2e tests, runs story verification commands, and runs the full regression suite. Used by ralph-orchestrator as the second phase of story execution.
GabrielOnDelphi/Claude-Tools-for-Delphi
Agent Claude Code
Audit a Delphi DUnitX or classic-DUnit test suite for FAKE or WEAK tests — tests that pass without verifying the behavior they name (zero assertions, Assert.Pass-only, tautologies, setup-only or tautological-helper checks, vague error assertions, negative tests with no probe). Reads every [Test] or published method…
Agent Claude Code
Use for adding or maintaining the minimal Vitest test baseline in the stabilization roadmap, including focused tests for pure utilities, validation, sanitization, config behavior, or package-safe logic.
Agent
When writing tests for this library.
Agent Codex
Use this agent when a new Rust function is added (or significantly rewritten) that depends on an LSB-side behavior — coord transforms, packet builders/decoders, session-state transitions, shared constants, lifecycle assumptions. The agent proposes the unit tests that would pin the LSB invariants so a future drive-by…
Agent
Rust testing specialist focused on comprehensive test coverage with nextest and criterion, test infrastructure, and quality assurance. Use PROACTIVELY when adding new functionality that requires tests, investigating test failures, or setting up test infrastructure. Also audits existing test suites for redundancy…
ehebert7/salesforce-claude-framework
Agent Claude Code
Generate comprehensive Apex test classes.
Agent Claude Code
Writes and runs Caraya unit tests for LabVIEW code — settles what is worth asserting, builds one test VI per group of cases with the subject called as an ORDINARY STATIC SUBVI, runs the suite through a generated Caraya runner, and reads the JUnit report. It does NOT run a negative control unless the task asks for one…