integration-testing-discipline Skill
4 principles for E2E testing discipline — observe first, fix in batches, expect long durations, check container state directly. NO FIXES DURING OBSERVATION RUNS. Published by microsoft in amplifier-bundle-superpowers.
What is integration-testing-discipline Skill?
4 principles for E2E testing discipline — observe first, fix in batches, expect long durations, check container state directly. NO FIXES DURING OBSERVATION RUNS. Published by microsoft in amplifier-bundle-superpowers. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use integration-testing-discipline Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-bundle-superpowers
- Skill file: skills/integration-testing-discipline/SKILL.md
What it does
4 principles for E2E testing discipline — observe first, fix in batches, expect long durations, check container state directly. NO FIXES DURING OBSERVATION RUNS.
Skill instructions
Integration Testing Discipline The Core Principle OBSERVE FIRST. FIX IN BATCHES. NEVER FIX DURING ACTIVE E2E RUNS. When running integration tests or E2E validation, your job is to CAPTURE ALL failures first, then fix them systematically. Making code changes during a running test invalidates that test run. The Four Principles Principle 1: Don't Fix During Observation Runs DO: Let the E2E run complete (or fail with a real error), capture ALL failure points, then fix everything as a coordinated batch. DON'T: See one failure, fix it immediately, and continue the same E2E run. Why: Code changes during E2E runs invalidate the running test. You lose the ability to trust that run's results. Example: ❌ WRONG: 1. E2E run finds validation error 2. Fix validation immediately 3. Continue same E2E run 4. Find auth error 5. Fix auth immediately 6. Continue same E2E run → Result: Can't trust this run's success ✅ RIGHT: 1. E2E run finds validation error — RECORD IT 2. E2E run finds auth error — RECORD
Explore related resources
Frequently asked questions
What is integration-testing-discipline?
integration-testing-discipline is a open-source AI agent skill with Copy skill directory. 4 principles for E2E testing discipline — observe first, fix in batches, expect long durations, check container state directly. NO FIXES DURING OBSERVATION RUNS.
Who is integration-testing-discipline best for?
integration-testing-discipline is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install integration-testing-discipline?
Install or run integration-testing-discipline using Copy skill directory. Check integration-testing-discipline for the latest setup command.
Is integration-testing-discipline actively maintained?
integration-testing-discipline may need a closer maintenance check before production use.
Auto-fetched from GitHub.
