From Fedora Project Wiki

(Added crond as cloud example)
(changed default service shown from sshd to chronyd)
Line 6: Line 6:
# Perform an installation of the Fedora release you wish to test, making as few choices as possible and making the most obvious and simple choices where choice is required
# Perform an installation of the Fedora release you wish to test, making as few choices as possible and making the most obvious and simple choices where choice is required
|actions=
|actions=
{{admon/note|Service used for testing|You may use another service for testing if necessary (for instance, testing Fedora Cloud images remotely, where disabling sshd would prevent you accessing the system). Ensure it is a service which works reliably (like crond) - this is a test of the service management mechanism, not of the particular service.}}
{{admon/note|Service used for testing|You may use another service for testing if necessary. Ensure it is a service which works reliably - this is a test of the service management mechanism, not of the particular service.}}
# Log in to the installed system
# Log in to the installed system
# In a console, run the following commands:
# In a console, run the following commands:
#: {{command|su -c 'systemctl stop sshd.service'}}
#: {{command|su -c 'systemctl stop chronyd.service'}}
#: {{command|su -c 'systemctl disable sshd.service'}}
#: {{command|su -c 'systemctl disable chronyd.service'}}
# Now reboot. Log in again, and run the following commands:
# Now reboot. Log in again, and run the following commands:
#: {{command|su -c 'systemctl status sshd.service'}}
#: {{command|su -c 'systemctl status chronyd.service'}}
#: {{command|ps aux <nowiki>|</nowiki> grep sshd}}
#: {{command|ps aux <nowiki>|</nowiki> grep chronyd}}
#: {{command|su -c 'systemctl start sshd.service'}}
#: {{command|su -c 'systemctl start chronyd.service'}}
#: {{command|su -c 'systemctl status sshd.service'}}
#: {{command|su -c 'systemctl status chronyd.service'}}
#: {{command|ps aux <nowiki>|</nowiki> grep sshd}}
#: {{command|ps aux <nowiki>|</nowiki> grep chronyd}}
#: {{command|su -c 'systemctl stop sshd.service'}}
#: {{command|su -c 'systemctl stop chronyd.service'}}
#: {{command|su -c 'systemctl status sshd.service'}}
#: {{command|su -c 'systemctl status chronyd.service'}}
#: {{command|ps aux <nowiki>|</nowiki> grep sshd}}
#: {{command|ps aux <nowiki>|</nowiki> grep chronyd}}
#: {{command|su -c 'systemctl enable sshd.service'}}
#: {{command|su -c 'systemctl enable chronyd.service'}}
# Now reboot. Log in again, and run the following commands:
# Now reboot. Log in again, and run the following commands:
#: {{command|su -c 'systemctl status sshd.service'}}
#: {{command|su -c 'systemctl status chronyd.service'}}
#: {{command|ps aux <nowiki>|</nowiki> grep sshd}}
#: {{command|ps aux <nowiki>|</nowiki> grep chronyd}}
#: {{command|su -c 'systemctl disable sshd.service'}}
#: {{command|su -c 'systemctl disable chronyd.service'}}
# Now reboot. Log in again, and run the following commands:
# Now reboot. Log in again, and run the following commands:
#: {{command|su -c 'systemctl status sshd.service'}}
#: {{command|su -c 'systemctl status chronyd.service'}}
#: {{command|ps aux <nowiki>|</nowiki> grep sshd}}
#: {{command|ps aux <nowiki>|</nowiki> grep chronyd}}
|results=
|results=
# Each time they appear, the commands {{command|su -c 'systemctl status sshd.service'}} and {{command|ps aux <nowiki>|</nowiki> grep sshd}} check whether the service is running. The expected results, in order, are:
# Each time they appear, the commands {{command|su -c 'systemctl status chronyd.service'}} and {{command|ps aux <nowiki>|</nowiki> grep chronyd}} check whether the service is running. The expected results, in order, are:
#: Disabled and inactive (not running)
#: Disabled and inactive (not running)
#: Disabled but active (running)
#: Disabled but active (running)

Revision as of 03:02, 12 May 2020

Associated release criterion
This test case is associated with the Basic_Release_Criteria#system-service-manipulation 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 tests whether starting, stopping, enabling and disabling system services works as expected.

Setup

  1. Perform an installation of the Fedora release you wish to test, making as few choices as possible and making the most obvious and simple choices where choice is required

How to test

Service used for testing
You may use another service for testing if necessary. Ensure it is a service which works reliably - this is a test of the service management mechanism, not of the particular service.
  1. Log in to the installed system
  2. In a console, run the following commands:
    su -c 'systemctl stop chronyd.service'
    su -c 'systemctl disable chronyd.service'
  3. Now reboot. Log in again, and run the following commands:
    su -c 'systemctl status chronyd.service'
    ps aux | grep chronyd
    su -c 'systemctl start chronyd.service'
    su -c 'systemctl status chronyd.service'
    ps aux | grep chronyd
    su -c 'systemctl stop chronyd.service'
    su -c 'systemctl status chronyd.service'
    ps aux | grep chronyd
    su -c 'systemctl enable chronyd.service'
  4. Now reboot. Log in again, and run the following commands:
    su -c 'systemctl status chronyd.service'
    ps aux | grep chronyd
    su -c 'systemctl disable chronyd.service'
  5. Now reboot. Log in again, and run the following commands:
    su -c 'systemctl status chronyd.service'
    ps aux | grep chronyd

Expected Results

  1. Each time they appear, the commands su -c 'systemctl status chronyd.service' and ps aux | grep chronyd check whether the service is running. The expected results, in order, are:
    Disabled and inactive (not running)
    Disabled but active (running)
    Disabled and inactive (not running)
    Enabled and active (running)
    Disabled and inactive (not running)
Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_base_service_manipulation&oldid=576102"