https://x.com/deankolson87/status/1880026759133032662?t=HdHF...
https://x.com/realcamtem/status/1880026604472266800
https://x.com/adavenport354/status/1880026262254809115
Moment of the breakup:
https://x.com/deankolson87/status/1880026759133032662?t=HdHF...
https://x.com/realcamtem/status/1880026604472266800
https://x.com/adavenport354/status/1880026262254809115
Moment of the breakup:
Apart from obviously double-checking for leaks, we will add fire suppression to that volume and probably increase vent area. Nothing so far suggests pushing next launch past next month.
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.
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.