VSPerf Milestone E report
1. Has your test framework been executed against a deployed OPNFV platform?
N/A ATM we are a standalone test utility running in Intel POD 3
2. Has your deploy tool been executed in more than one Pharos lab?
We have integrated with Fuel and run in the Montreal Lab.
3. Have your test framework and test cases been run against more than one deployment tool?
No.
4. Do you have all target Brahmaputra test cases available in your test suites?
Yes.
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.
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?
Yes all known issues are documented.
7. Are all known issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?
No.
8. Do all known critical Jira Tickets have a workaround in place?
N/A. All critical Jira Tickets for Release B are complete. Only the documentation remains open for final review.
9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?
N/A. All non-critical Jira Tickets for Release B are complete. Only the documentation remains open for final review.
10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?
One final patch is outstanding
