meddev-unit-testing
/meddev-unit-testing
Establish patterns for unit tests that verify software units against requirements with safety-class-appropriate rigor. Use when working on unit testing in medical device software.
- Author
- aminalam ↗
- Repository
- meddev-agent-skills ↗
- Licence
- MIT
- Last repository change
- 19.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Establish patterns for unit tests that verify software units against requirements with safety-class-appropriate rigor. Use when working on unit testing in medical device software.
Original author description
Establish patterns for unit tests that verify software units against requirements with safety-class-appropriate rigor. Use when working on unit testing in medical device software.
How it works
- Purpose
- When to Apply
- Requirements (testable)
- Recommended Practices
- Patterns
- Anti-Patterns (risks)
- Verification Checklist
- Traceability
- References
- Changelog
SKILL.md preview
---
name: meddev-unit-testing
description: Establish patterns for unit tests that verify software units against requirements with safety-class-appropriate rigor. Use when working on unit testing in medical device software.
license: MIT
metadata:
skill_id: TEST-UNIT
version: 1.1.0
last_updated: '2026-05-21'
applies_to: Class A, Class B, Class C
jurisdiction: Global
prerequisites: FW-EMBEDDED-C, FW-HAL, ARCH-SAFETY-CLASS
category: testing
---
# Unit Testing for Medical Device Software
## Purpose
Establish patterns for unit tests that verify software units against requirements with safety-class-appropriate rigor.
## When to Apply
- New or changed functions/modules, especially safety-related.
- Bug fixes to prevent regression.
## Requirements (testable)
1. Implement Units [Class A, B, C]: Implement each software unit per design. Rationale: 5.5.1.
2. Verification Process [Class B, C]: Define strategies, methods, and procedures for unit verification; evaluate test procedure adequacy. Rationale: 5.5.2.
3. Acceptance Criteria [Class B, C]: Define acceptance criteria before integration; confirm units meet criteria (requirements, interface consistency, coding standards). Rationale: 5.5.3.
4. Class C Criteria [Class C]: Where design requires, add criteria for event sequencing, data/control flow, resource use, fault handling, initialization, diagnostics, memory behaviour, and boundary conditions. Rationale: 5.5.4 (engineering checklist).
5. Execute and Record [Class B, C]: Perform unit verification and document results. Rationale: 5.5.5.
6. Structure: Use Arrange-Act-Assert; deterministic tests with clear preconditions. Rationale: reliable evidence.
7. Isolation: Mock hardware/HAL; no real hardware in unit tests. Rationale: determinism.
8. Traceability: Each test links to requirement and risk control IDs. Rationale: compliance.
9. CI Integration: Run in CI; archive results. Rationale: continuous assurance.
## Recommended Practices
- Keep tests fast (<1s each) to encourage frequent runs.
- Use table-driven tests for combinations; parametrize to reduce duplication.
- Enforce `-Wall -Wextra -Werror` in test builds.
- Add sanitizers (ASan/UBSan) on host where possible for non-embedded logic.
## Patterns
C unit test with Unity (example):
```c
// TEST-UNIT-105 covers REQ-C-TYPE-01
TEST(SumSamples, AccumulatesAll) {
uint16_t s[] = {1, 2, 3};
CHECK_EQUAL(6, sum_samples(s, 3));
}
```
Boundary test:
```c
// TEST-UNIT-110 covers REQ-DEF-INPUT-01
TEST(ValidateFlow, RejectsNegative) {
CHECK_FALSE(validate_flow(-1.0f));
}
```
Mock HAL:
```c
// TEST-UNIT-120 covers REQ-HAL-IF-01
MOCK_FUNCTION_WITH_RETURN(hal_status_t, hal_uart_write, const uint8_t*, size_t, size_t*);
```
## Anti-Patterns (risks)
- Tests that depend on real timing or hardware -> risk: flakiness.
- No negative/boundary tests -> risk: missed edge defects.
- Untagged tests with requirements -> risk: broken traceability.
- Ignoring test failures in CI -> risk: regressions ship.
## Verification Checklist
- [ ] Tests follow AAA and are deterministic.
- [ ] Coverage meets class targets (branch/MC-DC for critical logic).
- [ ] Hardware/HAL calls mocked; no real hardware dependencies.
- [ ] Requirements/risk IDs referenced in tests.
- [ ] Negative/boundary cases included.
- [ ] Tests run in CI with warnings-as-errors; failures block merges.
## Traceability
- Map `TEST-UNIT-###` to `REQ-###`; store coverage reports per release.
## References
- IEC 62304:2006+A1:2015, 5.5 (software unit implementation and verification).
- `TEST-COVERAGE` (informative MC/DC depth by class).
- ISO 14971:2019 for risk-based test depth.
## Changelog
- 1.1.0 (2026-05-21): Aligned with 5.5.2–5.5.5 and Class C acceptance topics.
- 1.0.0 (2026-01-04): Initial unit testing skill with coverage targets and traceability.
## Audit History
- **2026-01-04**: Audit performed. Verified:
- IEC 62304 section 5.5 reference for unit implementation/verification is accurate
- MC/DC requirement for Class B/C control logic aligns with industry practice
- Unity test framework examples are syntactically correct
Versions
The database has no other skills named meddev-unit-testing.
Database snapshot: 13.11.2026 · package version 0411bd7bba0f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100meddev-automated-testing
Define how to automate tests (unit, integration, system/HIL where feasible) in CI/CD pipelines for medical devices with gating and evidence capture. Use when working on automated testing in medical device software. - 100meddev-fault-tolerance
Provide patterns for detecting, containing, and recovering from faults in medical device software, scaled to safety class. Use when working on fault tolerance in medical device software. - 90unit-testing
Unit testing patterns: Vitest config with v8 coverage, Testing Library behavior testing, MSW for HTTP mocking (vs jest.mock), it.each parametrized tests, spies vs mocks vs stubs, testing async code, snapshot testing guidelines. Use when writing unit and component tests. - 100unit-testing
Write and review unit tests for Gather V2. Use when writing tests, reviewing test code, debugging test failures, or asking about testing patterns. - 100unit-tests
Guardrails for adding unit tests in bklit-ui without over-testing. Use when the user mentions unit test, unit tests, tests, test coverage, add tests, write tests, vitest, jest, or asks whether something should be tested. - 100testing-expert
Expert-level software testing with unit tests, integration tests, E2E tests, TDD/BDD, and testing best practices. Use when the user mentions TDD, BDD, unit tests, integration tests, or end-to-end tests, or when the task involves Testing Fundamentals, Unit Testing, Integration…