From Fedora Project Wiki
(Created page with "{{QA/Test_Case |description=This test case ensures the proper installation and basic functionality of the `dbus-broker`, `dbus-common`, and `dbus-daemon`. |setup= # Install the `dbus-broker`, `dbus-common`, and `dbus-daemon` packages: `sudo dnf install dbus-broker dbus-common dbus-daemon`. # Ensure the D-Bus broker is running: `systemctl status dbus-broker.service`. |actions= # Check the version of the installed packages: `rpm -q dbus-broker dbus-common dbus-daemon`. # L...") |
(No difference)
|
Latest revision as of 12:26, 14 August 2023
Description
This test case ensures the proper installation and basic functionality of the dbus-broker
, dbus-common
, and dbus-daemon
.
Setup
- Install the
dbus-broker
,dbus-common
, anddbus-daemon
packages:sudo dnf install dbus-broker dbus-common dbus-daemon
. - Ensure the D-Bus broker is running:
systemctl status dbus-broker.service
.
How to test
- Check the version of the installed packages:
rpm -q dbus-broker dbus-common dbus-daemon
. - List all the D-Bus services currently running using
dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames
. - Use the
dbus-monitor
tool to monitor D-Bus messages on the system bus or session bus. - Restart the
dbus-broker
service:systemctl restart dbus-broker.service
.
Expected Results
- The version command should display the correct versions of the installed packages.
- The list command should display all active D-Bus services.
dbus-monitor
should show live D-Bus messages as they occur.- No errors or crashes should occur during the process, and services relying on D-Bus should remain functional after the
dbus-broker
restart.
Optional
For advanced testing:
- Test sending and receiving custom messages using D-Bus and the broker.
- Verify the proper functioning of D-Bus activation where services are started on-demand.
- Examine the behavior of D-Bus under high load or with large message payloads.