Just tugging your chain.
I did enough s/w testing in my days to know, ya can't test for everything.
I would routinely put "out of range" values into input fields or do something "not expected or allowed" because people WILL do that using the s/w. That alone found a plethora of errors that were not caught on condition. I would look at all the "IF" statements to see if I could screw some up with out of bounds parameters. This would often crash the system.
Since I was working on various banking and before that some military systems my methods were encouraged, but the programmers sorta did not appreciate me. boo hoo.
When I was working at SPAR where we made the robotic arm for the space shuttle (Canadarm) I was a senior member of the project management team. During down time, I would play with the 3D simulator capturing satellites and putting them in orbit or back into the shuttle bay. I got fairly good at this too. It ain't easy by any stretch.
This simulator was built around the old IMSAI 8080 because the systems architecture was based on the computers in the shuttle. The 4 video displays used some radar processors and produced a vector line diagram on the 4 screens that mimicked the 4 windows on the aft shuttle cabin, much like the old ATARI Tank game. Very realistic video game. This setup was used primarily for engineering test and development. NASA had a similar system in Houston which was more realistic to the shuttles interior for training.
Anyway, one day I decided to do an end to end scenario, take the arm out of locks, take a sat out of the bay, put it in orbit, then park the arm for departure.
Well, lo and behold, I could NOT park the arm without setting off singularity alarms in the last inch or so. A singularity is the term used to warn of joint limitations.
It would auto-park, but not manually. NOBODY ever tried this before. The chief engineer tore a strip off me, but never checked. A week later we got a call from NASA with a problem..... Yep, couldn't manually park.
It is not good when the client finds a problem that you didn't. Took about 3 days to fix and validate the problem in the code. The program manager gave me an "attaboy"; the chief eng. never said a word about it.


