Automated summary
This skill enforces a mandatory TDD/BDD testing strategy with actual test execution and coverage verification before commits.
Strengths
- Ensures at least 80% code coverage
- Uses clear, readable BDD syntax
- Requires real test execution with output evidence
- Promotes deterministic and fast tests
Limitations
- May slow down initial development iterations
- Requires strict team discipline
- Does not cover complex UI testing
When building production-critical features where reliability and regression prevention are paramount.
During rapid exploration or prototyping phases where requirements are unclear and change often.
Security analysis
SafeThe skill instructs running standard test commands (pytest, npm test) and does not contain destructive, exfiltrating, or obfuscated instructions. No external payloads, no disabling of safety measures. Execution of tests is a normal development activity.
No concerns found
How this analysis is madeExamples
Write a BDD test for the login feature before implementing the actual login logic. Use describe/it syntax and test that a valid user can log in with correct credentials.Run the existing test suite with coverage reporting for the backend Python code using pytest with --cov=app, then show the test execution output and confirm coverage is at least 80%.Create failing tests for a new API endpoint /api/users that returns a list of users. Then implement the endpoint to make the tests pass, ensuring all tests run successfully with ≥80% coverage.Mandatory TDD/BDD Testing Strategy
Core Principles
- BDD Style:
describe/itsyntax for tests - Test-First: Write failing tests before implementation
- Deterministic: Use data-testid, role, label selectors
- Fast & Light: Prefer unit/integration tests
Example BDD Structure
describe('Calculator', () => {
it('adds two positive numbers', () => {
expect(add(5, 7)).to.equal(12);
});
});
Mandatory Test Execution
Requirements
- Actually run test suite with coverage
- Confirm all tests pass
- Verify ≥80% coverage
- Include test execution output
Backend (Python)
python3 -m pytest tests/ -v --cov=app --cov-report=term-missing
Frontend (TypeScript)
npm test -- --coverage
Evidence Requirement
## Test Execution Evidence
### Command:
`pytest tests/test_showcase_videos.py -v --cov=app.api`
### Output:
20 passed in 3.42s
Coverage: 87%
Enforcement
- MANDATORY with NO EXCEPTIONS
- Tests run LOCALLY before commit
- Test output in PR descriptions
- Actual coverage percentages required
Violation Consequences
- Broken code in production
- Undetected bugs
- Loss of test suite confidence
Reference
references/bdd-patterns.mdreferences/coverage-requirements.md
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/mandatory-tdd-bdd-testing-strategy-mm5t8a8j/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/mandatory-tdd-bdd-testing-strategy-mm5t8a8j' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mandatory-tdd-bdd-testing-strategy-mm5t8a8j/download' --output '.skill-downloads/mandatory-tdd-bdd-testing-strategy-mm5t8a8j/SKILL.md.part' && mv '.skill-downloads/mandatory-tdd-bdd-testing-strategy-mm5t8a8j/SKILL.md.part' '.skill-downloads/mandatory-tdd-bdd-testing-strategy-mm5t8a8j/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Requirements
- Actually run test suite with coverage
- Confirm all tests pass
- Verify ≥80% coverage
- Include test execution output
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/mandatory-tdd-bdd-testing-strategy-mm5t8a8j/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.