# Verification Testing

> How to write tests and verification evidence for ASPICE. Use this skill when creating unit tests (SWE.4), integration tests (SWE.5, SYS.4), or qualification tests (SWE.6, SYS.5). Also use when writing test plans (WP 08-52), test specifications (WP 08-50), recording test results (WP 13-50, WP 13-25), deriving tests from verification criteria (WP 17-50), creating Doorstop test spec items (UT, SWIT, SYIT, SWQT, SYQT), or when you need to understand what each test level verifies against. Consult this whenever you see 'verification,' 'qualification,' 'regression,' or 'test coverage' in an ASPICE context.

- Skill: `ksmyl/verification-testing` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add ksmyl/verification-testing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ksmyl/verification-testing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: ksmyl (https://skillmd.com/u/ksmyl)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ksmyl/verification-testing

---


# Verification and Testing for ASPICE

## What Each Test Level Verifies Against

This is the core principle — each test level on the right side of the V verifies against its counterpart on the left side.

| Test Level | ASPICE Process | Tests Against | Doorstop Prefix | Parent |
|------------|---------------|---------------|-----------------|--------|
| Unit verification | SWE.4 | Software detailed design (SWDD) | UT | SWDD |
| SW integration test | SWE.5 | Software architecture (SWARCH) | SWIT | SWARCH |
| System integration test | SYS.4 | System architecture (SYSARCH) | SYIT | SYSARCH |
| SW qualification test | SWE.6 | Software requirements (SWRS) | SWQT | SWRS |
| System qualification test | SYS.5 | System requirements (SYSRS) | SYQT | SYSRS |

Understanding this mapping is essential — a unit test that tests against requirements (rather than design) is misclassified and will confuse an assessor.

## Deriving Tests from Verification Criteria

1. Read each requirement from the relevant Doorstop document.
2. Find its `verification_criteria` attribute (or look up WP 17-50).
3. Design a test that exercises exactly that criterion.
4. The verification criteria define pass/fail — the test implements them.

Example flow:
```
SWRS001: "SOC accuracy +/-5%"
  -> verification_criteria: "Simulate charge/discharge cycle, compare estimated vs reference SOC at 10 points, all within 5%."
  -> SWQT001: test_swqt_soc_accuracy() implements this exact check.
```

## Detailed References

- For WP 08-52 (test plan), WP 08-50 (test spec), and WP 13-50 (test results) detailed formats, read `references/test-artifacts.md`.
- For Doorstop test spec item format, link commands, regression strategy, and coverage requirements, read `references/doorstop-test-items.md`.
- For test framework and coverage tool table by language, read `references/technology-table.md`.