Unit Testing
5220 skills in Testing & Security > Unit Testing
exploiting-web3-smart-contracts
Audit and exploit smart contracts and Web3 applications including reentrancy, integer overflow, access control flaws, and DeFi-specific vulnerabilities. Use when testing blockchain applications or performing smart contract audits.
run-benchmark
Run and interpret the File API vs Inline benchmark for Gemini performance testing. Use when discussing performance optimization, caching strategies, or comparing document upload approaches.
web-app-qa
Interactive UI/visual QA workflows using Playwright MCP for test generation, accessibility audits, visual regression, and cross-browser testing
auto-commit
Automatically commits changes using conventional commits format (feat:, fix:, docs:, chore:, refactor:, test:, style:). Use after completing bug fixes, feature implementations, or documentation updates. Triggered automatically via Stop hook.
implementation-phase
Standard Operating Procedure for /implement phase. TDD workflow, anti-duplication checks, task execution, and continuous testing.
review
Comprehensive code review with parallel specialist sub-agents. Analyzes requirements traceability, code quality, security, performance, accessibility, test coverage, and technical debt. Produces detailed findings and calls /qa-gate for final gate decision.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
playwright
Browser automation scripts for testing, screenshots, and web interaction. 16 scripts with persistent state.
subject-line-optimizer
Improve newsletter open rates through better subject lines. Use when:(1) Writing subject lines for tacosdedatos editions, (2) Analyzing why an editionhad low open rates, (3) A/B testing subject line variants, (4) Reviewing subjectlines before sending. Produces 5-10 variants with recommendations.
mode-backend-tdd
Methodological skill for Test-Driven Development in NestJS backend. This skill should be used when strict quality requirements demand tests-first approach, refactoring critical services, or building MVPs with mandatory coverage. Complements nestjs-architect skill with TDD methodology.
go-specialist
Go language consultant providing guidance on best practices, testing with testify, concurrency patterns, error handling, and technology stack recommendations. Use when answering Go questions, reviewing Go code, or advising on Go implementation approaches.
api-endpoint-tester
Expert at testing API endpoints, Supabase RPC functions, and database queries. Use when asked to test endpoints, verify API responses, check RPC functions, debug API issues, or validate data flows.
code-testing
Generate and run unit and integration tests using pytest (Python) or Jest (JavaScript) with fixtures, mocks, and async support. Use for test-driven development, code review validation, coverage verification, and regression testing. Target 80%+ code coverage. Supports pytest markers, Jest snapshots, and CI/CD integration. Triggers on "test", "TDD", "unit test", "integration test", "test coverage", "pytest", "jest".
test-before-commit
Enforces running unit tests and linting before committing code changes in the unsealed-networks repository
oversized-skill
A skill with an oversized SKILL.md file for testing warnings
unity-testing
This skill should be used when the user asks about "tests", "unit tests", "EditMode tests", "PlayMode tests", "Test Runner", "test coverage", "NUnit", "Assert", "test fixtures", "writing tests", "running tests", or discusses Unity testing patterns and practices.
webapp-testing
Tests local web applications using browser automation for UI verification, form testing, and screenshot capture. Use when validating frontend functionality, debugging UI behavior, or performing visual regression testing. Triggers on test requests, UI verification, or screenshot capture needs.
programming
Write, debug, review and explain source code following object-oriented best practices, DDD principles, and comprehensive testing standards. Use when writing new code, refactoring, debugging, code review, or explaining programming concepts.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
websocket-toolkit-googleai-dart
Automates updating googleai_dart when Gemini Live API WebSocket schema changes. Fetches latest schema, compares against current, generates changelogs and prioritized implementation plans. Use for: (1) Checking for Live API updates, (2) Generating implementation plans for WebSocket changes, (3) Creating new message types from schema, (4) Syncing local schema with upstream. Triggers: "update live api", "sync websocket", "new messages", "live api changes", "check for live updates", "update live schema", "websocket version", "fetch live schema", "compare live schema", "what changed in live api", "live implementation plan".