[Starlingx-discuss] Regression test cases for networking testing
Hello guys, I'm sharing the list of regression test cases for networking, please let me know if you consider that we need to add some other scenario. This test is based on a full analysis of different domains. Besides this, we are trying to perform a good scope coverage , wiping out those domains and features that StarlingX is not using such as AVS and go on. Please let me know if you have further questions or suggestions. We are in the process of adjusting some test cases according with new features and convention names such as Provider net. So, this list can be adjusted and may change in future days. [cid:image001.png@01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer.
Hi Chris, Can you please also review these test cases. Thanks, Numan. From: Martinez Monroy, Elio <elio.martinez.monroy@intel.com> Sent: February-22-19 1:59 PM To: Xu, Chenjie <chenjie.xu@intel.com>; starlingx-discuss@lists.starlingx.io Cc: Cabrales, Ada <ada.cabrales@intel.com>; Khalil, Ghada <Ghada.Khalil@windriver.com>; Waheed, Numan <Numan.Waheed@windriver.com>; Zhao, Forrest <forrest.zhao@intel.com> Subject: Regression test cases for networking testing Hello guys, I'm sharing the list of regression test cases for networking, please let me know if you consider that we need to add some other scenario. This test is based on a full analysis of different domains. Besides this, we are trying to perform a good scope coverage , wiping out those domains and features that StarlingX is not using such as AVS and go on. Please let me know if you have further questions or suggestions. We are in the process of adjusting some test cases according with new features and convention names such as Provider net. So, this list can be adjusted and may change in future days. [cid:image001.png@01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer.
Hi All Here is my feedback - respective to the row numbers in the "Regression tests Networking .xlsx" spreadsheet: Row 5-6: Remove TC: no vif model in stx Row 20-27: Remove the testcase: feature is depricated Row 41-42: Remove the testcase: n/a in STX Row 64: Correct the TC name: “i raised” to “is raised” Row: 68: Remove TC: not applicable Row 71: Remove TC: not applicable Row 72: Remove TC: not applicable Row 75: Remove TC: not applicable Row 81: Remove TC: not applicable Row 81: Remove TC: not applicable due to https://storyboard.openstack.org/#!/story/2004455 Row 82: Change priority to: 4 Row 86, 101, 102-106: Remove TC: No infra network in STX Row 109-111: Low value Row: 112-116: Change priority to: 3 Row 117, 119: N/A in STX Row: 133: VM misspeled with “vem” Row 137-138: Change priority to: 3 Row 139: Remove TC: No infra network in STX Row 140-143: Change priority to: 4 Row 146: Remove TC: No infra network in STX Row 148: Remove TC: No infra network in STX Row 149-151: Remove TC: No infra network in STX Chris Winnicki - MTS - SYS - PV chris.winnicki@windriver.com 613-963-1329 ________________________________ From: Waheed, Numan Sent: Friday, February 22, 2019 2:17 PM To: Martinez Monroy, Elio; Xu, Chenjie; starlingx-discuss@lists.starlingx.io; Winnicki, Chris Cc: Cabrales, Ada; Khalil, Ghada; Zhao, Forrest Subject: RE: Regression test cases for networking testing Hi Chris, Can you please also review these test cases. Thanks, Numan. From: Martinez Monroy, Elio <elio.martinez.monroy@intel.com> Sent: February-22-19 1:59 PM To: Xu, Chenjie <chenjie.xu@intel.com>; starlingx-discuss@lists.starlingx.io Cc: Cabrales, Ada <ada.cabrales@intel.com>; Khalil, Ghada <Ghada.Khalil@windriver.com>; Waheed, Numan <Numan.Waheed@windriver.com>; Zhao, Forrest <forrest.zhao@intel.com> Subject: Regression test cases for networking testing Hello guys, I’m sharing the list of regression test cases for networking, please let me know if you consider that we need to add some other scenario. This test is based on a full analysis of different domains. Besides this, we are trying to perform a good scope coverage , wiping out those domains and features that StarlingX is not using such as AVS and go on. Please let me know if you have further questions or suggestions. We are in the process of adjusting some test cases according with new features and convention names such as Provider net. So, this list can be adjusted and may change in future days. [cid:image001.png@01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer.
Thanks for your feedback Chris, In total we are going to keep 117 test cases with different priority, will take a look into the other ones and will work in the others 33. BR Elio From: Winnicki, Chris [mailto:Chris.Winnicki@windriver.com] Sent: Monday, February 25, 2019 4:03 PM To: Waheed, Numan <Numan.Waheed@windriver.com>; Martinez Monroy, Elio <elio.martinez.monroy@intel.com>; Xu, Chenjie <chenjie.xu@intel.com>; starlingx-discuss@lists.starlingx.io Cc: Cabrales, Ada <ada.cabrales@intel.com>; Khalil, Ghada <Ghada.Khalil@windriver.com>; Zhao, Forrest <forrest.zhao@intel.com> Subject: RE: Regression test cases for networking testing Hi All Here is my feedback - respective to the row numbers in the "Regression tests Networking .xlsx" spreadsheet: Row 5-6: Remove TC: no vif model in stx Row 20-27: Remove the testcase: feature is depricated Row 41-42: Remove the testcase: n/a in STX Row 64: Correct the TC name: "i raised" to "is raised" Row: 68: Remove TC: not applicable Row 71: Remove TC: not applicable Row 72: Remove TC: not applicable Row 75: Remove TC: not applicable Row 81: Remove TC: not applicable Row 81: Remove TC: not applicable due to https://storyboard.openstack.org/#!/story/2004455 Row 82: Change priority to: 4 Row 86, 101, 102-106: Remove TC: No infra network in STX Row 109-111: Low value Row: 112-116: Change priority to: 3 Row 117, 119: N/A in STX Row: 133: VM misspeled with "vem" Row 137-138: Change priority to: 3 Row 139: Remove TC: No infra network in STX Row 140-143: Change priority to: 4 Row 146: Remove TC: No infra network in STX Row 148: Remove TC: No infra network in STX Row 149-151: Remove TC: No infra network in STX Chris Winnicki - MTS - SYS - PV chris.winnicki@windriver.com<mailto:chris.winnicki@windriver.com> 613-963-1329 ________________________________ From: Waheed, Numan Sent: Friday, February 22, 2019 2:17 PM To: Martinez Monroy, Elio; Xu, Chenjie; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>; Winnicki, Chris Cc: Cabrales, Ada; Khalil, Ghada; Zhao, Forrest Subject: RE: Regression test cases for networking testing Hi Chris, Can you please also review these test cases. Thanks, Numan. From: Martinez Monroy, Elio <elio.martinez.monroy@intel.com<mailto:elio.martinez.monroy@intel.com>> Sent: February-22-19 1:59 PM To: Xu, Chenjie <chenjie.xu@intel.com<mailto:chenjie.xu@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Cc: Cabrales, Ada <ada.cabrales@intel.com<mailto:ada.cabrales@intel.com>>; Khalil, Ghada <Ghada.Khalil@windriver.com<mailto:Ghada.Khalil@windriver.com>>; Waheed, Numan <Numan.Waheed@windriver.com<mailto:Numan.Waheed@windriver.com>>; Zhao, Forrest <forrest.zhao@intel.com<mailto:forrest.zhao@intel.com>> Subject: Regression test cases for networking testing Hello guys, I'm sharing the list of regression test cases for networking, please let me know if you consider that we need to add some other scenario. This test is based on a full analysis of different domains. Besides this, we are trying to perform a good scope coverage , wiping out those domains and features that StarlingX is not using such as AVS and go on. Please let me know if you have further questions or suggestions. We are in the process of adjusting some test cases according with new features and convention names such as Provider net. So, this list can be adjusted and may change in future days. [cid:image001.png@01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer.
participants (3)
-
Martinez Monroy, Elio
-
Waheed, Numan
-
Winnicki, Chris