-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
False
-
False
-
Undefined
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:
- Performance (Load, Stress and Capacity, Soak Tests)
- Fault and Chaos Tests
- Full Product E2E and Quickstart Tests
- Service and OSD Upgrade Tests
- Integration Tests
See more about QE roles and test types for cloud services:
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)
- Chaos and Fault Testing - Naga Ravi Chaitanya Elluri (Chaos Engineering Team)
Official Deliverable: Test plans and Jira tracked under the above three SAASQE epics.
Definition of Done: Test Plans created and executed, test results shared with related teams gating quality, reliability and stability requirements.
