Backend Test Plan
Create backend test plans for APIs, services, databases, auth, integrations, and background jobs. Use when Codex is asked to define unit, integration, contract, migration, security, performance, or regression tests for backend changes.
Install
$ agentstack add skill-jeremylongworth-source-agentskills-backend-test-plan ✓ 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-jeremylongworth-source-agentskills-backend-test-plan) 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
Backend Test Plan
Core Workflow
- Identify changed behavior, risk areas, data stores, external integrations,
auth boundaries, and production impact.
- Define coverage across unit, integration, contract, database/migration,
authorization, error, performance, and regression tests.
- Specify fixtures, test data, mocks/fakes, environments, and cleanup needs.
- Tie each test to an acceptance criterion or failure mode.
- Include non-happy paths: denied access, invalid input, dependency failure,
concurrency, retries, and rollback.
- Recommend what must pass before merge, release, or rollback.
Safety Rules
- Do not claim tests passed unless output is available.
- Do not use real production data or credentials in test plans.
- Escalate testing gaps for auth, payments, migrations, customer data,
background jobs, and public APIs.
Deliverable Shape
For backend test plans, provide:
- Change and risk summary
- Test matrix
- Fixtures and environments
- Contract and integration coverage
- Data/migration coverage
- Auth and security coverage
- Performance or load checks when relevant
- Merge/release gates
References
- Read
references/backend-test-plan-checklist.mdwhen creating or reviewing
backend test coverage.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jeremylongworth-source
- Source: jeremylongworth-source/AgentSkills
- 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.