From Fedora Project Wiki

(extend to cover (most) Beta criteria)
(criterion is now Basic, not Alpha)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Associated_release_criterion|Alpha|cockpit-management-interface}}
{{Template:Associated_release_criterion|Basic|cockpit-management-interface}}
{{Template:Associated_release_criterion|Beta|cockpit-management-interface}}
 
{{admon/info|Milestones|For release validation purposes, note that this test case covers levels of functionality for different milestones. Not all of the requirements must be met for all milestones. If you hit failures during the test, check the release criteria to see which milestone you should file a blocker bug against.}}


{{QA/Test_Case
{{QA/Test_Case
|description=This test case checks that Cockpit is enabled, accessible and functional after a Fedora Server installation, as required in the [[Server/Technical_Specification]].
|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=
# 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.
# 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
#: {{command|sudo firewall-cmd --list-all}} should show the cockpit service
#: {{command|sudo 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
# 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
# Log in to Cockpit with the root account or an administrative user account, and select the system from the host list
# Click 'Journal' and check you can browse the journal and open individual entries
# Click 'Services' and check you can see services with their statuses
|results=
|results=
# As far as you can reasonably test, Cockpit must be enabled and accessible on the test system after installation
# As far as you can reasonably test, Cockpit must be enabled and accessible on the test system after installation
# It must be possible to view the journal and service status from Cockpit
}}
}}
[[Category:Server_Acceptance_Test_Cases]]
[[Category:Server_Acceptance_Test_Cases]]

Latest revision as of 15:40, 1 February 2018

Note.png
Associated release criterion
This test case is associated with the Basic_Release_Criteria#cockpit-management-interface release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.


Description

This test case checks that Cockpit is enabled and accessible after a Fedora Server installation, as required in the Server/Technical_Specification.

Setup

  1. 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

  1. 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 errors
    sudo firewall-cmd --list-all should show the cockpit service
  2. 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

Expected Results

  1. As far as you can reasonably test, Cockpit must be enabled and accessible on the test system after installation
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Server_cockpit_default&oldid=510676"