My tests keep failing until I fix all of my code, then we deploy to production. If code fails in production than that's a problem.
We could say that rockets are not code. A test run of a Spaceship surely cost much more than a test run of any software on my laptop but tests are still tests. They are very likely to fail and there are things to learn from their failures.
Do your tests require tens of millions, and can have potential casualties?
How would you test a rocket?
You’ll catch issues along the way, but you can’t catch all of them before a full launch test. That’s why there are launch tests.
Real tests do all of this at once with no option to escape reality.
Again, one thing is automating thorough software tests, another one is testing physical stuff.
Integration tests are the next where multiple units are combined.
Then there is staging.
Test a rocket by launching it.
Honestly I thought they would be live testing fuel exchange in orbit by now. Seems pretty far from it sadly.
What makes these launches “non-production” tests is that they are not carrying any valuable payload. Blowing up rockets like this is exactly what gives the company it’s advantage over competitors who try to anticipate everything during design stages.
It's true that other rocket companies are treating launches as production, but SpaceX has always been doing "hardware-rich" testing.
It is more like an "all or nothing" process.
They already implemented a whole host of changes to the vehicles after the first test back in 2023. There's a list of corrective actions here.
According to this website their current success rate is 99,18%. That's a good number I guess? Considering other companies did not even land their stages for years.
https://spaceinsider.tech/2024/07/31/ula-vs-spacex/#:~:text=....
There's an order of magnitude difference between them. If they were cars, it'd be like comparing the smallest car you can think of vs one of the biggest tanks ever made.
I'd say that only the 7th mission was legitimately a failure, because there was some rerouting of flights outside the exclusion zone. The other six missions were successful tests since nothing other than the rocket itself was affected.
That would be like comparing a 1-y.o.'s ability to run to a 10-y.o.'s. Of course the younger kid doesn't yet control their legs, but that doesn't mean it's going to stumble and fall forever.
Without Spacex, the typical cohort of gov contractors would have been happy bleeding NASA dry with one time use rockets that have 10x the launch cost and carry 1/4 the cargo.
Isn’t SpaceX the largest launch provider in the world and for the U.S. government?
Many times than the rest of the U.S. space industry combined.
Falcon 9 has had plenty of "ROI" but it wasn't really federally funded. Let's not get carried away though about "more than the entire US space industry combined," though.
But that still means it’s not just taxpayer money, it’s mostly theirs. They’ve been raising equity rounds this whole time.
In my experience in corporate america you communicate efficiency by proclaiming a checklist of things to do - plausible, but not necessarily accurate things - and then let engineers figure it out.
Nobody cares of the original checklist as long as the problem gets resolved. It's weird but it seems very hard to utter statement "I don't have specific answers but we have very capable engineers, I'm sure they will figure it out". It's always better to say (from the top of your head) "To resolve A, we will do X,Y and Z!". Then when A get's resolved, everyone praises the effort. Then when they query what actually was done it's "well we found out in fact what were amiss were I, J K".