GitHub
writing-verification-plans
Use when a project needs a verification plan for acceptance testing in real-world scenarios
Skills IA data ai testing
Découvrez les skills data ai testing, comparez leurs dépôts et consultez leurs instructions.
Catégories: data ai testing
data ai testing Effacer les filtres
Explorer
GitHub
testing-anti-patterns
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without unders...
GitHub
tdd-workflow
Test-Driven Development guidance. Use during feature-dev Phase 5 (Implementation) or any code implementation. Ensures tests are written BEFORE implementation code, following Red-Green-Refactor cycle.
GitHub
writing-go-tests
Applies current Go testing best practices. Use when writing or modifying Go test files or advising on Go testing strategies.
GitHub
spec-driven-development
Implements Spec-Driven Development (SDD) methodology where specifications drive code generation. Use when users build new features, plan implementations, create technical specs, or want structured development w...
GitHub
e2e-tester
Generate and track E2E test checklists with clear user/Claude separation. Users do manual UI actions, Claude runs automated verifications (DB, API, logs). Launches a Docker webapp for testing with screenshot up...
GitHub
characterization-testing
Create tests that describe what legacy code actually does (not what it should do) as safety net before refactoring
GitHub
mutation-testing
在單元測試通過後觸發。透過引入人工錯誤（Mutants）來「測試你的測試」，確保測試案例具有足夠的錯誤偵測能力，建立對驗證機制的信任（Trust the Verification）。
GitHub
enforce-contract
單元測試與代碼提交前觸發。掃描並驗證方法的 pre-conditions、post-conditions 與 invariants，透過契約式設計減少 AI 幻覺。
GitHub
generate-acceptance-test
從規格目錄的 acceptance.yaml 生成/維護 BDD/ezSpec 測試。使用類似 Gherkin 語法，AI 自動產生 step definition（開發人員不需要手寫），驗收測試規格即為 Executable Specification。
GitHub
test-strategy
Production-grade test strategy skill with risk-based testing, coverage analysis, quality gates, and resource optimization
GitHub
performance
Production-grade performance testing skill with k6, JMeter, load testing, stress testing, and performance optimization guidance
GitHub
automation
Production-grade test automation skill covering Selenium, Cypress, Playwright, Appium with POM architecture, retry logic, and CI/CD integration
GitHub
test-endpoints
This skill automates API endpoint testing and documentation. It runs curl requests against specified endpoints, captures responses, validates against OpenAPI spec, and generates markdown documentation. Use afte...
GitHub
spring-testing
Test Spring Boot applications - MockMvc, TestContainers, test slices, integration testing
GitHub
tdd-practices
Guide TDD workflow, design tests, and create mocking strategies
GitHub
prompt-evaluation
Prompt testing, metrics, and A/B testing frameworks
GitHub
php-testing
PHP testing mastery - PHPUnit 11, Pest 3, TDD, mocking, and CI/CD integration
GitHub
codegen-test
A skill for writing Go tests in a TDD workflow. Follow README/Issue requirements and existing test conventions, add a balanced set of table-driven cases across behavior/boundaries/branches, and produce maintain...
GitHub
rspec-testing
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Shou...
GitHub
testing-assistant
Activates when user needs help writing tests, understanding testing patterns, or improving test coverage. Triggers on "write tests", "add unit tests", "test this function", "improve coverage", "mock this", "tes...
GitHub
test-planning
Master test planning with test strategies, test plans, scope definition, and comprehensive testing approaches.
GitHub
performance-testing
Master performance testing with load testing, stress testing, JMeter, k6, and performance benchmarking.
GitHub
test-automation
Master test automation with Selenium, Cypress, Playwright, framework design, and maintainable automated tests.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.