| Line 34: | Line 34: | ||
== Reporting bugs == | == Reporting bugs == | ||
If you have problems with any of the tests, have a look at the list of reported bugs in the [http://testdays.fedorainfracloud.org/events/ | If you have problems with any of the tests, have a look at the list of reported bugs in the [http://testdays.fedorainfracloud.org/events/25 results page]. If you don't see it, please a new bug to [https://bugzilla.redhat.com Bugzilla], probably against <code>lxqt-xxxxx</code> 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 == | == Test Results == | ||
Revision as of 14:35, 8 August 2017
| Fedora Test Day | |
|---|---|
| |
| LXQt 0.11.1 | |
| Date | 2017-08-17 |
| 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 installment of Fedora Test Day will focus on LXQt 0.11.1
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion ...
- Development - [[User:]] (xxxx)
- Quality Assurance - Adam Williamson (admaw), Mike Ruckman (roshi),Sumantro Mukherjee (sumantro), Kamil Páral (kparal), Quentin Tayssier (tenk)
Prerequisites for Test Day
- A fully updated Fedora 26 LXQt Spin installation, either on bare metal or in 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. If you don't see it, please a new bug to Bugzilla, probably against lxqt-xxxxx 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
The test results will be posted here after the test day is over