< User:Roshi | QA/Cloud Docs
Objective
This document aims to establish what testing is necessary to ensure the milestone releases of the Fedora Cloud product meet the desired levels of quality.
Scope
The Cloud Products Requirements Document - henceforth, "PRD" - defines the high-level aims of the Cloud product. Significant points include:
- The product will be delivered as a self-contained cloud image (AMI, qcow2, raw.xz, etc). This means testing of the product will not require any form of installation testing.
- Aims to support the cattle aspect of the [pets vs cattle] metaphor of computing.
- The product will be used on public and private cloud infrastructures.
- The product will have access to Fedora package collections, this includes: Access to the standard Fedora package repositories, Standard language stacks (like Python, Ruby, NodeJS, PHP), and Modernized language and application-specific stacks, perhaps in the form of SCLs, for running userspace applications .
- The product has a goal of being able to automatically generate and upload images throughout the year. This will require a significant amount of testing and work to develop the needed infrastructure for testing generated images.
- The product aims to increase support for Docker with a custom image.
- Cloud images also need to be able to support traditional server roles, transitioning one of your "cattle" into a pet (while in the cloud).
- Various requirements for the base system are documented in the TS, several of which are likely to be held in common with the other Products and current Fedora, but some of which are specific to Cloud.
Proposed test coverage
It is reasonable to assume that most of our existing Fedora_Release_Criteria, with the exception of those specifically relating to desktop functionality, will be held to apply to the Server product. It is therefore equally reasonable to assume that our existing QA:Installation_validation_testing and QA:Base_validation_testing processes will apply to the Server product, and the corresponding test plans ('test matrices') will need to be run for each milestone release of the Server product.
We will also require additional Server-specific testing to fully validate the product for release. Testing the "server roles" will form the majority of this work. The mechanisms for deploying and configuring server roles both during installation and after installation will need to be tested. All of the "featured" roles for any given release will also need to be tested to ensure they meet the "mandatory requirements" defined in the PRD.
Beyond this, additional "Base validation" type tests are likely to be required to validate all the commitments of the TS which are not currently explicitly tested, e.g. the requirements for remote logging and remote updating, the requirements relating to firewall functionality, and so forth. Some of these tests may be shared with the other products and deliverables.