Unit Testing
5220 skills in Testing & Security > Unit Testing
prompt-versioning
Track prompt versions, A/B test variants, and measure prompt performance
building-stories-with-tdd
Expert for building user stories using Test-Driven Development (TDD) with NestJS and @lenne.tech/nest-server. Implements new features by creating story tests first in tests/stories/, then uses generating-nest-servers skill to develop code until all tests pass. Ensures high code quality and security compliance. Use in projects with @lenne.tech/nest-server in package.json dependencies (supports monorepos with projects/*, packages/*, apps/* structure).
a11y-tester
Run automated accessibility tests on URLs or HTML content using axe-core engine to WCAG 2.2 AA standards, then format findings as standardized issue reports. Use this skill when users want to test website accessibility, find WCAG violations, audit pages for accessibility issues, check if sites are accessible, analyze HTML for accessibility problems, or create accessibility issue tickets. Triggers on requests like "test accessibility", "check for WCAG violations", "audit this URL", "is this page accessible", "find accessibility issues", or "write accessibility issues".
test-risk-analyzer
あらゆる言語/スタックで潜在バグリスクを洗い出し、追加すべきテストケースを提案する。未テストのエッジケース探索や安全性確認、カバレッジ強化のテスト案提示を求められたときに使用する。
test-pattern-detector
Delegates test pattern detection to a lightweight agent. Use when you need to understand existing test conventions without loading test files into context.
midnight-network
Configure and operate Midnight Network infrastructure including proof servers, indexers, and network endpoints. Use when setting up development environment, troubleshooting connections, or configuring deployments. Triggers on network, proof server, indexer, or testnet questions.
validate-test-coverage
Homeostatic sensor validating test coverage percentage and detecting requirements without tests. Calculates coverage per requirement (REQ-*) and overall. Use as quality gate or continuous coverage monitoring.
ci-cd-pipelines
Guide for creating and configuring CI/CD pipelines with GitHub Actions or GitLab CI. Use when users need to set up automated workflows for testing, building, deploying applications, or managing secrets. Covers Node.js, Python, Docker, Vercel, Railway, Cloudflare, and multi-environment deployments.
code-refactoring-patterns
When and how to refactor complex functions including complexity thresholds (50+ statements, 12+ branches), extraction patterns, guard clauses, and testing strategies. Use when ruff/pylint complexity warnings appear or code becomes hard to maintain.
mcp-builder-evaluation
MCP (Model Context Protocol) server evaluation guide for creating comprehensive test suites with read-only, independent questions
module-extractor
Extract classes, functions, or code blocks from large modules into separate files. This skill should be used during refactoring to break up monolithic files while maintaining import compatibility and test coverage.
cloudflare-browser-rendering
Guide for implementing Cloudflare Browser Rendering - a headless browser automation API for screenshots, PDFs, web scraping, and testing. Use when automating browsers, taking screenshots, generating PDFs, scraping dynamic content, extracting structured data, or testing web applications. Supports REST API, Workers Bindings (Puppeteer/Playwright), MCP servers, and AI-powered automation. (project)
opentofu-qa
Quality assurance and testing toolkit for OpenTofu/Terraform infrastructure as code. Use this skill when reviewing, testing, or validating OpenTofu/Terraform configurations. This skill runs automated QA checks (tofu fmt, tofu validate, tflint, trivy) and validates code against client-specific conventions and best practices. Ideal for code review, pre-commit validation, and ensuring IaC quality standards.
molecule-init
Initialize Molecule testing framework for Ansible roles with Docker-based TDD setup. Use when creating new Ansible roles, setting up molecule scenarios, or when user asks to initialize molecule testing.
openrewrite
OpenRewrite recipe development and test maintenance. Use when writing OpenRewrite recipes, fixing test failures, or working with import ordering in recipe tests.
qa-workflow-manager
Manage QA test case workflows, status transitions, and verification checklists. Use when working with QA status states (Reviewing, DevError, ProdError, DevDone, ProdDone, Hold, Rejected, Duplicate), progress tracking (Waiting, Checking, Working, DevDeployed, ProdDeployed), activity logging, or test case management.
prompt-injection-testing
Master prompt injection attacks, jailbreak techniques, input manipulation, and payload crafting. Use when testing LLM prompt vulnerability or designing attack scenarios.
smalltalk-debugger
Systematic debugging guide for Pharo Smalltalk development. Provides expertise in error diagnosis (MessageNotUnderstood, KeyNotFound, SubscriptOutOfBounds, AssertionFailure), incremental code execution with eval tool, intermediate value inspection, error handling patterns (on:do: blocks), stack trace analysis, UI debugger window detection (read_screen for hung operations), and debug-fix-reimport workflow. Use when encountering Pharo test failures, Smalltalk exceptions, unexpected behavior, timeout or non-responsive operations, need to verify intermediate values, execute code incrementally for diagnosis, or troubleshoot Tonel import errors.
device-testing
Expert in React Native testing strategies including unit tests with Jest, integration tests, E2E tests with Detox, component testing with React Native Testing Library, snapshot testing, mocking native modules, testing on simulators and real devices. Use for testing, jest, detox, e2e, unit test, integration test, component test, test runner, mock, snapshot test, testing library, react native testing library, test automation.
godot-visual-bug-diagnosis
Debug visual and spatial bugs in Godot games through user observation, Godot-specific diagnosis, and test-driven fixes. Use when debugging visual or input issues in Godot where the user can observe the game but you cannot, when bugs involve rendering, positioning, animation, or coordinate systems, or when "what user sees" differs from expected behavior. For pure logic bugs use Systematic Debugging instead