| Fedora Test Day | |
|---|---|
| |
| Modularity | |
| Date | 2019-03-26 |
| Time | all day |
| Website | QA/Test Days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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 testing Modularity in Fedora 30
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - sgallagh (sgallagh), Petr Šabata (contyk), Adam Šamalík (asamalik)
- Quality Assurance - Adam Williamson (adamw),Sumantro Mukherjee (sumantrom), Kamil Páral (kparal) lruzicka(lruzicka) , coremodule(coremodule)
Prerequisites for Test Day
- A clean Fedora 30
- 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. If you don't see it, please file a new bug to Bugzilla, probably against Fedora Modules 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.
Test Results
This will be populated when the test day has ended