| Line 28: | Line 28: | ||
== Prerequisite for Test Day == | == Prerequisite for Test Day == | ||
A Fedora 21 system which you can screw around with. | A Fedora 21 system which you can screw around with. This can be a VM, but we are also very interested in test results on real hardware. | ||
'''TODO:''' We will have | '''TODO:''' We will have Fedora Server install images available with a recent version of Cockpit. | ||
== How to test? == | == How to test? == | ||
Revision as of 08:07, 10 September 2014
| Fedora Test Days | |
|---|---|
| |
| Cockpit Test Day | |
| Date | 2014-09-16 |
| Time | all day |
| Website | QA/Fedora_21_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | cockpit-devel |
The Test Day page is under construction. It will be ready in time for the Test Day (and this message will be removed).
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 testing Cockpit. Cockpit is a server user interface.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Stef Walter (stefw), Marius Vollmer (mvollmer), Andreas Nillson (andraesn), Patrick Uiterwijk (puiterwijk)
- Quality Assurance - Jan Ščotka (jscotka)
Prerequisite for Test Day
A Fedora 21 system which you can screw around with. This can be a VM, but we are also very interested in test results on real hardware.
TODO: We will have Fedora Server install images available with a recent version of Cockpit.
How to test?
TODO:' Complete this section. High level details on how a contributor can get involved. This can include (but not limited to):
- Areas to target with exploratory testing
- A list of pre-defined test cases to execute
- How to report back results
Here's another common chunk (again, replace XX as above):
Update your machine
TODO: Complete this section.
If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:
Live image
TODO: Complete this section.
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.
Test Cases
- Free play
Test Results
TODO: Complete this section.
Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
If you have problems with any of the tests, report a bug to Bugzilla usually for the component udisks, or gnome-disk-utility for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the result template to enter your result, as shown in the example result line.
| User | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|
| Sample User |  |
 |
 |