This document aims to establish what testing is necessary to ensure the milestone releases of the Fedora Workstation product meet the desired levels of quality.
The Workstation/Workstation_PRD - henceforth, "PRD" - defines the high-level aims of the Workstation product, and the Workstation/Technical_Specification - henceforth, "TS" - provides technical detail on its design. Significant points include:
- The product will be delivered as a local live install media, with USB sticks as the primary target. The image will also be burnable on to DVDs. Persistence is not an important requirement. gnome-disks, liveusb-creator need to be tested to check creation of EFI compatible USB sticks on both Windows and Linux (TS)
- The product will use Anaconda as its deployment mechanism (implicit in the TS)
- The product's default storage configuration will be btrfs. However, until btrfs is deemed mature enough, the product will continue to use the current configuration: ext4 (TS)
- The product will be built on top of the Base WG's output (part of overall Fedora.next plan)
- The PRD/Technical spec does not cover installation methods.
- The product will be based on the GNOME desktop environment. (TS)
- A core package set will be focussed on. This includes but is not limited to gdm, gnome-initial-setup, firefox, gnome-terminal, gnome-boxes, nautilus, developer assistant (TS)
- 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 Workstation.
Proposed test coverage
It is reasonable to assume that most of our existing Fedora_Release_Criteria will be apply to the Workstation product. It is therefore equally reasonable to assume that our existing QA:Installation_validation_testing and QA:Base_validation_testing processes will also apply to the Workstation product, and the corresponding test plans ('test matrices') will need to be run for each milestone release of the Workstation product.
We will also require additional Workstation-specific testing to fully validate the product for release.
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.