| 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?
After installing the Fedora Server snapshot and booting the new system, Cockpit is up and runnning, and listens on port 9090. Point a browser at http://IP:9090, and Cockpit's login page will load.
(Here, IP is the IP address of your machine. You can find it by logging into the machine on the text console as "root" and running ip addr.)
Once the Cockpit log in screen is loaded in your browser, log in as "root". You can log into Cockpit as any user that exists on the machine, but currently only "root" has enough privileges to execute the test cases. Trying with any other user, even those that are in the "wheel" group, will likely lead to techno-babble error messages. (This will be improved as Cockpit and its dependencies evolve, of course.)
The test cases are intentionally a bit vague. They don't tell you exactly what button to click, and what to type into which field. You have to figure that out yourself. :-) Cockpit should be discoverable´, and your feedback about this is very valuable.
Unfortunately, Cockpit is quite far from being finished. There are so many things worth improving that it will be a lot of work to report them all. Thus, we can not ask you to be exhaustive. Feel free to report only things that you consider non-obvious´ or are particularily important to you.
In fact, please stray from the test cases into whatever corner of Cockpit you want to explore!
Report your feedback on Github as issues for this repository and link to them from the test results.
Test Cases
- Free play
Test Results
If you have problems with any of the tests, report a bug here. 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 tables 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.
Basic
| User | Password change | Create user account | References |
|---|---|---|---|
| Sample User |  |
 |
Storage
| User | Monitor disk I/O | Create a RAID Device | Create a Logical Volume | References |
|---|
Network
| User | Monitor network I/O | Create VLAN | Create Bond | References |
|---|
Docker
| User | Download and run image | Create a new image and run it | References |
|---|