Test Writer
Generate comprehensive unit tests with edge cases and mocks
Install
$ agentstack add skill-amelmo-loadout-test-writer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-amelmo-loadout-test-writer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Test Writer
Given a function, hook, or module, generate comprehensive unit tests:
- Happy path: Normal usage with expected inputs and outputs
- Edge cases: Empty inputs, boundary values, max/min, unicode, null/undefined
- Error paths: Invalid inputs, network failures, timeout scenarios
- Async behavior: Promise resolution, rejection, loading states
- Integration: How the unit interacts with its direct dependencies
Rules
- Use
vitestwithdescribe/itblocks - Mock external dependencies with
vi.mock()— never mock the unit under test - Use
@testing-library/reactandrenderHook()for React hooks - Each test should verify exactly one behavior
- Use descriptive test names:
it("returns empty array when input is null") - Include setup/teardown in
beforeEach/afterEachwhen shared across tests - Aim for 90%+ branch coverage on the unit under test
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AmElmo
- Source: AmElmo/loadout
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.