1. The battle school

Orson Scott Card’s Ender’s Game puts its protagonist through a series of simulated battles that are deliberately harder than anything he is expected to face. The simulations are supposed to prepare him, but they also deceive him about what is real. The lesson for qualification is double-edged: tests must be rigorous enough to find failure modes, but honest enough that the team understands what has actually been proven.

Entry 279 introduced manufacturing and qualification. This entry looks at the environments where the desktop will be tested.

2. The standard environments

A spacecraft qualification campaign typically includes:

  • Vibration: simulates launch vehicle loads. Includes random vibration on each axis and sometimes sine vibration or quasi-static loads.
  • Shock: simulates pyrotechnic events such as separation from the launch vehicle or deployment of solar arrays.
  • Acoustic: simulates the sound pressure field inside the launch fairing during ascent.
  • Thermal vacuum: simulates the vacuum and temperature extremes of space, including hot and cold soak and thermal cycling.
  • EMC: verifies that the spacecraft does not emit unacceptable interference and is not overly susceptible to external interference.
  • Life testing: verifies that mechanisms, such as robotic joints and deployment hinges, survive their required number of cycles.

Each environment has standards that define test levels, durations, and acceptance criteria.

3. Qualification versus acceptance

There is an important distinction:

  • Qualification testing: performed on a dedicated unit, often to levels more severe than flight, to prove the design.
  • Acceptance testing: performed on the flight unit to prove that the specific unit is free of manufacturing defects.

Qualification answers: “Does the design work?” Acceptance answers: “Was this unit built correctly?”

For the desktop, the first flight unit may also serve as the qualification unit, depending on budget and risk tolerance. Reusing the flight unit for heavy qualification reduces cost but increases risk to the flight article.

4. Test by subsystem

Not every subsystem needs the same treatment:

  • Structure: vibration, acoustic, shock, and thermal vacuum to verify strength and stability.
  • Electronics: thermal vacuum, EMC, and sometimes radiation testing.
  • Mechanisms: life testing, thermal vacuum cycling, and deployment testing.
  • Software: hardware-in-the-loop simulation, fault injection, and long-duration stress tests.
  • Optics and sensors: alignment verification, contamination control, and thermal vacuum performance.

Attachments can often be qualified separately from the platform, then integrated for system-level testing. This is one advantage of the modular grid.

5. Test as failure discovery

The purpose of testing is not to pass. The purpose is to learn. A test campaign that finds no failures is either very lucky or not looking hard enough.

The Resident expects failures during qualification:

  • A connector backs out under vibration.
  • A solder joint cracks during thermal cycling.
  • A software race condition appears during long-duration testing.
  • A mechanism binds after cold soak.

Each failure is an opportunity to fix the design before launch. The cost of finding a failure on the ground is a tiny fraction of the cost of finding it in orbit.

6. Test cost and schedule

Qualification is expensive and time-consuming. A full environmental test campaign can take months and cost a significant fraction of the spacecraft budget. Test facilities are often booked far in advance.

For the desktop, the test schedule must be planned alongside the design. Waiting until the hardware is ready to book a thermal vacuum chamber is a common way to delay a programme.

Cost-saving strategies:

  • Use heritage components that have already been qualified.
  • Perform analysis in place of test where standards allow.
  • Qualify attachments at module level rather than system level.
  • Share test facilities with other small spacecraft programmes.

These strategies reduce cost but must not reduce confidence below the level required for the mission.

7. The test-analyse-fix-test loop

Qualification is iterative. A typical loop:

  1. Design and build the test article.
  2. Perform a test.
  3. Analyse the results.
  4. Fix any failures.
  5. Verify the fix with analysis or retest.

This loop continues until the design is qualified. The loop works best when the team is honest about failures and quick to fix root causes rather than symptoms.

What this changes

  • The desktop’s qualification campaign includes vibration, shock, acoustic, thermal vacuum, EMC, and life testing.
  • Qualification proves the design; acceptance proves the flight unit was built correctly.
  • Subsystems are tested according to their specific environments and failure modes.
  • Tests are treated as opportunities to find failures, not just boxes to check.
  • Test schedule and cost are planned early, not after hardware is ready.
  • The next entry will cover assembly strategy and cleanroom practice.