(note use of self-signed https cert by default)
(criterion is now Basic, not Alpha)
|Line 1:||Line 1:|
Latest revision as of 15:40, 1 February 2018
This test case checks that Cockpit is enabled and accessible after a Fedora Server installation, as required in the Server/Technical_Specification.
- 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.socketshould show the service as enabled and running without errors
sudo firewall-cmd --list-allshould show the cockpit service
- Connect to the Cockpit web interface on the test system from another system with a web browser pointed to http://server:9090 ; the Cockpit management interface should show up. You can also use https://server:9090 , but unless you changed the server certificate from the default, it will be self-signed and the browser will show a warning or refuse to connect
- As far as you can reasonably test, Cockpit must be enabled and accessible on the test system after installation