From Fedora Project Wiki

(add a requirement that firewall status be indicated, as the criteria state)
(associated with firewall configuration release criterion)
Line 1: Line 1:
 
{{Template:Associated_release_criterion|Beta|roles}}
 
{{Template:Associated_release_criterion|Beta|roles}}
 +
{{Template:Associated_release_criterion|Beta|firewall_configuration}}
  
 
{{QA/Test_Case
 
{{QA/Test_Case

Revision as of 01:18, 22 October 2014

Note.png
Associated release criterion
This test case is associated with the Fedora_36_Beta_Release_Criteria#roles 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.
Note.png
Associated release criterion
This test case is associated with the Fedora_36_Beta_Release_Criteria#firewall_configuration 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 a Rolekit role can be successfully enabled, started and queried 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. Create a configuration file with the minimum required settings for the role (domaincontroller instructions can be found here)
  2. Deploy the role with rolectl deploy --settings-file=/path/to/configfile [--name=instancename] (rolename)
  3. Start the role with rolectl start (instancename)
  4. Query the role with rolectl status (instancename) and rolectl settings (instancename)
  5. If possible, attempt to interact with the role in expected ways - for example, if it is a database server, attempt to connect to it and create a database
  6. Stop the role with rolectl stop (instancename)

Expected Results

  1. Role deployment must complete successfully
  2. The deployed role must start successfully
  3. Typical basic interaction with the deployed role must work correctly
  4. The deployed role must report its status and configuration settings correctly
  5. The status report must indicate the current status of the role's firewall ports/services
  6. The deployed role must stop correctly