meddev-unit-testing
/meddev-unit-testing
Ustanawia wzorce testów jednostkowych, które weryfikują jednostki oprogramowania względem wymagań z rygorem odpowiednim do klasy bezpieczeństwa.
- Autor
- aminalam ↗
- Repozytorium
- meddev-agent-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 19.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 19.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Ustanawia wzorce testów jednostkowych, które weryfikują jednostki oprogramowania względem wymagań z rygorem odpowiednim do klasy bezpieczeństwa.
Oryginalny opis (EN)
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.
Jak działa
- Purpose
- When to Apply
- Requirements (testable)
- Recommended Practices
- Patterns
- Anti-Patterns (risks)
- Verification Checklist
- Traceability
- References
- Changelog
Podgląd SKILL.md
---
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
Wersje
W bazie nie ma innych skilli o nazwie meddev-unit-testing.
Migawka bazy z 13.11.2026 · wersja paczki 0411bd7bba0f (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100meddev-automated-testing
Określa automatyzację testów (jednostkowych, integracyjnych, systemowych i HIL) w pipeline'ach CI/CD dla wyrobów medycznych, z bramkami jakości i gromadzeniem dowodów. - 100meddev-fault-tolerance
Podaje wzorce wykrywania, ograniczania i odzyskiwania po błędach w oprogramowaniu wyrobów medycznych, skalowane do klasy bezpieczeństwa. - 90unit-testing
Opisuje wzorce testów jednostkowych: Vitest z pokryciem v8, testowanie zachowania przez Testing Library, MSW zamiast jest.mock, testy parametryzowane i asynchroniczne. - 100unit-testing
Pisze i przegląda testy jednostkowe w projekcie Gather V2, a także pomaga w błędach testów i wzorcach testowania. - 100unit-tests
Pilnuje zasad dodawania testów jednostkowych w bklit-ui, żeby nie testować ponad miarę. - 100testing-expert
Prowadzi testowanie oprogramowania na poziomie eksperckim: testy jednostkowe, integracyjne i E2E, TDD i BDD oraz dobre praktyki testowania.