This looks basically fine. I've added some comments to the PR, but they boil down to two issues I think:
- For everything that's broken (ie, that should've worked but didn't), we should have a JIRA ticket linked in the test report. These will be the Software Problem Reports assessed by the CCB. If we can convince the CCB that they are "noncritical" (e.g. because they are within reasonable tolerances) then we can claim the test as having been passed.
- Most of our failures are due to things which haven't been implemented, and in some cases things for which the requirements haven't even yet been properly established. Rather than writing these up as failures, my suggestion would be to document them as "deviations from test procedure". That means we are properly reporting on the success (or otherwise) of code which actually exists now, but maintaining those parts of the test cases so that they will be executed when we come to re-run the tests with a more mature stack in future.