Test Plans:

Automated Functional and Non-Functional tests including performance and fault tests. 

The functional tests mainly cover the following types of testing:

• Sanity testing – to verify build sanity
• Smoke testing – to make sure that the service operates at a very basic level and it makes sense to move forward
• Regression testing – main part of testing verifying all possible previously found regressions
• Usability testing – verifies ease of use, the ability to achieve supported use cases

Within the engineering teams, QE engineers also lead the development of non-functional tests, including:

• Load and Performance Tests
• Stress and Capacity Tests
• Soak Tests
• Fault and Chaos Tests
• Full Product E2E Tests
• Automated Quickstart Tests
• Service and OSD Upgrade Tests
• Interoperability Tests
• Integration Tests
• Security Tests
• Certifications

Please note: the tests listed above are not a hard requirement for each one of them, it's up to the program team to prioritize and determine the test plan and integration use cases, or when/what to prioritize for different release milestones (service preview, or GA).

See more about QE roles and test types for cloud services: 

• Document
• Slide Deck
• Recording

Best Practice

The following JIRAs should be reviewed and associated JIRAs created for the Managed Service with tracker and guidance for QE:

• https://issues.redhat.com/browse/PLMPGM-1918

Primary Area: Quality Engineering, Engineering

Contacts:

• Main Contact: Quality Engineering (if you don't have a QE or don't know where to ask, contact Michael Harvey <mharvey@redhat.com>)
• Performance&Scalability: Pradeep Surisetty
• Interoperability Testing: Anoop Nair and Paige Vauter (this is also called out as a separate task in ROMS, please track the activities here - PLMPGM-1672)  

Official Deliverable: Test plans and Jira tracked under 

• https://issues.redhat.com/browse/PLMPGM-1918

Definition of Done: Test Plans created and executed, test results shared with related teams gating quality, reliability and stability requirements.

Recommended for internal services, required for customer-facing services