From Fedora Project Wiki
(actually, let's split it up) |
(clean up a bit) |
||
Line 2: | Line 2: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This test case checks that Cockpit is enabled | |description=This test case checks that Cockpit is enabled and accessible after a Fedora Server installation, as required in the [[Server/Technical_Specification]]. | ||
|setup= | |||
# Install the Fedora Server release you wish to test, in graphical or text mode, making as few choices as possible and making the most simple and obvious choices where a choice is required. | |||
|actions= | |actions= | ||
# Boot the installed system, and check that Cockpit is running and accessible: | # Boot the installed system, and check that Cockpit is running and accessible: | ||
#: {{command|sudo systemctl status cockpit.socket}} should show the service as enabled and running without errors | #: {{command|sudo systemctl status cockpit.socket}} should show the service as enabled and running without errors |
Revision as of 00:44, 22 October 2014
Description
This test case checks that Cockpit is enabled and accessible after a Fedora Server installation, as required in the Server/Technical_Specification.
Setup
- Install the Fedora Server release you wish to test, in graphical or text mode, making as few choices as possible and making the most simple and obvious choices where a choice is required.
How to test
- Boot the installed system, and check that Cockpit is running and accessible:
sudo systemctl status cockpit.socket
should show the service as enabled and running without errorssudo firewall-cmd --list-all
should show the cockpit service
- Connect to the Cockpit port on the test system from another system with a web browser; the Cockpit management interface should show up
Expected Results
- As far as you can reasonably test, Cockpit must be enabled and accessible on the test system after installation