From Fedora Project Wiki
Frantisekz (talk | contribs) (new compose) |
(moved testcase bits) |
||
| Line 14: | Line 14: | ||
== What to test? == | == What to test? == | ||
Today's | Today's installment of Fedora Test Day will focus on '''Anaconda''' | ||
== Who's available? == | == Who's available? == | ||
| Line 29: | Line 29: | ||
== How to test? == | == How to test? == | ||
=== Run the tests === | === Run the tests === | ||
Visit the [http://testdays.fedorainfracloud.org/events/40 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. | Visit the [http://testdays.fedorainfracloud.org/events/40 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. | ||
Revision as of 01:22, 16 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 installment 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), František Zatloukal (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
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.