Testing General
Language-agnostic testing principles: boundary assertions, null checks, and behavior-driven test naming
Install
$ agentstack add skill-ucdavis-ai-skills-registry-testing-general ✓ 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-ucdavis-ai-skills-registry-testing-general) 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
Testing — General
Structure
- One test file per source module.
- Name tests as specifications:
"should when ". - Group related cases with describe/context blocks.
- Follow Arrange-Act-Assert (AAA), with a blank line between each phase.
What to Test
- Happy path: expected inputs produce expected outputs.
- Edge cases: empty input, zero, maximum values, boundary conditions.
- Error paths: invalid input, missing data, external failures.
Mocking
- Mock only what you don't control: HTTP calls, databases, filesystems, clocks.
- Never mock the unit under test.
- Restore mocks after each test to prevent state leakage.
Assertions
- Assert specific values, not just that something was called.
- On error paths, assert both the error type and message.
- Avoid assertions inside loops — use parameterized tests instead.
Coverage
- Focus on behavior coverage, not line coverage.
- 100% coverage does not mean a test suite is complete.
- Missing: edge cases, concurrent access, failure paths that coverage tools can't see.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ucdavis
- Source: ucdavis/ai-skills-registry
- 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.