test-local
Skill2 starsChanged 6 months agoMITView on GitHub
Local dev testing workflow — verify test environment, provision infrastructure (Docker, Testcontainers), run multi-level test suite (unit → integration → E2E), coverage analysis, quality gate. Applies QA Engineer role. Use for full local QA cycle before commit or PR.
- Reads credentials
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/agent365-skillstheir own version, first seen Oct 13, 2026
- searlsco/prove_ittheir own version, first seen Mar 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- searlsco/prove_it★ 198same name
- microsoft/agent365-skills★ 50same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- social-media-managerSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 19 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read TESTING.md at the project root (and per-service TESTING.md in monorepos) for test infrastructure, commands, credentials, and …
- Distinctive: line 26
Ask the user (or extract from context):
- Distinctive: line 32
If invoked by another workflow — extract scope from parent context.
- Distinctive: line 49
Read AGENTS.md and scan project files to determine:
- Distinctive: line 68
Before running tests, verify the local environment is ready.
- Distinctive: line 77
If Docker is not running — notify user and stop.
- Distinctive: line 81
Check that ports needed by test services are available:
- Distinctive: line 90
If conflicts found — report which process holds the port.
- Distinctive: line 94
Check for test-specific environment configuration:
- Very specific: line 98
Read only .env.example for reference — never log or output actual .env values
- Distinctive: line 102
Verify project dependencies are installed:
- Very specific: line 111
If dependencies are stale — suggest npm install / pip install -r requirements.txt / etc.
- Distinctive: line 119
If the project uses Testcontainers — no manual setup needed.
- Very specific: line 127
If the project uses docker-compose.test.yml or similar:
- Distinctive: line 133
Wait for services to be healthy:
- Very specific: line 139
Check health status. If any service is unhealthy — collect logs and diagnose using devops-engineer role.
- Distinctive: line 143
If the project has seed scripts for test data:
- Distinctive: line 146
Run seed scripts after infrastructure is ready
- Distinctive: line 147
Verify seed completed successfully
- Distinctive: line 151
If the project uses only mocks/stubs for unit tests — skip to Step 6.
- Distinctive: line 170
Run only if unit tests pass (or user explicitly requested):
- Distinctive: line 189
Run only if integration tests pass (or user explicitly requested):
- Distinctive: line 210
If user requested or project has them:
- Distinctive: line 220
After all tests pass, run coverage analysis:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test Local
Full QA cycle for local development environments. Verifies test infrastructure, provisions dependencies, runs tests at all levels (unit → integration → E2E), analyzes coverage, and applies quality gates. Orchestrated by qa-engineer role.
Key difference from run-tests skill: This workflow manages the full local test environment lifecycle (setup → test → report → cleanup). run-tests skill is a lightweight follow-up skill that only executes and analyzes tests.
1. Define Scope
Read TESTING.md at the project root (and per-service TESTING.md in monorepos) for test infrastructure, commands, credentials, and organization. This is the authoritative source for how to test the project.
Ask the user (or extract from context):
- Test scope: Full suite / specific module / specific test level (unit / integration / E2E)
- What changed: New feature / bug fix / refactor / pre-commit check / full regression
- Known issues: Any tests expected to fail? Any infra known to be down?
If invoked by another workflow — extract scope from parent context.
2. Apply Roles
Primary: qa-engineer role — owns test strategy, quality gates, and test infrastructure decisions.
Secondary (applied as needed during test execution):
| Need | Role |
| Fix failing unit/integration tests | Stack-specific: java-engineer role / python-engineer role / frontend-engineer role |
| Docker/compose/infra issues | devops-engineer role |
| Test data / database schema | db-engineer role |
| General debugging | software-engineer role |
3. Detect Project Stack
Read AGENTS.md and scan project files to determine:
| Signal | Stack | Test Runner | Container Tool |
package.json + vitest/jest | TypeScript/JS | npx vitest / npx jest | Testcontainers-node |
package.json + playwright | TypeScript/JS (E2E) | npx playwright test | Playwright containers |
pom.xml / build.gradle | Java | mvn test / gradle test | Testcontainers-java |
pyproject.toml / pytest.ini | Python | pytest | Testcontainers-python |
go.mod | Go | go test ./... | Testcontainers-go |
*.csproj | .NET | dotnet test | Testcontainers-dotnet |
Also detect:
- Docker Compose:
docker-compose.yml,docker-compose.test.yml,compose.yaml - Test config files:
.env.test,jest.config.*,vitest.config.*,playwright.config.*,pytest.ini,conftest.py - CI config:
.github/workflows/,Jenkinsfile,.gitlab-ci.yml— extract test commands used in CI for parity
4. Verify Local Environment
Before running tests, verify the local environment is ready.
4a. Docker Daemon
// turbo
docker version --format "Client: {{.Client.Version}} | Server: {{.Server.Version}}"If Docker is not running — notify user and stop. Tests requiring containers will fail.
4b. Port Conflicts
Check that ports needed by test services are available:
// turbo
netstat -ano | findstr ":<port>"Common test ports: 5432 (PostgreSQL), 6379 (Redis), 27017 (MongoDB), 9092 (Kafka), 3306 (MySQL).
If conflicts found — report which process holds the port. Suggest resolution.
4c. Environment Variables
Check for test-specific environment configuration:
- Root
.env— verify it exists and containstest_prefixed variables (e.g.,test_user,test_db_host) - Compare with
.env.example— flag missing test variables - Read only
.env.examplefor reference — never log or output actual.envvalues
4d. Dependencies
Verify project dependencies are installed:
| Stack | Check Command |
| Node.js | node_modules/ exists, package-lock.json up to date |
| Java | mvn dependency:resolve -q |
| Python | Virtual env active, pip check |
| Go | go mod verify |
If dependencies are stale — suggest npm install / pip install -r requirements.txt / etc.
5. Provision Test Infrastructure
Based on project config, set up test dependencies.
5a. Testcontainers (preferred)
If the project uses Testcontainers — no manual setup needed. Testcontainers starts/stops containers automatically per test suite. Verify:
- Docker daemon is running (Step 4a)
- Testcontainers config exists (
.testcontainers.propertiesif needed) - Required images are available (or will be pulled automatically)
5b. Docker Compose
If the project uses docker-compose.test.yml or similar:
docker compose -f docker-compose.test.yml up -dWait for services to be healthy:
docker compose -f docker-compose.test.yml psCheck health status. If any service is unhealthy — collect logs and diagnose using devops-engineer role.
5c. Seed Data
If the project has seed scripts for test data:
- Locate seed scripts (check
AGENTS.md,package.jsonscripts,Makefile,scripts/directory) - Run seed scripts after infrastructure is ready
- Verify seed completed successfully
5d. No Infrastructure Needed
If the project uses only mocks/stubs for unit tests — skip to Step 6.
6. Run Tests
Execute tests in pyramid order: unit → integration → E2E. Stop at first failing level unless user requested full suite.
6a. Unit Tests
// turbo
<unit-test-command>Expected: Fast (< 2 min), high pass rate. If unit tests fail — fix before proceeding.
For failures — delegate to run-tests skill for analysis and auto-fix (Step 3-4 of that workflow).
6b. Integration Tests
Run only if unit tests pass (or user explicitly requested):
<integration-test-command>Expected: Moderate speed (< 10 min). Tests interact with real dependencies (DB, APIs via containers).
Common integration test patterns by stack:
| Stack | Command | Notes |
| Vitest/Jest | npx vitest run --project integration | If workspace configured |
| pytest | pytest tests/integration/ -v | Or pytest -m integration |
| Maven | mvn verify -pl <module> | Failsafe plugin for ITs |
| Go | go test -tags=integration ./... | Build tag separation |
6c. E2E Tests
Run only if integration tests pass (or user explicitly requested):
<e2e-test-command>Prerequisites:
- Application must be running locally (dev server or Docker)
- E2E test config must point to local URL
- Browser binaries installed (Playwright:
npx playwright install)
Common E2E commands:
| Stack | Command |
| Playwright | npx playwright test |
| Cypress | npx cypress run |
| pytest + Selenium | pytest tests/e2e/ -v |
6d. Specialized Tests (optional)
If user requested or project has them:
| Type | When | Command Pattern |
| Performance | Pre-release, after optimization | k6 run tests/load/script.js |
| Security | Pre-release, after auth changes | npm audit / OWASP ZAP scan |
| Accessibility | UI changes | npx playwright test --grep @a11y or axe-core |
7. Coverage Analysis
After all tests pass, run coverage analysis:
| Stack | Command |
| Vitest | npx vitest run --coverage |
| Jest | npx jest --coverage |
| pytest | pytest --cov=<package> --cov-report=term-missing |
| Go | go test -coverprofile=coverage.out ./... && go tool cover -func=coverage.out |
| Maven | mvn jacoco:report |
Compare against test-strategy skill targets:
| Metric | Target | Hard Minimum | Status |
| Line coverage | ≥ 80% | ≥ 60% | [pass/fail] |
| Branch coverage | ≥ 75% | ≥ 50% | [pass/fail] |
| New code coverage | ≥ 90% | ≥ 80% | [pass/fail] |
Flag modules with coverage below hard minimum.
8. Quality Gate
Evaluate overall test quality:
| Gate | Criteria | Result |
| Unit tests | All pass | ✅ / ❌ |
| Integration tests | All pass (if run) | ✅ / ❌ / ⏭️ skipped |
| E2E tests | All pass (if run) | ✅ / ❌ / ⏭️ skipped |
| Coverage | Meets targets | ✅ / ⚠️ below target / ❌ below minimum |
| No flaky tests | Zero retried tests | ✅ / ⚠️ |
| No new warnings | Lint + type checks clean | ✅ / ❌ |
Decision:
| Result | Action |
| All gates pass | ✅ PASS — safe to commit/PR |
| Coverage warning only | ⚠️ PASS with notes — consider adding tests |
| Any test failure | ❌ FAIL — fix before commit |
| Flaky tests detected | ⚠️ PASS with action — file flaky test issue |
9. Cleanup
After testing completes:
- Stop test containers (if Docker Compose was used):
docker compose -f docker-compose.test.yml down -v - Remove test data (if seed scripts ran outside containers)
- Report leftover containers (if any test containers weren't cleaned up)
Testcontainers handles its own cleanup automatically — verify no orphaned containers remain.
10. Summary
## Local Test Summary
### Environment
- **Stack**: [detected stack]
- **Docker**: [version] | Test infra: [Testcontainers / Docker Compose / none]
- **Env issues**: [none / list]
### Test Results
| Level | Total | Passed | Failed | Skipped | Duration |
|-------|-------|--------|--------|---------|----------|
| Unit | X | X | X | X | Xs |
| Integration | X | X | X | X | Xs |
| E2E | X | X | X | X | Xs |
### Coverage
| Metric | Value | Target | Status |
|--------|-------|--------|--------|
| Line | X% | 80% | ✅/❌ |
| Branch | X% | 75% | ✅/❌ |
| New code | X% | 90% | ✅/❌ |
### Coverage Gaps
- [file/module] — [current%] — [uncovered areas]
### Quality Gate: ✅ PASS / ❌ FAIL
- [gate details]
### Failures Fixed (if any)
- [test] — [issue] — [fix]
### Remaining Issues
- [issue] — [action needed]
### Follow-up
- [recommendations]Integration
- Roles:
qa-engineerrole (primary), stack-specific roles (test fixes),devops-engineerrole (infra issues) - Skills:
test-strategyskill (test patterns, coverage targets) - follow-up skills:
run-testsskill (test execution and auto-fix for failures) - Called by:
feature-devskill (pre-commit testing),bugfixskill (verify fix) - Follow-up:
pre-commitskill (quality gate),create-prskill (submit changes)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

