Yardstick Milestone E report
1. Has your test framework been executed against a deployed OPNFV platform?
Yes, executed against fuel and compass.
2. Has your deploy tool been executed in more than one Pharos lab?
Yes.
3. Have your test framework and test cases been run against more than one deployment tool?
Yes.
4. Do you have all target Brahmaputra test cases available in your test suites?
No, good progress on generic (Yardstick owned NFVI) test cases, missing to complete/develop feature test cases.
5. Is your test framework able to be repeated on the same infrastructure at least 4 consecutive times without failures? Does it meet the agreed upon criteria of "stable"?
Yes, but not for all installers/target PODs.
6. Have all known test issues (Jira tickets against your project) been documented and that documentation either integrated into the release or made available on a public page and pointed to through documents that are integrated into the release?
Up to this date documented in Jira.
7. Are all known issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?
No critical faults at the moment; remaining work is prioritized.
8. Do all known critical Jira Tickets have a workaround in place?
No critical faults found at the moment, testing on target PODs still remains to be done. Hard to define workaround for faults that have not yet occured.
9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?
Not all.
10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?
Documentation initiated, not completed.
