Some folks have been criticizing the recent Orion parachute test failure as just one more screwup at NASA that they’ve been covering up, and made a bigger deal of it than it is, but Henry Spencer has a more nuanced, and correct view:
Foul-ups in testing are not uncommon, especially when the test setup is being tried for the first time. One of the headaches of high-tech test programmes is having to debug the test arrangements before you can start debugging the things you’re trying to test.
Sometimes a malfunctioning test setup actually gives the tested system a chance to show what it can do in an unrehearsed emergency. During a test of an Apollo escape-system in the 1960s, the escape system successfully got the capsule clear of a malfunctioning test rocket.
But sometimes the test conditions are so unrealistically severe that there’s no hope of correct functioning. Unpleasant though the result often looks, this isn’t properly considered a failure of the tested system. That seems to have been what happened here.
As I’ve noted before, requirements verification is where the real cost of a development program comes from, particularly when the only useful verification method is test.