test-driven-development
Test-Driven Development workflow - use only when explicitly requested. Write failing test first, verify it fails, write minimal code to pass, refactor while keeping tests green
Discover blockchain testing skills, compare source repositories and read the instructions for each workflow.
Test-Driven Development workflow - use only when explicitly requested. Write failing test first, verify it fails, write minimal code to pass, refactor while keeping tests green
Run the right tests for changes and keep coverage expectations. Use when modifying code or tests, or when debugging failures.
Set up async tests with proper fixtures and mocks using pytest-asyncio patterns. Use when testing async functions, creating async fixtures, mocking async services, or handling async context managers. Covers @py...
Generate MSTest + Moq unit tests for Notebook Automation, following existing patterns in src/c-sharp/NotebookAutomation.Tests.
Guidance for running and updating tests in this repository.
Monitors and analyzes network traffic during browser automation workflows using Playwright MCP tools. Use when investigating API behavior, debugging failed requests, performance analysis, or checking network ac...
Ensure TEST_VERSION is updated whenever creating or editing Lithuanian HTML practice tests under tests/ (including tests/kids/). Use when modifying test content or logic so saved progress invalidation works cor...
Select and execute the next TDD task phase from SCOPES.yml
Auto-generate constructor validation tests from service class signatures. Use when creating tests for new services, validating fail-fast principle, ensuring constructor validation, or testing required parameter...
Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
Execute browser-based UI testing using Chrome MCP tools. Tests user interactions, visual outcomes, captures evidence. Use for UI features after implementation and security review.
Testing use cases and application services: use case testing with mocked gateways, DTO testing, application exception testing, orchestration testing, mocking at adapter boundaries. Coverage target: 85-90%. Use...
Use this skill when developing code, especially during a TDD cycle. This is the "Green" phase of TDD
Environment file (.env) patterns, test data, and credential loading
Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales. Use when uncertain about scalability, edge cases unclear, or validating architecture for producti...
在即将声称工作完成、修复或通过时使用,在提交或创建 PR 之前 - 要求在做出任何成功声明之前运行验证命令并确认输出;始终证据先于断言
Integration test patterns using real API calls with credentials from .env
Measure and track test coverage: coverage thresholds by layer, coverage reporting (HTML/terminal), identifying coverage gaps, branch coverage vs line coverage, coverage-driven testing. Includes layer-specific t...
Run the TMI comprehensive test suite against Oracle ADB (OCI) including unit tests, integration tests, API tests, and CATS security fuzzing. Use when asked to run tests against Oracle database.
Validate spec-implementation-test alignment and convergence for spec groups. Checks spec completeness, atomic spec coverage, implementation evidence, test evidence, and traceability. Use after implementation an...
Runs tests, analyzes failures, and fixes test issues to ensure code quality.
Configure comprehensive testing in Gradle including JUnit 5, TestContainers, test separation (unit vs integration), and code coverage with JaCoCo. Use when setting up test frameworks, configuring integration te...
Go testing patterns and best practices. Load when writing or running Go tests. Triggers: running tests, writing test files, test coverage, benchmarks, integration tests, table-driven tests, mocking, fixtures, o...
Testing best practices for Crude Functions project - includes TestSetupBuilder usage patterns, test structure guidelines, mocking approaches, and anti-patterns to avoid. Use when writing or modifying tests in t...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.