From Fedora Project Wiki

mNo edit summary
 
(14 intermediate revisions by 2 users not shown)
Line 5: Line 5:
== Setup ==
== Setup ==


# This test case can be performed on both '''bare machines'''.
# This test case should be performed on either '''bare-metal or virtual''' machines. Leave a note in the comments on which one you performed this test.
# The computer must be equipped with a sound device, real or virtual.
# The computer must be '''equipped with a sound device'''.
# Install a desktop version of '''Fedora 34''' (or later).
# Install a desktop version of '''Fedora 35''' (or later).
# Boot the system and log in as a ''common user''.
# Boot the system and log in as a '''regular user'''.


== How to test ==
== How to test ==


<ol>
<ol>
<li><p>Check the PipeWire <code>systemd</code> service:</p>
<li><p>Check that the <code>pipewire-utils</code> package is installed. If not, report it and install it.</p><p>rpm -qa pipewire-utils</p></li>
<li><p>Check that PipeWire <code>systemd</code> service is '''active'''.</p>
<p><code>$ systemctl --user status pipewire</code></p></li>
<p><code>$ systemctl --user status pipewire</code></p></li>
<li><p>Check the PipeWire PulseAudio <code>systemd</code> service:</p>
<li><p>Check that PipeWire PulseAudio <code>systemd</code> service is '''active'''.</p>
<p><code>$ systemctl --user status pipewire-pulse</code></p></li>
<p><code>$ systemctl --user status pipewire-pulse</code></p></li>
<li><p>Check that PipeWire is working:</p>
<li><p>Check that PipeWire is working and that basic information about the ''PipeWire'' sessions can be obtained.</p>
<p><code>$ pw-dump 0</code></p></li>
<p><code>$ pw-dump 0</code></p></li>
<li><p>Check that the '''PulseAudio on PipeWire''' sound server is working:</p>
<li><p>Check that the '''WirePlumber''' is working. </p><p><code>systemctl --user status wireplumber</code></p></li>
<p><code>$ pactl info</code></p></li>
<li><p>Check that information can be obtained about its status. </p>
<li><p>List all audio and video device known to the system:</p>
<p><code>$ wpctl status</code></p></li>
<p><code>$ pactl list</code></p></li></ol>
</ol>


== Expected results ==
== Expected results ==


# The <code>pipewire</code> service is '''active'''.
# The required services must be installed and running by default without any user interaction.
# The <code>pipewire-pulse</code> service is '''active'''.
# The above mentioned commands are available and produce expected output.
# The <code>pw-dump</code> command shows information and settings about the currently running session.
 
# The <code>pactl info</code> command shows information about the ''PulseAudio'' server settings, especially the server name must read <code>PulseAudio (on PipeWire \ldots )</code>.
[[Category:Test Days Test Cases]]
# The <code>pactl list</code> command lists all available audio and video devices on the system.
[[Category:Package_pipewire_test_cases]]

Latest revision as of 11:09, 6 September 2021

PipeWire default

This test case tests that PipeWire is installed and running in the default installation.

Setup

  1. This test case should be performed on either bare-metal or virtual machines. Leave a note in the comments on which one you performed this test.
  2. The computer must be equipped with a sound device.
  3. Install a desktop version of Fedora 35 (or later).
  4. Boot the system and log in as a regular user.

How to test

  1. Check that the pipewire-utils package is installed. If not, report it and install it.

    rpm -qa pipewire-utils

  2. Check that PipeWire systemd service is active.

    $ systemctl --user status pipewire

  3. Check that PipeWire PulseAudio systemd service is active.

    $ systemctl --user status pipewire-pulse

  4. Check that PipeWire is working and that basic information about the PipeWire sessions can be obtained.

    $ pw-dump 0

  5. Check that the WirePlumber is working.

    systemctl --user status wireplumber

  6. Check that information can be obtained about its status.

    $ wpctl status

Expected results

  1. The required services must be installed and running by default without any user interaction.
  2. The above mentioned commands are available and produce expected output.