Before an official Fedora release comes out, several alpha, beta and release candidate releases - known collectively as pre-releases - are made available. You can contribute by installing these pre-releases and testing them. Testing will involve executing test cases to verify installation on different hardware platforms and gathering installation test feedback. Everyone is encouraged to test anaconda and share your ideas, tests, and results.
Scope and Approach
Testing will include:
- Manually executed test cases using DVD, CDROM,
boot.isoor live image media
- Automatically executed test cases via the AutoQA system. For more information about automatic testing, please see Is Anaconda Broken Proposal and the install automation roadmap.
This is one of several release validation test plans. Each covers a particular type of testing - installation, base, desktop etc. This test plan on its own does not cover all release criteria, but the set of release validation test plans taken together ought to do so.
Timing of installation test events
Installation test events occur before milestone releases (e.g. Alpha, Beta, Final). Often this includes a Test compose followed by one or more Release candidate composes. A detailed list of QA events for Fedora 29 can be found at http://jreznik.fedorapeople.org/schedules/f-29/f-29-quality-tasks.html
The Fedora 29 Installation Test plan is available at QA:Fedora 29_Install_Test_Plan.
The test plan is designed to ensure that the release under test complies with the Fedora_Release_Criteria. If the criteria are adjusted or updated, new test cases should be created and no longer valid ones removed as appropriate.
Test results are recorded in a separate page for each test run. To ensure consistency, new test result pages are created using a template page. Test results for each release of Fedora are linked below.
- Fedora 29 install test results
- Fedora 28 install test results
- Fedora 27 install test results
- Additional installation results templates
The procedure for managing installation validation testing is documented as part of the general release validation testing procedure.
For further information or to send comments about installation testing, please contact the QA group.