Not funny anymore
- Feb 6, 2008
- Reaction score
Could you elaborate a bit on what you mean by this?
Like, since the checklists essentially formulate already from the "user perspective", what the spacecraft should do, run an automated test process over the add-on by executing a checklist and comparing the results to the quantities that should be noted or observed according to this checklist.
This is a different perspective as unit tests, which test individual units of code or subsystems.
For example, when you change something in NASSP, without correcting the checklists, you would find it by the test failing. If you run a new mission, the test should fail, if the checklists have assumptions that are not according to the mission conditions.
It would not be a fast test, that you could run in a build pipeline, but you could run multiple such tests over a weekend, if each test just covers maybe a sequence of maximal one hour flight. And since it is automated, it would complain ever for minor issues that are wrong with the test, instead of being wrong with the add-on. And much more great: The test artifacts are also release artifacts, since you need correct checklists as well there.