pytest-application-layer-testing
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...
Discover documentation testing skills, compare source repositories and read the instructions for each workflow.
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...
C#/Python测试生成器技能:负责单元测试骨架生成、Mock对象创建、测试数据构造、边界条件覆盖、测试项目结构管理。使用时需要生成测试骨架、创建Mock对象、构造测试数据、覆盖边界条件、管理测试项目结构。
Web application testing principles. E2E, Playwright, deep audit strategies.
Property-based testing with Hypothesis for Python projects. Use when writing property tests, testing invariants, generating test cases, fuzz testing, roundtrip testing, or validating behavior across many inputs...
Write tests that verify atomic spec acceptance criteria and requirements. Maps each AC to specific test cases, follows AAA pattern, ensures deterministic isolated tests. Use in parallel with implementation or a...
Visual regression testing for Textual TUI applications using pytest-textual-snapshot. Captures SVG screenshots and compares across test runs to detect visual regressions. Use when: testing visual appearance, de...
Seed and manage test data for dev/preview environments. Use when the user mentions seeding, creating test users, or resetting seed data.
Testing recipes for specific Textual TUI scenarios. Provides "how do I test X?" patterns for common testing needs. Use when: testing keyboard shortcuts, screen transitions, focus management, reactive attributes...
TDD loop checklist: tests first, implement, refactor, verify.
An AI tool for automated testing, focusing on output quality, reliability, user trust, regulatory compliance, and security. Use this skill to prevent injection attacks, ensure system integrity, and protect data...
Smart Recipe Planner UI testing patterns with Playwright. Trigger: When writing E2E tests for the frontend, creating Page Objects, or validating UI flows in Smart Recipe Planner.
Gate 4b validation: Integration test creation and no-hardcoded-values enforcement
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.