releases:brahmaputra:release_plan:functest_milestone_e_report
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
releases:brahmaputra:release_plan:functest_milestone_e_report [2016/01/04 17:05] Morgan Richomme |
releases:brahmaputra:release_plan:functest_milestone_e_report [2016/01/07 14:28] (current) Jose Lausuch |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| 2. Has your deploy tool been executed in more than one Pharos lab? | 2. Has your deploy tool been executed in more than one Pharos lab? | ||
| - | yes | + | * yes |
| 3. Have your test framework and test cases been run against more than one deployment tool? | 3. Have your test framework and test cases been run against more than one deployment tool? | ||
| - | yes | + | * yes |
| 4. Do you have all target Brahmaputra test cases available in your test suites? | 4. Do you have all target Brahmaputra test cases available in your test suites? | ||
| - | no (internal testcase OK with doubt on capability to extend odl suite), onos and opencontrail test suites not tested yet (no target solution available), no news from other feature tests | + | * no (internal testcase OK with doubt on capability to extend odl suite), onos and opencontrail test suites not tested yet (no target solution available), no news from other feature tests |
| 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"? | 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"? | ||
| - | * achieved only once on fuel/no controller (with is not the target) | + | * achieved only once on fuel/no controller (wich is not the target) |
| * no on all the other targets | * no on all the other targets | ||
| Line 40: | Line 40: | ||
| 8. Do all known critical Jira Tickets have a workaround in place? | 8. Do all known critical Jira Tickets have a workaround in place? | ||
| - | * not really if no target lab, no test..I do no see any possible workaround for that | + | * not really if no target lab, no test..I do not see any possible workaround for that |
| 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)? | 9. Do all non-critical Jira Tickets have a planned disposition in place (ie. deferred-fix in later release or closed- won't fix)? | ||
releases/brahmaputra/release_plan/functest_milestone_e_report.1451927124.txt.gz ยท Last modified: 2016/01/04 17:05 by Morgan Richomme
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
