Executes testing and regression workflows with a focus on boundary cases and evidence-based verification.
Install
mkdir -p .claude/skills/test-jacksmack1971 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14552" && unzip -o skill.zip -d .claude/skills/test-jacksmack1971 && rm skill.zipInstalls to .claude/skills/test-jacksmack1971
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Run DegenExus pytest planning and regression workflow with Prove-It, FSV-AAA, and edge-case evidence.Key capabilities
- →Identify the source of truth and current test patterns
- →Write or describe failing regression tests for bugs
- →Apply FSV-AAA for test structure
- →Cover boundary and equivalence classes in tests
- →Mock LLM providers, network calls, time, and randomness
- →Run targeted pytest then broader regression tests
How it works
The skill identifies test patterns, writes failing regressions for bugs, and applies FSV-AAA for test structure. It covers boundary cases and mocks external dependencies before running tests.
Inputs & outputs
When to use test
- →Writing regression tests
- →Verifying bug fixes
- →Auditing edge cases
About this skill
Test Workflow
test-engineer is the canonical owner for DegenExus test authoring and coverage analysis. test-writer is a read-only deprecated alias and must not be routed for new work.
Required References
.claude/rules/synergy-contract.yml.claude/rules/evidence-schema.yml.claude/skills/test-regression/SKILL.md.claude/skills/fsv-verify/SKILL.md.claude/skills/edge-case-audit/SKILL.md
Steps
- Identify the source of truth and current test patterns.
- For bugs, write or describe the failing regression first and record
failing_before. - Use FSV-AAA where practical: PRE source-of-truth read, one ACT, POST reread, expected DIFF assertion.
- Cover boundary/equivalence classes: empty/zero, min/max boundary, malformed/adversarial input, and ordering/concurrency where applicable.
- Use
pytest-mock'smockerfixture; do not importunittest.mockdirectly. - Mock LLM providers, yfinance/network calls, time, and randomness.
- Run targeted pytest first, then broader regression tests when feasible.
- Emit
.claude/rules/evidence-schema.ymlfields withedge_cases,failing_before, andpassing_afterevidence when applicable.
When not to use it
- →When `test-writer` is routed for new work
Limitations
- →The skill does not use `test-writer` for new work.
- →The skill requires documentation of edge cases and failing/passing states.
- →The skill uses `pytest-mock`'s `mocker` fixture, not `unittest.mock` directly.
How it compares
This workflow systematically structures tests with FSV-AAA and covers specific boundary conditions, unlike ad-hoc testing.
Compared to similar skills
test side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| test (this skill) | 0 | 2mo | No flags | Advanced |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| python-playground | 2 | 4mo | Review | Beginner |
| mflux-manual-testing | 2 | 2mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
python-playground
pydantic
Run and test Python code in a dedicated playground directory. Use when you need to execute Python scripts, test code snippets, investigate CPython behavior, or experiment with Python without affecting the main codebase.
mflux-manual-testing
filipstrand
Manually validate mflux CLIs by exercising the changed paths and reviewing output images/artifacts.
examples-auto-run
openai
Run python examples in auto mode with logging, rerun helpers, and background control.
extract-fuzzer-repro
noir-lang
Extract a Noir reproduction project from fuzzer failure logs in GitHub Actions. Use when a CI fuzzer test fails and you need to create a local reproduction.
klingai-known-pitfalls
jeremylongshore
Manage avoid common mistakes when using Kling AI. Use when troubleshooting issues or learning best practices to prevent problems. Trigger with phrases like 'klingai pitfalls', 'kling ai mistakes', 'klingai gotchas', 'klingai best practices'.