Jump to: navigation, search

StarlingX/Test

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