From Fedora Project Wiki

Revision as of 08:10, 14 August 2023 by Sumantrom (talk | contribs) (Created page with "{{QA/Test_Case |description=This test case verifies the installation and basic functionality of the Cockpit server management platform and its supporting packages. |setup= # Install a fresh version of Fedora/ ensure nothing is running on localhost:9090. # Install the required Cockpit packages: `sudo dnf install cockpit cockpit-bridge cockpit-system cockpit-ws`. |actions= # Start the Cockpit service: `sudo systemctl start cockpit`. # Enable Cockpit to start on boot: `sud...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Description

This test case verifies the installation and basic functionality of the Cockpit server management platform and its supporting packages.

Setup

  1. Install a fresh version of Fedora/ ensure nothing is running on localhost:9090.
  2. Install the required Cockpit packages: sudo dnf install cockpit cockpit-bridge cockpit-system cockpit-ws.

How to test

  1. Start the Cockpit service: sudo systemctl start cockpit.
  2. Enable Cockpit to start on boot: sudo systemctl enable cockpit.
  3. Access the Cockpit web interface by opening a web browser and navigating to https://localhost:9090. Replace localhost with your server's IP address if you're accessing it from a different machine.
  4. Log in using your system credentials.
  5. Explore the Cockpit dashboard, system information, logs, and other functionalities.
  6. Perform a basic task, such as restarting the system, using the Cockpit interface.

Expected Results

  1. The Cockpit service should start without errors.
  2. The Cockpit web interface should be accessible via a web browser on port 9090.
  3. The login using system credentials should be successful.
  4. The Cockpit dashboard should display system information accurately (e.g., CPU, memory usage).
  5. System logs and other functionalities in the Cockpit interface should be functional and show real-time data.
  6. Actions performed via the Cockpit interface (like a system restart) should execute successfully.

Optional

For extended testing:

  1. Try accessing Cockpit from a different machine on the same network using the server's IP address.
  2. Install additional Cockpit plugins and ensure they are visible and functional in the Cockpit interface.
  3. Verify the interaction between cockpit-bridge and system APIs by monitoring system API calls.
  4. Test out the functionalities provided by the cockpit-system and cockpit-ws packages specifically, ensuring all components work harmoniously.