testing
GitHub指导是否添加测试、设计回归测试或执行TDD。遵循仓库策略，默认不新增测试，仅在明确请求或复现回归时添加自动化测试，避免过度测试。
Trigger Scenarios
Install
npx skills add yielded-dev/auth --skill testing -g -y
SKILL.md
Frontmatter
{
"name": "testing",
"license": "MIT",
"metadata": {
"source": "https:\/\/github.com\/danieljvdm\/dev-kit\/tree\/2bda762e1573fbfdaf5c5aa6c06abe952d812a0b\/skills\/testing",
"source_skill": "testing",
"source_commit": "2bda762e1573fbfdaf5c5aa6c06abe952d812a0b"
},
"description": "Decide whether committed tests are warranted, design regression tests, or follow explicitly requested TDD."
}
Testing
Follow the repository's testing policy and the user's requested scope. Default to no new tests or test infrastructure; verification remains required. Use existing checks and direct observation of the real workflow first. Add committed automation only for an explicit user request for tests or a reproduced regression, with a concrete gap that existing evidence cannot adequately cover. Read test selection before expanding tests, fixtures, mocks, or harnesses.
- Whether to add, retain, or remove a test: test selection.
- A test boundary, substitute, or mocking decision: test design.
- A justified isolated test, or an explicit TDD, red-green, or test-first request: failure-first development. Ordinary feature verification does not require this workflow.
Honor an explicit testing request within its scope. Express expectations independently of implementation, exercise a stable public boundary, and follow repository evidence and placement rules. Never replace an unnecessary unit test with a larger integration or E2E suite. Reuse valid evidence, keep the final suite green, and stop when the requested outcomes are sufficiently verified.
Version History
- 72bfeeb Current 2026-10-18 15:35
