m (Added missing category) |
m (internal link cleaning) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 99: | Line 99: | ||
! User | ! User | ||
! Hardware | ! Hardware | ||
! [ | ! [[QA:Testcase_Cockpit_Login|Password change]] | ||
! [ | ! [[QA:Testcase_Cockpit_Account|Create user account]] | ||
! References | ! References | ||
|- | |- | ||
Line 217: | Line 217: | ||
! User | ! User | ||
! Hardware | ! Hardware | ||
! [ | ! [[QA:Testcase_Cockpit_DiskIO|Monitor disk I/O]] | ||
! [ | ! [[QA:Testcase_Cockpit_RAID|Create a RAID Device]] | ||
! [ | ! [[QA:Testcase_Cockpit_LVM|Create a Logical Volume]] | ||
! References | ! References | ||
|- | |- | ||
Line 308: | Line 308: | ||
! User | ! User | ||
! Hardware | ! Hardware | ||
! [ | ! [[QA:Testcase_Cockpit_NetworkIO|Monitor network I/O]] | ||
! [ | ! [[QA:Testcase_Cockpit_VLAN|Create VLAN]] | ||
! [ | ! [[QA:Testcase_Cockpit_Bond|Create Bond]] | ||
! References | ! References | ||
|- | |- | ||
Line 398: | Line 398: | ||
! User | ! User | ||
! Hardware | ! Hardware | ||
! [ | ! [[QA:Testcase_Cockpit_DockerImage|Download and run image]] | ||
! [ | ! [[QA:Testcase_Cockpit_DockerCommit|Create a new image and run it]] | ||
! References | ! References | ||
|- | |- | ||
Line 466: | Line 466: | ||
<references group="long" /> | <references group="long" /> | ||
[[Category:Fedora 21 Test Days|c]] | [[Category:Fedora 21 Test Days|c]] |
Latest revision as of 21:42, 19 September 2016
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 |
What to test?[edit]
Today's installment of Fedora Test Day will focus on testing Cockpit. Cockpit is a server user interface.
Who's available[edit]
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Stef Walter (stefw), Marius Vollmer (mvollmer), Andreas Nilsson (andreasn), Patrick Uiterwijk (puiterwijk)
- Quality Assurance - Jan Ščotka (jscotka)
Prerequisite for Test Day[edit]
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.
- Install Fedora 21 Server. Make sure that your installation is recent enough. Either install Fedora 21 Server Alpha TC7 or run
yum update
in an older Fedora 21 Server installation. You should have at least Cockpit 0.23. In the Server variant of Fedora 21, Cockpit is enabled by default. For other variants, please refer to the Notes at the end of this page. - Prepared Live ISO images: (root have no password here by default, anything you type will access cockpit page)
- Image for virt-manager : http://fedorapeople.org/groups/qa/20140916-Cockpit-VM-disk-image.qcow2.xz
- user/password: test/test root/internal
curl https://fedorapeople.org/groups/qa/20140916-Cockpit-VM-disk-image.qcow2.xz >20140916-Cockpit-VM-disk-image.qcow2.xz unxz 20140916-Cockpit-VM-disk-image.qcow2.xz yum -y install qemu\* systemctl restart libvirtd virt-install --connect qemu:///system --ram 1024 -n cockpit --os-type=linux --os-variant=fedora20 --disk path=20140916-Cockpit-VM-disk-image.qcow2,device=disk,format=qcow2 --vcpus=1 --vnc --noautoconsole --import virt-manager&
Note that Docker is not enabled by default, but the test cases will tell you how to enable it.
How to test?[edit]
After boot, Cockpit is up and running and listens on port 9090.
- Point a browser at
http:
//<server-ip-address>:9090
. - Cockpit's login page will load.
- Cockpit uses a self-signed certificate, and your browser will very likely warn you about it.
(Here, <server-ip-address>
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. 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.
The test cases don't cover every feature of Cockpit. 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.
Please report your feedback either on Github or in Bugzilla.
Test Cases[edit]
Test Results[edit]
If you have problems with any of the tests, report a bug either on Github or in Bugzilla.
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[edit]
User | Hardware | Password change | Create user account | References |
---|---|---|---|---|
Alich | Hewlett-Packard HP xw4600 Workstation | [2] | ||
jskladan | X230 | |||
lnie | virt-manager | |||
baoboa | HP workstation Z400 | |||
jprokes | VPS | [2] | ||
dspurek | Lenovo 440s (+VM) | [2] | ||
roshi | virt-manager | |||
psklenar | virt image | [3] | ||
elemc | Gigabyte PH67-DS3-B3 | |||
lpol | openstack instances | |||
jscotka | lenovo T61 | [2][3][4] |
| |
omoris | Lenovo 430s (+VM) | |||
rskvaril | Lenovo T440s |
| ||
bblaskov | openstack | |||
alikins | f21-server-cockpit-virt-image | [2] | ||
konstantinjch | ASRock P67 Extreme4 | |||
pschindl | Lenovo ThinkPad T540p |
Storage[edit]
User | Hardware | Monitor disk I/O | Create a RAID Device | Create a Logical Volume | References |
---|---|---|---|---|---|
Alich | Hewlett-Packard HP xw4600 Workstation | ||||
jskladan | X230 | ||||
baoboa | HP workstation Z400 | ||||
jprokes | VPS | ||||
roshi | virt-manager | ||||
elemc | Gigabyte PH67-DS3-B3 | ||||
jscotka | lenovo T61 | ||||
rskvaril | Lenovo T440s | ||||
alikins | f21-server-cockpit-virt-image | [2] |
|||
konstantinjch | ASRock P67 Extreme4 | ||||
pschindl | Lenovo ThinkPad T540p | [4] |
Network[edit]
User | Hardware | Monitor network I/O | Create VLAN | Create Bond | References |
---|---|---|---|---|---|
jskladan | X230 | ||||
baoboa | HP workstation Z400 | ||||
jprokes | VPS |
| |||
todoleza | openstack/vps | [2] | |||
roshi | virt-manager | ||||
elemc | Gigabyte PH67-DS3-B3 | ||||
jscotka | lenovo T61 | ||||
omoris | Lenovo 430s (+VM) | ||||
rskvaril | Lenovo T440s | ||||
konstantinjch | ASRock P67 Extreme4 | ||||
pschindl | Lenovo ThinkPad T540p |
Docker[edit]
User | Hardware | Download and run image | Create a new image and run it | References |
---|---|---|---|---|
baoboa | HP workstation Z400 | |||
jprokes | VPS | |||
dspurek | Lenovo 440s (+VM) | [2] | ||
roshi | virt-manager | |||
elemc | Gigabyte PH67-DS3-B3 | |||
lpol | openstack instances | |||
jscotka | lenovo T61 | |||
omoris | Lenovo 430s (+VM) |
Notes[edit]
We recommend that you install Fedora 21 Server since we would like you to also test whether Cockpit really works out of the box. Of course, if you would like to test Cockpit but would rather not go through the trouble of installing Fedora from scratch yet one more time, you can also add Cockpit to your existing Fedora system.
yum -y install cockpit docker-io fedora-dockerfiles wmdocker firewall-cmd --permanent --add-service=cockpit systemctl reload firewalld.service systemctl start cockpit.socket systemctl enable cockpit.socket
Long comments[edit]
- ↑ Some bugs which I found just by using cockpit (not relevant for this testcase) https://github.com/cockpit-project/cockpit/issues/1175 https://github.com/cockpit-project/cockpit/issues/1179 https://github.com/cockpit-project/cockpit/issues/1182
- ↑ Unclear if formatting needed to happen to the "Raid device" on the storage-detail page (Format is an option in it's drop down options) or the "Content" (defaults to "Format" option).