|
|
| (10 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| __NOTOC__
| | #REDIRECT [[QA:Release_validation_test_plan]] |
| {{header|qa}}
| |
| | |
| == Introduction ==
| |
| | |
| Before an official Fedora release comes out, several alpha, beta and release candidate releases - known collectively as pre-releases - are made available. As part of the validation process for each pre-release, the QA group tests to see that various typical desktop functions meet pre-defined quality standards. You can find the requirements for each release in the [[Fedora_Release_Criteria]].
| |
| | |
| == Scope and Approach ==
| |
| | |
| Testing will include:
| |
| | |
| * Manually executed test cases using DVD, CD-ROM, or live image media
| |
| | |
| == Timing of installation test events ==
| |
| | |
| Installation test events occur before milestone releases. Current events can be found at:
| |
| | |
| * http://poelstra.fedorapeople.org/schedules/f-{{FedoraVersion||next}}/f-{{FedoraVersion||next}}-quality-tasks.html
| |
| | |
| == Test plan ==
| |
| | |
| A [[:Category:Desktop_Acceptance_Test_Cases|set of test cases]] forms the basis of desktop validation testing. These test cases are designed to ensure that the release under testing complies with the [[Fedora_Release_Criteria]]: the test cases derive from the criteria, not the other way around. As and when the criteria are adjusted or updated, new test cases should be created and no longer valid ones removed as appropriate.
| |
| | |
| For each candidate, pre-release, and release build to be tested, the entire set of desktop validation test cases should be run. Tests can be performed by any QA group member, and multiple test runs are acceptable and encouraged. Each test case is associated with a particular release stage (Alpha, Beta or Final), depending on which set of release criteria the criterion it is intended to validate forms a part of. Even though all tests are run at each stage, only those associated with the current stage or an earlier stage will be considered as blocking the release. That is, if an Alpha test fails at Final stage, the failure blocks the final release; but if a Final test fails at Alpha stage, the Alpha release is not blocked.
| |
| | |
| Any failure of any test must be reported using the appropriate tracking system - usually [http://bugzilla.redhat.com Bugzilla].
| |
| | |
| === Test environment ===
| |
| | |
| Testing can be performed using the pre-release or release images, or candidate images for pre-releases or releases as provided to the QA group by the Release Engineering group. Testing must be performed on the [[Architectures#Primary_Architectures|primary architectures]].
| |
| | |
| == Results ==
| |
| | |
| Results are recorded in a separate page for each testing run. The results for the upcoming {{FedoraVersion|long|next}} release can be found [[:Category:{{FedoraVersion|long|next}}_Test_Results|in this category]]. The results for the current {{FedoraVersion|long|current}} release can be found [[:Category:{{FedoraVersion|long|current}}_Test_Results|in this category]]. These pages are created based on a [[QA:Desktop_validation_results_template|template page]].
| |
