ECSS System Testing — Test Campaign Management (space-systems/ecss/e1003-management)
Use when the task is to organise a system-level test campaign per
ECSS-E-ST-10C §4.3.1 — assigning responsibilities between customer and
supplier, verifying test readiness before a run is authorised, and
sequencing campaign phases in the required order.
Domain quick reference
- §4.3.1 partitions test-campaign responsibilities into two roles.
The customer owns witness decisions, procedure approval sign-off,
and final acceptance of test results. The supplier conducts tests,
prepares and executes procedures, controls the test environment, and
maintains the configuration baseline. Some events (system integration,
combined operations) are joint — both parties share responsibility for
planning and execution.
- Readiness conditions are mandatory prerequisites that must each be
confirmed true before a test is authorised to start. The five canonical
conditions are: configuration baseline locked; test procedure approved;
support equipment calibrated and within validity; personnel qualified for
the test; safety clearance granted. A test with any unmet condition is
not authorised — partial satisfaction does not suffice.
- Campaign phases follow a fixed sequence: planning → preparation →
readiness review → execution → reporting → closeout. Phases may be
tailored out (omitted) when formally justified, but the relative order of
retained phases must not be changed.
Workflow
- Inventory every test event in the campaign and record its test type
(acceptance, unit, subsystem, environmental, manufacturing, system,
integration, combined operations, or qualification witness). Reject any
event whose type is not on the recognised list before it enters the
responsibility assignment step.
- For each event, apply the responsibility rule: acceptance and
qualification-witness tests are customer-led; unit, subsystem,
environmental, and manufacturing tests are supplier-led; system,
integration, and combined-operations tests are joint. Record the
assigned role and flag any event where the assignment could not be made
automatically (unknown type or contested override).
- Before each test, evaluate all five mandatory readiness conditions.
Collect which conditions are confirmed and which remain unmet. A single
unmet condition blocks authorisation. Record unknown or ad-hoc condition
labels as warnings — they do not satisfy the canonical list.
- Assemble the campaign phase sequence and validate it against the
canonical order. Flag out-of-order phases, unknown phase names, and
duplicates; do not proceed to execution review if the sequence is invalid.
- Build the campaign plan: aggregate responsibility assignments and
readiness status across all events. The campaign is ready to enter
execution only when every event carries a valid responsibility assignment
and all readiness conditions are met for each event.
Pitfalls
- Treating partial readiness as sufficient — all five conditions must be
confirmed; an event that satisfies four of five is not authorised.
- Allowing an unrecognised test type to pass through without an explicit
responsibility decision — unknown types must be resolved or rejected before
the campaign plan is finalised.
- Reordering campaign phases to work around scheduling pressure — the
readiness review must precede execution; bypassing it invalidates the
authorisation chain.
- Conflating the customer witness role with joint responsibility — a customer
witness test is customer-led (supplier conducts, customer witnesses and
accepts); that is not the same as a joint event where both parties share
planning and execution responsibility.
Behavior contract (gate 3)
The responsibility-assignment, readiness-condition, phase-sequencing, and
campaign-plan logic is exercised by the gate 3 contract test:
scripts/test_e1003_management.py against scripts/e1003_management_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e1003_management.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1003-management3description: "Use when manage a system-level test campaign under ECSS-E-ST-10C §4.3.1: assign customer and supplier responsibilities to each test event, verify that all mandatory readiness conditions (configuration baseline locked, procedure approved, support-equipment calibrated, personnel qualified, safety clearance granted) are satisfied before authorising a test, sequence campaign phases from planning through closeout, and flag any responsibility gap or unmet readiness prerequisite before the test-readiness review is held. Trigger: ecss, e-st-10-system-scope, test-management, test-campaign, readiness-review, customer-supplier, test-responsibility, test-readiness."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/e1003-management15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, test-management, test-campaign, readiness-review, customer-supplier, test-responsibility]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Testing — Test Campaign Management (space-systems/ecss/e1003-management)2324Use when the task is to organise a system-level test campaign per25ECSS-E-ST-10C §4.3.1 — assigning responsibilities between customer and26supplier, verifying test readiness before a run is authorised, and27sequencing campaign phases in the required order.2829## Domain quick reference3031- §4.3.1 partitions test-campaign responsibilities into two roles.32 The **customer** owns witness decisions, procedure approval sign-off,33 and final acceptance of test results. The **supplier** conducts tests,34 prepares and executes procedures, controls the test environment, and35 maintains the configuration baseline. Some events (system integration,36 combined operations) are joint — both parties share responsibility for37 planning and execution.38- Readiness conditions are mandatory prerequisites that must each be39 confirmed true before a test is authorised to start. The five canonical40 conditions are: configuration baseline locked; test procedure approved;41 support equipment calibrated and within validity; personnel qualified for42 the test; safety clearance granted. A test with any unmet condition is43 not authorised — partial satisfaction does not suffice.44- Campaign phases follow a fixed sequence: planning → preparation →45 readiness review → execution → reporting → closeout. Phases may be46 tailored out (omitted) when formally justified, but the relative order of47 retained phases must not be changed.4849## Workflow50511. Inventory every test event in the campaign and record its test type52 (acceptance, unit, subsystem, environmental, manufacturing, system,53 integration, combined operations, or qualification witness). Reject any54 event whose type is not on the recognised list before it enters the55 responsibility assignment step.562. For each event, apply the responsibility rule: acceptance and57 qualification-witness tests are customer-led; unit, subsystem,58 environmental, and manufacturing tests are supplier-led; system,59 integration, and combined-operations tests are joint. Record the60 assigned role and flag any event where the assignment could not be made61 automatically (unknown type or contested override).623. Before each test, evaluate all five mandatory readiness conditions.63 Collect which conditions are confirmed and which remain unmet. A single64 unmet condition blocks authorisation. Record unknown or ad-hoc condition65 labels as warnings — they do not satisfy the canonical list.664. Assemble the campaign phase sequence and validate it against the67 canonical order. Flag out-of-order phases, unknown phase names, and68 duplicates; do not proceed to execution review if the sequence is invalid.695. Build the campaign plan: aggregate responsibility assignments and70 readiness status across all events. The campaign is ready to enter71 execution only when every event carries a valid responsibility assignment72 and all readiness conditions are met for each event.7374## Pitfalls7576- Treating partial readiness as sufficient — all five conditions must be77 confirmed; an event that satisfies four of five is not authorised.78- Allowing an unrecognised test type to pass through without an explicit79 responsibility decision — unknown types must be resolved or rejected before80 the campaign plan is finalised.81- Reordering campaign phases to work around scheduling pressure — the82 readiness review must precede execution; bypassing it invalidates the83 authorisation chain.84- Conflating the customer witness role with joint responsibility — a customer85 witness test is customer-led (supplier conducts, customer witnesses and86 accepts); that is not the same as a joint event where both parties share87 planning and execution responsibility.8889## Behavior contract (gate 3)9091The responsibility-assignment, readiness-condition, phase-sequencing, and92campaign-plan logic is exercised by the gate 3 contract test:93scripts/test_e1003_management.py against scripts/e1003_management_logic.py94(stdlib unittest, offline). Run:9596 python3 scripts/test_e1003_management.py9798## Compliance99100- ECSS standards are freely downloadable (ESA); cite the source and101 paraphrase per standards-map.yaml.102- compliance: STANDARDS-REF, gated: false.