software-testinglisted
Install: claude install-skill ashfordeOU/aero-agent-skills
# DO-178C Requirements-Based Software Testing (avionics/do178c/software-testing)
Use when the task is generating test cases from DO-178C requirements,
counting the test cases a structural coverage metric demands for a boolean
condition, or measuring statement, decision, and MC/DC coverage against the
objectives for the software level.
## Domain quick reference
- Requirements-based testing: every high-level and low-level requirement is
exercised by at least one test case derived from that requirement (normal
range, plus robustness and boundary cases the requirement implies).
- Statement coverage: every executable statement runs at least once. Test
cases needed per statement: 1.
- Decision coverage: every decision (boolean expression) takes both
outcomes. Test cases needed per decision: 2.
- MC/DC (modified condition/decision coverage): every condition in a
decision takes both outcomes, and each condition independently affects
the decision outcome. For a compound condition with n independent terms:
n + 1 test cases.
- Worked count: A AND B AND C (3 terms) needs 4 MC/DC cases: TTT, FTT,
TFT, TTF.
- Worked count: A OR B OR C OR D (4 terms) needs 5 MC/DC cases: FFFF,
TFFF, FTFF, FFTF, FFFT.
- Coverage objectives per level (DO-178C Table A-7, summarized): level A =
statement + decision + MC/DC; level B = statement + decision; level C =
statement; levels D and E = none required.
- Required structural coverage: 100% of the metric the level demands. The
test