Re: So let me see if I understand...
This was a verification of years of simulation and modelling that was supposed to prove the design before any construction even started. A sensor reading out of range shows there is an important detail missing from the model that makes the simulation invalid.
This is what bothers me. When I'm testing software I never worry about the things I know to test. I build my test cases and expect everything to pass. I don't make excuses why something 'almost worked'. If it's test parameters then you fix them just like a defect. What worries me is there are ALWAYS things that could fail that you don't know about. You either find them and fix them during testing, or it bites you in the ass in the real world.
Boeing isn't going to build a dozen test vehicles and 'fail early' like SpaceX does. With their recent track record, saying "no worries, it's just a bad test parameter" isn't good enough. It was just a 'bad test parameter' on a clock that caused their launch problem on their test capsule.