Bottlenecks Milestone E report
1. Has your test framework been executed against a deployed OPNFV platform?
Yes. Successfully tested on Fuel. Would be tested on Compass in the coming weeks.
2. Has your deploy tool been executed in more than one Pharos lab?
No. Have only tested on LF Pod. Soon will be testing on Huawei lab in Santa Clara.
3. Have your test framework and test cases been run against more than one deployment tool?
No. Have only tested on Fuel. But running against Compass will be in the coming weeks.
4. Do you have all target Brahmaputra test cases available in your test suites?
Yes. The test cases for B release has already available.
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?
still open. The documentation about the test suites will be integrated into the release.
7. Are all known issues (Jira Tickets) prioritized by severity of impact (critical, high, medium, low) to users?
The prioritization of Jira tickets will be discussed in the latest weekly meeting.
8. Do all known critical Jira Tickets have a workaround in place?
yes
9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)?
Most of the critical Jira tickets have already resolved. The priority of Jira about testing on Compass will be raised.
10. Is your documentation complete and checked in? If not, how do you plan to deliver it independent of the release?
Documentation is initialed and would be finished in 2~3 weeks.
