From Fedora Project Wiki
Frantisekz (talk | contribs) (init) |
Frantisekz (talk | contribs) mNo edit summary |
||
| Line 20: | Line 20: | ||
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ... | The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ... | ||
* Development - [[User:m4rtink|m4rtink]] (m4rtink) | * Development - [[User:m4rtink|m4rtink]] (m4rtink) | ||
* Quality Assurance - [[User:adamw|Adam Williamson]] (admaw), [[User: | * Quality Assurance - [[User:adamw|Adam Williamson]] (admaw), [[User:pschindl|Petr Schindler]] (pschindl), [[User:Sumantrom|Sumantro Mukherjee]] (sumantrom), [[User:frantisekz|frantisekz]] (frantisekz) | ||
== Prerequisites for Test Day == | == Prerequisites for Test Day == | ||
Revision as of 14:09, 12 April 2018
| Fedora Test Day | |
|---|---|
| |
| Anaconda | |
| Date | 2018-04-16 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
Today's instalment of Fedora Test Day will focus on Anaconda
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - m4rtink (m4rtink)
- Quality Assurance - Adam Williamson (admaw), Petr Schindler (pschindl), Sumantro Mukherjee (sumantrom), frantisekz (frantisekz)
Prerequisites for Test Day
- Latest Fedora 28 Compose either on bare metal or VM (please make sure you have no important data on that installation, things might go wrong -- don't do this on your production machine!)
- Enough free space on HDD
How to test?
Run the tests
setup
- Prepare your test system for booting and installing from an install-capable Fedora image.
- If testing in a virtual machine, attach the image to the virtual machine as a CD or DVD.
- If testing optical media on a real machine, burn the image to a CD or DVD, insert it into the system's optical drive, and ensure the system is configured to boot from the optical drive.
- If testing USB media on a real machine, prepare the USB stick according to the official instructions, using the most prominently-recommended method (currently Fedora Media Writer), and ensure the system is configured to boot from the USB medium.
- If the image you are installing from is a network install image, ensure the system has a working network connection.
actions
- Boot the system from the prepared install medium.
- In the boot menu select the appropriate option to boot the image.
- Once booted, run the installer (if necessary) and complete an installation
results
- A boot menu must be displayed for users to select install options. Navigating the menu and selecting entries must work. If no option is selected, the installer (or live environment) must load after a reasonable timeout.
- If the image under test is a dedicated installer image, the default package set must be the intended default for that image.
- An installation using the default install repository for the image under test must complete the installation process.
Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.
Reporting bugs
If you have problems with any of the tests, have a look at the list of reported bugs in the results page. Please include the vulnerability output at the end of the test suite in the comments.
If you don't see it, please file a new bug to Bugzilla, probably against anaconda component. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC #fedora-test-day or #fedora-qa and we will help you.