|Fedora Test Days|
|Cockpit Test Day|
|Mail • Subscribe • Archives|
What to test?
Today's installment of Fedora Test Day will focus on testing Cockpit. Cockpit is a server user interface.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Stef Walter (stefw), Marius Vollmer (mvollmer), Andreas Nilsson (andraesn), Patrick Uiterwijk (puiterwijk)
- Quality Assurance - Jan Ščotka (jscotka)
Prerequisite for Test Day
A machine that can run Fedora 21 and that you can screw around with. This can be a virtual machine, but we are also very interested in test results on real hardware.
The test machine should ideally have multiple disks and multiple network interfaces. If you use a virtual machine, just add some virtual disks and network adapters.
How to test?
Install Fedora 21 Server Alpha TC6 on your machine.
Then update Cockpit to the most recent version by running
yum update cockpit. You should get at least version 0.23. Reboot the machine after updating Cockpit.
After boot, Cockpit is up and runnning and listens on port 9090. Point a browser at
//IP:9090, and Cockpit's login page will load. Cockpit uses a self-signed certificate, and your browser will very likely warn you about it.
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
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. For example, most of the dialogs don't do intelligent validation of user input. 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!
When Cockpit encounters an internal error, a red "Oops" label will appear at the top right. Please report it when this happens. It is not a good idea to continue using Cockpit after an "Oops", but simply reloading the page should put you back on track.
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.
= Testdat result App
|User||Password change||Create user account||References|
|User||Monitor disk I/O||Create a RAID Device||Create a Logical Volume||References|
|User||Monitor network I/O||Create VLAN||Create Bond||References|
|User||Download and run image||Create a new image and run it||References|
to install&enable cockpit service after restart and allow access from outside:
yum -y install cockpit firewall-cmd --permanent --add-service=cockpit systemctl reload firewalld.service systemctl start cockpit.socket systemctl enable cockpit.socket