Jump to: navigation, search

Difference between revisions of "StarlingX/Test"

(Sanity Information)
 
(57 intermediate revisions by 7 users not shown)
Line 2: Line 2:
  
 
=== Team Information ===
 
=== Team Information ===
* Project Lead: '''Ada Cabrales''' <ada.cabrales@intel.com>
+
* Project Lead: Rob Cooke
* Technical Lead: '''Jose Perez''' <jose.perez.carranza@intel.com>
+
* Technical Lead: Rob Cooke
* Quality Assurance Engineer:  '''Elio Martinez''' <elio.martinez.monroy@intel.com>
 
* Contributors:
 
  
 
=== Team Objective / Priorities ===
 
=== Team Objective / Priorities ===
* Responsible for verification of StarlingX, including automated and manual testing
+
* Verification and validation of StarlingX system - take a look at the [[StarlingX/TestStrategy|test strategy]]
 +
* Consolidate an automated test suite using an unified Framework
 +
* Reduce to 0 the amount of manual testing
 +
 
 +
=== Documentation ===
 +
* [[StarlingX/TestStrategy|Test strategy]]
 +
* [[StarlingX/TestCaseDocument|Documenting a test]]
  
 
=== Project calls ===
 
=== Project calls ===
Line 39: Line 43:
 
*** [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.test+stx.2018.10&field.tags_combinator=ALL stx.2018.10 Open Bugs]
 
*** [https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.test+stx.2018.10&field.tags_combinator=ALL stx.2018.10 Open Bugs]
  
===Latest ISO image Sanity Summary===
+
=== Sanity Information ===
*ISO: stx-2018-09-02-100.iso
+
'''Overview'''
*ISO: stx-2018-09-03-101.iso
+
*2 configurations are run on Baremetal:
*ISO: stx-2018-09-04-102.iso
+
**AIO-SX (Simplex)
*ISO: stx-2018-09-05-103.iso
+
**AIO-DX (Duplex)
*ISO: stx-2018-09-06-104.iso
 
*ISO: stx-2018-09-07-106.iso
 
*ISO: stx-2018-09-08-107.iso
 
*ISO: stx-2018-09-09-108.iso
 
*ISO: stx-2018-09-10-110.iso
 
*ISO: stx-2018-09-11-111.iso
 
*ISO: stx-2018-09-12-112.iso
 
*ISO: stx-2018-09-13-113.iso
 
*ISO: stx-2018-09-13-114.iso
 
*ISO: stx-2018-09-15-115.iso
 
*ISO: stx-2018-09-16-116.iso
 
*ISO: stx-2018-09-17-117.iso
 
*ISO: stx-2018-09-18-120.iso
 
*ISO: stx-2018-09-19-121.iso
 
  
*Installation [PASS]: 4 TCs Passed, 0 TCs Failed.
+
*Execution is run on Wind River provided labs and hardware
*Provisioning [FAIL]: 2 TCs Passed, 4 TCs Failed.
+
*Execution with Pytest Framework developed by Wind River.
** After configured storage and added LVM storage backend to Controller-0, the Controller-0 stays in "Config out-of-date" state and storage backend stays in "configuring" state.
+
*Execution split in Sanity Platform and Sanity OpenStack
** Controller-0 cannot be unlocked since: "Lvm is configuring. All storage backends must be configured before operation is allowed."
+
------------------------------------------------
** Based on Wind River feedback, test framework was modified to wait for 30 min and for 60 min since state will change to "configured" eventually,  but controller and storage states never change and it cause tests fails.
+
'''Tests Cycle'''
** Issue in Launchpad will be open.
 
*Sanity [FAIL]: 9 TCs Paseed, 11 TCs Failed.
 
*Total: 29 TCs Executed, 15 TCs Passed, 15 TCs Failed.
 
*More details regarding results, please contact elio.martinez.monroy@intel.com and juan.carlos.alonso@intel.com
 
  
**Full logs and reports will be uploaded soon
+
* Sanity for both Platform and Openstack are run once per week
*Related bugs:
+
* Sanities are executed on Baremetal h/w provided by Wind River
** https://bugs.launchpad.net/starlingx/+bug/1790213 (Fixed)
+
* Executed for AIO-SX and AIO-DX configurations
** https://bugs.launchpad.net/starlingx/+bug/1790514
+
* Results are shared by email to the community distribution list
** https://bugs.launchpad.net/starlingx/+bug/1790716 (Fixed)
+
*
** https://bugs.launchpad.net/starlingx/+bug/1790718 (Fixed)
+
* Regression is executed near the end of the release test cycle once all content is in the release
 +
* Automated regression typically includes two executions
 +
* Automated Regression is run within the same framework as the weekly Sanity for Platform
 +
* Executed for AIO-SX and AIO-DX
 +
* Report is generated and shared with the community via email
 +
------------------------------------------------
 +
'''Frameworks'''
 +
*Robot Framework: 61 TCs - dormant was maintained by Intel who have ceased providing this support
 +
*PyTest Framework: 70 TCs
 +
* [[StarlingX/Test/SanityTests|Sanity Tests]]
 +
------------------------------------------------
 +
'''Launchpads'''
 +
* N/A
 +
------------------------------------------------
 +
'''Notes'''
 +
* No participation outside of Wind River on test activities
 +
* Intel used to assist with Sanity and Regression - but this is no longer the case
 +
* Intel used to maintain the test repo - again no longer the case

Latest revision as of 20:49, 12 September 2023

StarlingX Test Sub-project

Team Information

  • Project Lead: Rob Cooke
  • Technical Lead: Rob Cooke

Team Objective / Priorities

  • Verification and validation of StarlingX system - take a look at the test strategy
  • Consolidate an automated test suite using an unified Framework
  • Reduce to 0 the amount of manual testing

Documentation

Project calls

Bi-weekly meetings on Tuesdays at 9:00am PDT / 1600 UTC

Agenda and meeting minutes are in this etherpad

Story Board Tags

All story board stories created for this team should use the tag "stx.test" and the prefix [Test]

Team Work Items

Sanity Information

Overview

  • 2 configurations are run on Baremetal:
    • AIO-SX (Simplex)
    • AIO-DX (Duplex)
  • Execution is run on Wind River provided labs and hardware
  • Execution with Pytest Framework developed by Wind River.
  • Execution split in Sanity Platform and Sanity OpenStack

Tests Cycle

  • Sanity for both Platform and Openstack are run once per week
  • Sanities are executed on Baremetal h/w provided by Wind River
  • Executed for AIO-SX and AIO-DX configurations
  • Results are shared by email to the community distribution list
  • Regression is executed near the end of the release test cycle once all content is in the release
  • Automated regression typically includes two executions
  • Automated Regression is run within the same framework as the weekly Sanity for Platform
  • Executed for AIO-SX and AIO-DX
  • Report is generated and shared with the community via email

Frameworks

  • Robot Framework: 61 TCs - dormant was maintained by Intel who have ceased providing this support
  • PyTest Framework: 70 TCs
  • Sanity Tests

Launchpads

  • N/A

Notes

  • No participation outside of Wind River on test activities
  • Intel used to assist with Sanity and Regression - but this is no longer the case
  • Intel used to maintain the test repo - again no longer the case