ECSS Test Centres -- Reference Test Process Sequence (space-systems/ecss/q2007-test-sequence)
Use when the task is laying a test campaign plan against the Annex B
reference flow of ECSS-Q-ST-20-07C: a sequence of phases has been
proposed and the question is whether it covers the typical process, runs
in the right direction, and adds up to a schedule.
Domain quick reference
- The reference flow is informative, so conformance is a comparison and
not a pass mark. What it fixes is the direction: request, specify,
prepare, configure, review, run, package, report. A plan is graded on
coverage and order against that flow, not on matching it phase for
phase.
- Mandatory and optional are different failures. An optional phase left
out -- a facility feasibility study, an incoming inspection, an item
return leg -- is a campaign choice. A mandatory phase left out is a
gap unless somebody wrote down why, and the rationale is what turns an
omission into tailoring.
- Order violations are local. A single phase dropped into the wrong slot
produces one inversion against its neighbour, and reporting the pair is
what makes it fixable; reporting only that the plan is unordered sends
the planner back through the whole list.
- A stale tailoring rationale is worth reporting. A rationale recorded
for a phase that is planned anyway usually means the plan changed and
the justification file did not, and the next reviewer will read the
rationale as still applying.
- The durations are what turn the flow into a campaign. Contiguous day
windows from the campaign start give each phase a slot and the campaign
a total, which is the number the facility booking is made against.
Workflow
- Normalise the proposed plan: phase, duration in whole days, in the
planner's own order. Reject an unknown phase, a phase planned twice,
and a non-positive or fractional duration.
- Normalise the tailoring rationales and refuse one that names a phase
outside the reference flow or carries no text.
- Grade coverage phase by phase over the mandatory set: planned,
tailored against a rationale, or an omission that blocks.
- Report any rationale recorded for a phase that is in fact planned.
- Walk the plan and name every adjacent pair whose reference positions
run backwards.
- Lay the durations into contiguous windows from the campaign start day
and take the campaign total from the first and last window.
- Return the mandatory coverage fraction, the order verdict and the
decision: conforms, conforms with tailoring, or non-conforming.
Pitfalls
- Reading full coverage as conformance. A plan can contain every
mandatory phase and still run the review after the test; coverage and
order are graded separately and both appear in the decision.
- Treating an omission as tailoring because somebody mentioned it. The
rationale has to be recorded against the phase, otherwise the next
reviewer cannot tell a decision from an oversight.
- Reporting a single unordered verdict. Every inversion is a pair, and
the pair is what the planner moves.
- Grading optional phases as gaps. They are in the flow because a
campaign often needs them, not because every campaign does, and
raising them as findings buries the mandatory omission that matters.
- Summing durations without laying out the windows. The total is the same
number, but the window is what shows the facility when each phase
actually occupies it.
Behavior contract (gate 3)
The reference flow, the plan and tailoring normalisation, the mandatory
coverage grading, the stale-rationale report, the adjacent-pair order
check, the contiguous day windows and the conformance decision are
exercised by the gate 3 contract test:
scripts/test_q2007_test_sequence.py against
scripts/q2007_test_sequence_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_q2007_test_sequence.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: q2007-test-sequence3description: "Structure a test campaign plan against the typical test process sequence offered by ECSS-Q-ST-20-07C Annex B: lay the planned phases on the reference flow, report a mandatory phase that is neither planned nor omitted against a recorded tailoring rationale, name every adjacent pair that runs the flow backwards, flag a rationale left behind for a phase that is planned anyway, and lay the durations into contiguous day windows so the plan carries a schedule. Use when a campaign plan is being drafted or an offered sequence is being compared with the reference. Trigger: ecss, q-st-20-07c, typical-test-process-sequence, test-campaign-phase-ordering, test-phase-precedence-conformance, test-sequence-tailoring-rationale, campaign-phase-day-windows."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/q2007-test-sequence15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-20-07-test-centre-scope, q2007-test-sequence, typical-test-process-sequence, test-campaign-phase-ordering, test-phase-precedence-conformance, test-sequence-tailoring-rationale, campaign-phase-day-windows]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Test Centres -- Reference Test Process Sequence (space-systems/ecss/q2007-test-sequence)2324Use when the task is laying a test campaign plan against the Annex B25reference flow of ECSS-Q-ST-20-07C: a sequence of phases has been26proposed and the question is whether it covers the typical process, runs27in the right direction, and adds up to a schedule.2829## Domain quick reference3031- The reference flow is informative, so conformance is a comparison and32 not a pass mark. What it fixes is the direction: request, specify,33 prepare, configure, review, run, package, report. A plan is graded on34 coverage and order against that flow, not on matching it phase for35 phase.36- Mandatory and optional are different failures. An optional phase left37 out -- a facility feasibility study, an incoming inspection, an item38 return leg -- is a campaign choice. A mandatory phase left out is a39 gap unless somebody wrote down why, and the rationale is what turns an40 omission into tailoring.41- Order violations are local. A single phase dropped into the wrong slot42 produces one inversion against its neighbour, and reporting the pair is43 what makes it fixable; reporting only that the plan is unordered sends44 the planner back through the whole list.45- A stale tailoring rationale is worth reporting. A rationale recorded46 for a phase that is planned anyway usually means the plan changed and47 the justification file did not, and the next reviewer will read the48 rationale as still applying.49- The durations are what turn the flow into a campaign. Contiguous day50 windows from the campaign start give each phase a slot and the campaign51 a total, which is the number the facility booking is made against.5253## Workflow54551. Normalise the proposed plan: phase, duration in whole days, in the56 planner's own order. Reject an unknown phase, a phase planned twice,57 and a non-positive or fractional duration.582. Normalise the tailoring rationales and refuse one that names a phase59 outside the reference flow or carries no text.603. Grade coverage phase by phase over the mandatory set: planned,61 tailored against a rationale, or an omission that blocks.624. Report any rationale recorded for a phase that is in fact planned.635. Walk the plan and name every adjacent pair whose reference positions64 run backwards.656. Lay the durations into contiguous windows from the campaign start day66 and take the campaign total from the first and last window.677. Return the mandatory coverage fraction, the order verdict and the68 decision: conforms, conforms with tailoring, or non-conforming.6970## Pitfalls7172- Reading full coverage as conformance. A plan can contain every73 mandatory phase and still run the review after the test; coverage and74 order are graded separately and both appear in the decision.75- Treating an omission as tailoring because somebody mentioned it. The76 rationale has to be recorded against the phase, otherwise the next77 reviewer cannot tell a decision from an oversight.78- Reporting a single unordered verdict. Every inversion is a pair, and79 the pair is what the planner moves.80- Grading optional phases as gaps. They are in the flow because a81 campaign often needs them, not because every campaign does, and82 raising them as findings buries the mandatory omission that matters.83- Summing durations without laying out the windows. The total is the same84 number, but the window is what shows the facility when each phase85 actually occupies it.8687## Behavior contract (gate 3)8889The reference flow, the plan and tailoring normalisation, the mandatory90coverage grading, the stale-rationale report, the adjacent-pair order91check, the contiguous day windows and the conformance decision are92exercised by the gate 3 contract test:93scripts/test_q2007_test_sequence.py against94scripts/q2007_test_sequence_logic.py (stdlib unittest, offline). Run:95python3 scripts/test_q2007_test_sequence.py9697## Compliance9899- ECSS standards are freely downloadable (ESA); cite the source and100 paraphrase per standards-map.yaml.101- compliance: STANDARDS-REF, gated: false.