Jump to: navigation, search

Difference between revisions of "StarlingX/Test"

(Sanity Information)
 
(8 intermediate revisions by 3 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
* PyTest Developer Lead: '''Yang Liu''' <yang.liu@windriver.com>
 
* Team members:
 
**  '''Cristopher Lemus''' <cristopher.j.lemus.contreras@intel.com>
 
**  '''Elio Martinez''' <elio.martinez.monroy@intel.com>
 
** '''Fernando Hernandez''' <fernando.hernandez.gonzalez@intel.com>
 
** '''Juan Carlos Alonso''' <juan.carlos.alonso@intel.com>
 
** '''Juan Pablo Gomez''' <juan.p.gomez@intel.com>
 
**  '''Maria Perez''' <maria.g.perez.ibarra@intel.com>
 
**  '''Numan Waheed''' <Numan.Waheed@windriver.com>
 
**  '''Ricardo Perez''' <ricardo.o.perez@intel.com>
 
  
 
=== Team Objective / Priorities ===
 
=== Team Objective / Priorities ===
Line 23: Line 13:
 
* [[StarlingX/TestStrategy|Test strategy]]
 
* [[StarlingX/TestStrategy|Test strategy]]
 
* [[StarlingX/TestCaseDocument|Documenting a test]]
 
* [[StarlingX/TestCaseDocument|Documenting a test]]
* [[StarlingX/Test/SanityTests|Sanity Tests]]
 
  
 
=== Project calls ===
 
=== Project calls ===
Line 56: Line 45:
 
=== Sanity Information ===
 
=== Sanity Information ===
 
'''Overview'''
 
'''Overview'''
*4 configurations are run:
+
*2 configurations are run on Baremetal:
 
**AIO-SX (Simplex)
 
**AIO-SX (Simplex)
 
**AIO-DX (Duplex)
 
**AIO-DX (Duplex)
**Standard Local Storage (2+2)
+
 
**Standard External Storage (2+2+2)
+
*Execution is run on Wind River provided labs and hardware
* 2 environments are run:
+
*Execution with Pytest Framework developed by Wind River.
**Baremetal
 
**Virtual
 
*Execution is run with no proxy settings, with proxy settings and with local registry.
 
*Execution is run in a variety of hardware
 
*Execution with Robot Framework developed by Intel and PyTest Framework developed by WR.
 
 
*Execution split in Sanity Platform and Sanity OpenStack
 
*Execution split in Sanity Platform and Sanity OpenStack
 
------------------------------------------------
 
------------------------------------------------
 
'''Tests Cycle'''
 
'''Tests Cycle'''
* Each site, Intel and WR, runs two configuration for two weeks, then switch.
+
 
*Baremetal Environment will be executed by Intel and WR
+
* Sanity for both Platform and Openstack are run once per week
*Virtual Environment will be executed by Intel only
+
* Sanities are executed on Baremetal h/w provided by Wind River
*Execution of Sanity will be run with PyTest Framework that is already in the public repo.
+
* Executed for AIO-SX and AIO-DX configurations
*Execution during Week 1 & 2:
+
* Results are shared by email to the community distribution list
**Intel:
+
*
***AIO-SX
+
* Regression is executed near the end of the release test cycle once all content is in the release
***Standard External Storage (2+2+2)
+
* Automated regression typically includes two executions
**WR:
+
* Automated Regression is run within the same framework as the weekly Sanity for Platform
***AIO-DX
+
* Executed for AIO-SX and AIO-DX
***Standard Local Storage (2+2)
+
* Report is generated and shared with the community via email
*Execution during Week 3 & 4:
 
**Intel:
 
***AIO-DX
 
***Standard Local Storage (2+2)
 
**WR:
 
***AIO-SX
 
***Standard External Storage (2+2+2)
 
 
------------------------------------------------
 
------------------------------------------------
 
'''Frameworks'''
 
'''Frameworks'''
*Robot Framework: 61 TCs
+
*Robot Framework: 61 TCs - dormant was maintained by Intel who have ceased providing this support
 
*PyTest Framework: 70 TCs
 
*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