[Proposal] Test Cases for the Fedora Audio Test Day.

[Lukas Ruzicka]

Hello friends of Fedora.

As you know, Fedora 34 will have PipeWire as a default sound solution to
replace PulseAudio.
We would like to organize a Fedora Audio Test Day that will be aimed on the
most common audio use on Fedora. It should help to prevent a situation when
a problem will go unnoticed into the new release.

Below, you can find the drafts of the test cases prepared on our Wiki for
you to read and comment. Also, if you have some other audio use cases that
you think should be tested, please let us know. Any suggestions are welcome.

List of test cases to test that:

   - PipeWire is used by default (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_default
   )
   - PipeWire CLI works (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_cli)
   - ALSA backend works (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_ALSA_backend)
   - Basic Audio tests (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio)
   - Pavucontrol works (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_basic
   )
   - Pavucontrol mixing (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_mixing
   )
   - Pavucontrol recording (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_reco...
   )
   - Pavucontrol add and remove devices (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_addr...
   )
   - PipeWire handles Bluetooth devices (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_bluetooth_devices
   )
   - Jack applications (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack)
   - Jack MIDI routing (
   https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack_midi)




-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Kamil Paral]

On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:

>  List of test cases to test that:
>
>     - PipeWire is used by default (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_default
>     )
>
>  
"This test case can be performed on both bare machines." doesn't make
sense
to me.

"Boot the system and log in as a common user." - I think the more
frequently used term is a "regular user". Do I understand correctly that
you mean any non-root user (i.e. your regular user can have admin
privileges - be in the wheel group, right?). Perhaps you can clarify with
"log in as a regular user (i.e. not root)" or similar.

I really really really dislike when there's a testing step "Run command X",
but the step doesn't say what the output should be. And you have to look at
the bottom and try to figure out where it is in the Expected results
section. And basically piece together the actual steps by jumping forth and
back, easily making mistakes or skipping something. The Expected results
section should contain some overall guidance that is valid for the whole
testcase duration, or instructions which don't fit into the testing
structure. But immediate result checking should be part of the How to test
section. For example:
"Check that the pipewire systemd service shows up as active: $ systemctl
--user status pipewire"
or
"Run "pactl list" and verify that is lists all available audio and video
devices on the system"

"the server name must read PulseAudio (on PipeWire \ldots )" - that's some
forgotten formatting in there, I guess?


>     - PipeWire CLI works (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_cli)
>     - ALSA backend works (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_ALSA_backend)
>     - Basic Audio tests (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio)
>     - Pavucontrol works (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_basic
>     )
>     - Pavucontrol mixing (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_mixing
>     )
>     - Pavucontrol recording (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_reco...
>     )
>     - Pavucontrol add and remove devices (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_addr...
>     )
>     - PipeWire handles Bluetooth devices (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_bluetooth_devices
>     )
>     - Jack applications (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack)
>     - Jack MIDI routing (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack_midi)
>
>  
Could you please rewrite the rest of the testcases into a more readable
format (regarding the "Expected results" section) before I review them all?
Just by quickly looking at them, some of them are very hard to follow,
especially when they commonly have 8+ points in the expected results, and
my brain hurts when trying to make sense of them in this format. I would
get discouraged from executing these test cases just on this ground alone
:-) Thanks a lot.

[Kamil Paral]

On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:

>  Below, you can find the drafts of the test cases prepared on our Wiki
> for
>  you to read and comment. Also, if you have some other audio use cases that
>  you think should be tested, please let us know. Any suggestions are welcome.
>  
>  List of test cases to test that:
>  
Oh, one more question. Can you please specify which testcases you think
should be general testcases to be included in our release validation
matrices, and which testcases you consider PipeWire TestDay-related only?
I'm asking because testday-only testcases can often be more specific, while
general-purpose testcases should be more generic (so that we can use them
in many releases and environments), and I might be reading them in a
different light, then. Thanks.

[Lukas Ruzicka]

On Mon, Feb 15, 2021 at 11:09 AM Kamil Paral <kparal(a)redhat.com&gt; wrote:

>  On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka
> <lruzicka(a)redhat.com&gt; wrote:
>
> > Below, you can find the drafts of the test cases prepared on our Wiki for
> > you to read and comment. Also, if you have some other audio use cases that
> > you think should be tested, please let us know. Any suggestions are welcome.
> >
>
> > List of test cases to test that:
> >
>
>  Oh, one more question. Can you please specify which testcases you think
>  should be general testcases to be included in our release validation
>  matrices, and which testcases you consider PipeWire TestDay-related only?
>  
All tests cases in this batch are intended for Audio Test Days. There is
not need to change the Basic Audio test case we have already had and there
is a new recording test case proposed that we discussed some time ago here
on this list.

_______________________________________________

>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Lukas Ruzicka]

>  "This test case can be performed on both bare machines." doesn't make
>  sense to me.
>  
Originally I thought that some tests could be done on VMs, too, but then I
thought that I do not want it, cause it may only cause some troubles. This
is a remnant which I overlooked.


>  "Boot the system and log in as a common user." - I think the more
>  frequently used term is a "regular user". Do I understand correctly that
>  you mean any non-root user (i.e. your regular user can have admin
>  privileges - be in the wheel group, right?). Perhaps you can clarify with
>  "log in as a regular user (i.e. not root)" or similar.
>  
Ok, "regular user" it will be.


>  I really really really dislike when there's a testing step "Run command
>  X", but the step doesn't say what the output should be. And you have to
>  look at the bottom and try to figure out where it is in the Expected
>  results section. And basically piece together the actual steps by jumping
>  forth and back, easily making mistakes or skipping something. The Expected
>  results section should contain some overall guidance that is valid for the
>  whole testcase duration, or instructions which don't fit into the testing
>  structure. But immediate result checking should be part of the How to test
>  section. For example:
>  "Check that the pipewire systemd service shows up as active: $ systemctl
>  --user status pipewire"
>  or
>  "Run "pactl list" and verify that is lists all available audio and video
>  devices on the system"
>  
Hmm, this makes actually sense, because I dislike the way to split it, too.
Will rewrite it.
Thanks.


>  "the server name must read PulseAudio (on PipeWire \ldots )" - that's some
>  forgotten formatting in there, I guess?
>  
Sure, LaTeX origin.


> >
> >    - PipeWire CLI works (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_cli)
> >    - ALSA backend works (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_ALSA_backend)
> >    - Basic Audio tests (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio)
> >    - Pavucontrol works (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_basic
> >    )
> >    - Pavucontrol mixing (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_mixing
> >    )
> >    - Pavucontrol recording (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_reco...
> >    )
> >    - Pavucontrol add and remove devices (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_addr...
> >    )
> >    - PipeWire handles Bluetooth devices (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_bluetooth_devices
> >    )
> >    - Jack applications (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack)
> >    - Jack MIDI routing (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack_midi)
> >
> >
>  Could you please rewrite the rest of the testcases into a more readable
>  format (regarding the "Expected results" section) before I review them all?
>  Just by quickly looking at them, some of them are very hard to follow,
>  especially when they commonly have 8+ points in the expected results, and
>  my brain hurts when trying to make sense of them in this format. I would
>  get discouraged from executing these test cases just on this ground alone
>  :-) Thanks a lot.
>  
Yes.


>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Kamil Paral]

On Mon, Feb 15, 2021 at 11:37 AM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:

>  On Mon, Feb 15, 2021 at 11:09 AM Kamil Paral
> <kparal(a)redhat.com&gt; wrote:
>
> > Oh, one more question. Can you please specify which testcases you think
> > should be general testcases to be included in our release validation
> > matrices, and which testcases you consider PipeWire TestDay-related only?
> >
>
>  All tests cases in this batch are intended for Audio Test Days. There is
>  not need to change the Basic Audio test case we have already had and there
>  is a new recording test case proposed that we discussed some time ago here
>  on this list.
>  
So you say there's no need to change the Basic Audio test case [1] yet
there is a testcase for it [2], which on a proper look is called slightly
different but basically the same. Would it make sense to either rename it
to something that is less interchangeable, or unify it into a single test
case applicable for both use cases?

[1] https://fedoraproject.org/wiki/QA:Testcase_audio_basic
[2] https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio

[Lukas Ruzicka]

>  So you say there's no need to change the Basic Audio test case [1] yet
>  there is a testcase for it [2], which on a proper look is called slightly
>  different but basically the same. Would it make sense to either rename it
>  to something that is less interchangeable, or unify it into a single test
>  case applicable for both use cases?
>  
The Test Day basic audio has specific applications listed which should be
used, because this is what Wim suggested to test. The usual Audio Basic has
no such listings and I do not think that people want to specify some
applications and leave out some others that they might possibly test.

The name can be easily changed.



>  [1] https://fedoraproject.org/wiki/QA:Testcase_audio_basic
>  [2] https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio
>
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Lukas Ruzicka]

Hello again,

I have changed the test cases according to Kamil's review, so please take a
look and let me know what you think of them.

Also the Testcase_basic_audio has been renamed to not interfere with the
Release validation test case and lives now here:
https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_audio_selected_apps

Have a nice day.


On Mon, Feb 15, 2021 at 12:33 PM Kamil Paral <kparal(a)redhat.com&gt; wrote:

>  On Mon, Feb 15, 2021 at 11:37 AM Lukas Ruzicka
> <lruzicka(a)redhat.com&gt;
>  wrote:
>
> > On Mon, Feb 15, 2021 at 11:09 AM Kamil Paral <kparal(a)redhat.com&gt; wrote:
> >
> >> Oh, one more question. Can you please specify which testcases you think
> >> should be general testcases to be included in our release validation
> >> matrices, and which testcases you consider PipeWire TestDay-related only?
> >>
> >
> > All tests cases in this batch are intended for Audio Test Days. There is
> > not need to change the Basic Audio test case we have already had and there
> > is a new recording test case proposed that we discussed some time ago here
> > on this list.
> >
>
>  So you say there's no need to change the Basic Audio test case [1] yet
>  there is a testcase for it [2], which on a proper look is called slightly
>  different but basically the same. Would it make sense to either rename it
>  to something that is less interchangeable, or unify it into a single test
>  case applicable for both use cases?
>
>  [1] https://fedoraproject.org/wiki/QA:Testcase_audio_basic
>  [2] https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_basic_audio
>
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Kamil Paral]

On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:

>  List of test cases to test that:
>
>     - PipeWire is used by default (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_default
>     )
>
>  
s/bare machines/bare-metal machines/
(Also in (all) other testcases)


>     - PipeWire CLI works (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_cli)
>
>  
"Have an audio file ready (wav)."
It would be nice either to link to some freely available sample, or specify
a path where such a file is present on default desktop installations
(there's usually something in /usr/share/sounds/, for example). Otherwise
each tester needs to waste time searching for a wav file individually.

"Play a sound file over the default target and check that it is correctly
played over the default sound device.
$ pw-cat -p <audiofile>"
Is this supposed to be the wav file, or any audio file (e.g. ogg)? A
clarification would be good, e.g.:
"Play a wav sound file over the default target and check that it is
correctly played over the default sound device.
$ pw-cat -p <audiofile.wav>"


>     - ALSA backend works (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_ALSA_backend)
>
>  
"Log in as a common user."
A "regular user", if you want to make it consistent.

s/headphoned/headphones/

"Keep an audio file at hand (wav)."
Ditto as above.

The Expected Results section could be simplified, either merged into the
steps, or e.g. "Every time you use `aplay` to play an audio file in each
testing step, you can hear it correctly".


>     - Audio Selected Apps (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_audio_selected_apps
>     )
>     - Pavucontrol works (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_basic
>     )
>
>  
LGTM


>     - Pavucontrol mixing (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_mixing
>     )
>
>  
"Connect your speakers (headphones) to all your computer’s sound
devices."
This confused me until I read the whole testcase. It sounds like I should
connect the same headphones to all sound outputs, which is of course
impossible to do at the same time, so I thought I would re-plug it to each
device as needed. Turns out you wanted to say "make sure each sound device
has some speakers/headphones connected to it", right? It would be good to
make this clearer.


>     - Pavucontrol recording (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_reco...
>     )
>
>  
LGTM


>     - Pavucontrol add and remove devices (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_addr...
>     )
>
>  
"The computer must be equipped with a sound device with multiple ports
(speakers and phones), such as laptops."
Perhaps you can also say "or desktops with an audio front panel (where
plugging a jack into the front audio panel would disable the usual jack
output on the computer's back)" or similar, so that people know laptops are
not strictly needed.

"Plug in an HDMI monitor and check that the device appears in the
Pavucontrol’s list of devices."
I'm a bit confused that Setup didn't speak about HDMI at all and suddenly
in step 8 I need it. If it is a requirement, it should be in Setup. If it
is just optional, it should be said so ("If you have a HDMI monitor, ...").
Also:
a) audio routing is available not just with HDMI, but also with DisplayPort
(which might be even more common, for desktop users)
b) just a HDMI/DP monitor is not enough, I think. It has to either have its
own speakers, or an output jack (which you can plug headphones/speakers
into). If it doesn't have any audio output, I'm not sure whether it appears
as an audio output device once connected (and even if it did, you wouldn't
be able to verify it works).


>     - PipeWire handles Bluetooth devices (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_bluetooth_devices
>     )
>
>  
"The computer must be equipped with a Bluetooth adapter."
And also you need to have some BT device to test with. Those can be
BT-enabled headphones or speakers. Is there anything else? Can I test it
using a phone somehow? Just wondering.



>     - Jack applications (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack)
>
>  
"Install the pipewire-jack-audio-connection-kit package. Using the
--allowerasing option might be necessary for successful installation."
This might be confusing if one doesn't know the option and therefore
doesn't realize you're talking about dnf.




>     - Jack MIDI routing (
>     https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack_midi)
>
>  
"Install the pipewire-jack-audio-connection-kit package. Using the
--allowerasing option might be necessary for successful installation."
Ditto.

Overall it looks very good. Note that some time ago I created a special
category for "test day's test cases", and so let's put all of those in
when
moving them into the final location:
https://fedoraproject.org/wiki/Category:Test_Days_Test_Cases
Since those testcases are related to the PipeWire testday, you can prefix
them like that, e.g. "Testcase PipeWire ALSA backend" or "Testcase
PipeWire
Jack". Just a thought.

As discussed yesterday at our team meeting, adding one more testcase to
test popular videoconferencing tools is probably a good idea.

Thanks for your work,
Kamil

[Lukas Ruzicka]

Thank you, Kamil, for the review, I will work on it tomorrow again to
incorporate the suggestions.

Lukas

On Wed, Feb 17, 2021 at 4:00 PM Kamil Paral <kparal(a)redhat.com&gt; wrote:

>  On Fri, Feb 12, 2021 at 2:28 PM Lukas Ruzicka
> <lruzicka(a)redhat.com&gt; wrote:
>
> > List of test cases to test that:
> >
> >    - PipeWire is used by default (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_default
> >    )
> >
> >
>  s/bare machines/bare-metal machines/
>  (Also in (all) other testcases)
>
>
> >    - PipeWire CLI works (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pipewire_cli)
> >
> >
>  "Have an audio file ready (wav)."
>  It would be nice either to link to some freely available sample, or
>  specify a path where such a file is present on default desktop
>  installations (there's usually something in /usr/share/sounds/, for
>  example). Otherwise each tester needs to waste time searching for a wav
>  file individually.
>
>  "Play a sound file over the default target and check that it is correctly
>  played over the default sound device.
>  $ pw-cat -p <audiofile>"
>  Is this supposed to be the wav file, or any audio file (e.g. ogg)? A
>  clarification would be good, e.g.:
>  "Play a wav sound file over the default target and check that it is
>  correctly played over the default sound device.
>  $ pw-cat -p <audiofile.wav>"
>
>
> >
> >    - ALSA backend works (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_ALSA_backend)
> >
> >
>  "Log in as a common user."
>  A "regular user", if you want to make it consistent.
>
>  s/headphoned/headphones/
>
>  "Keep an audio file at hand (wav)."
>  Ditto as above.
>
>  The Expected Results section could be simplified, either merged into the
>  steps, or e.g. "Every time you use `aplay` to play an audio file in each
>  testing step, you can hear it correctly".
>
>
> >
> >    - Audio Selected Apps (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_audio_selected_apps
> >    )
> >    - Pavucontrol works (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_basic
> >    )
> >
> >
>  LGTM
>
>
> >
> >    - Pavucontrol mixing (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_mixing
> >    )
> >
> >
>  "Connect your speakers (headphones) to all your computer’s sound devices."
>  This confused me until I read the whole testcase. It sounds like I should
>  connect the same headphones to all sound outputs, which is of course
>  impossible to do at the same time, so I thought I would re-plug it to each
>  device as needed. Turns out you wanted to say "make sure each sound device
>  has some speakers/headphones connected to it", right? It would be good to
>  make this clearer.
>
>
> >
> >    - Pavucontrol recording (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_reco...
> >    )
> >
> >
>  LGTM
>
>
> >
> >    - Pavucontrol add and remove devices (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_pavucontrol_addr...
> >    )
> >
> >
>  "The computer must be equipped with a sound device with multiple ports
>  (speakers and phones), such as laptops."
>  Perhaps you can also say "or desktops with an audio front panel (where
>  plugging a jack into the front audio panel would disable the usual jack
>  output on the computer's back)" or similar, so that people know laptops are
>  not strictly needed.
>
>  "Plug in an HDMI monitor and check that the device appears in the
>  Pavucontrol’s list of devices."
>  I'm a bit confused that Setup didn't speak about HDMI at all and suddenly
>  in step 8 I need it. If it is a requirement, it should be in Setup. If it
>  is just optional, it should be said so ("If you have a HDMI monitor, ...").
>  Also:
>  a) audio routing is available not just with HDMI, but also with
>  DisplayPort (which might be even more common, for desktop users)
>  b) just a HDMI/DP monitor is not enough, I think. It has to either have
>  its own speakers, or an output jack (which you can plug headphones/speakers
>  into). If it doesn't have any audio output, I'm not sure whether it appears
>  as an audio output device once connected (and even if it did, you wouldn't
>  be able to verify it works).
>
>
> >
> >    - PipeWire handles Bluetooth devices (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_bluetooth_devices
> >    )
> >
> >
>  "The computer must be equipped with a Bluetooth adapter."
>  And also you need to have some BT device to test with. Those can be
>  BT-enabled headphones or speakers. Is there anything else? Can I test it
>  using a phone somehow? Just wondering.
>
>
>
> >
> >    - Jack applications (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack)
> >
> >
>  "Install the pipewire-jack-audio-connection-kit package. Using the
>  --allowerasing option might be necessary for successful installation."
>  This might be confusing if one doesn't know the option and therefore
>  doesn't realize you're talking about dnf.
>
>
>
>
> >
> >    - Jack MIDI routing (
> >    https://fedoraproject.org/wiki/User:Lruzicka/QA:Testcase_jack_midi)
> >
> >
>  "Install the pipewire-jack-audio-connection-kit package. Using the
>  --allowerasing option might be necessary for successful installation."
>  Ditto.
>
>  Overall it looks very good. Note that some time ago I created a special
>  category for "test day's test cases", and so let's put all of those in
> when
>  moving them into the final location:
>  https://fedoraproject.org/wiki/Category:Test_Days_Test_Cases
>  Since those testcases are related to the PipeWire testday, you can prefix
>  them like that, e.g. "Testcase PipeWire ALSA backend" or "Testcase
> PipeWire
>  Jack". Just a thought.
>
>  As discussed yesterday at our team meeting, adding one more testcase to
>  test popular videoconferencing tools is probably a good idea.
>
>  Thanks for your work,
>  Kamil
>
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Lukas Ruzicka]

>  Overall it looks very good. Note that some time ago I created a special
>  category for "test day's test cases", and so let's put all of those in
> when
>  moving them into the final location:
>  https://fedoraproject.org/wiki/Category:Test_Days_Test_Cases
>  Since those testcases are related to the PipeWire testday, you can prefix
>  them like that, e.g. "Testcase PipeWire ALSA backend" or "Testcase
> PipeWire
>  Jack". Just a thought.
>
>  
I have corrected the test cases accordingly. How do I move them into the
correct category and rename them to their new names?



>  As discussed yesterday at our team meeting, adding one more testcase
> to
>  test popular videoconferencing tools is probably a good idea.
>  
I have to look around how this could be tested using some tool that does
not require anyones presence.
@Adam Williamson <awilliam(a)redhat.com&gt;  suggested the following page:
zoom.us/test however I am not able to tell whether audio is sent to it
because there is no feedback and recording cannot be started at that
meeting. Again, to test the recording, registration is required.

I have not been able to track down an online video conferencing system that
would actually allow some testing to unregistered users.

Do you think a test case that needs two people connect in a conference
would be plausible?



>  Thanks for your work,
>  Kamil
>
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Kamil Paral]

On Thu, Feb 18, 2021 at 2:58 PM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:

>  Overall it looks very good. Note that some time ago I created a
> special
> > category for "test day's test cases", and so let's put all of those
> in when
> > moving them into the final location:
> > https://fedoraproject.org/wiki/Category:Test_Days_Test_Cases
> > Since those testcases are related to the PipeWire testday, you can prefix
> > them like that, e.g. "Testcase PipeWire ALSA backend" or "Testcase
> PipeWire
> > Jack". Just a thought.
> >
> >
>  I have corrected the test cases accordingly. How do I move them into the
>  correct category
>  
Just add
[[Category:Test Days Test Cases]]
to the bottom of each testcase. That will make them show up in the category.

You can also add
[[Category:Package_pipewire_test_cases]]
and it will make Bodhi show your testcases for all pipewire updates.


>  and rename them to their new names?
>  
When you're logged in to the wiki, each page has a Move button in the top
right corner.


>  As discussed yesterday at our team meeting, adding one more testcase
> to
> > test popular videoconferencing tools is probably a good idea.
> >
>
>  I have to look around how this could be tested using some tool that does
>  not require anyones presence.
>  @Adam Williamson <awilliam(a)redhat.com&gt;  suggested the following page:
>  zoom.us/test however I am not able to tell whether audio is sent to it
>  because there is no feedback and recording cannot be started at that
>  meeting. Again, to test the recording, registration is required.
>
>  I have not been able to track down an online video conferencing system
>  that would actually allow some testing to unregistered users.
>
>  Do you think a test case that needs two people connect in a conference
>  would be plausible?
>  
I think we're overcomplicating this unnecessarily. Of course it would be
nice if all major teleconferencing tools offered an echo service for
unregistered users, and if we are aware of some of those, we should include
links/instructions. But this is a community test day, and so we can use the
strengths of the community to test this. There is a high chance most
participants are already familiar with some of these tools and have their
accounts registered. They even probably have family members or co-workers
or other events they regularly talk to/attend to. So why overthink this?
Just ask people to run the Live image/upgrade to specific package versions
and start their preferred teleconferencing tool and test whether it works
as usual. If they can't do it on that very day, perhaps they can do it a
day or two later, and submit results. Each result should have a note saying
which tool/service was tested. Simple.

[Lukas Ruzicka]

>  Just add
>  [[Category:Test Days Test Cases]]
>  to the bottom of each testcase. That will make them show up in the
>  category.
>
>  You can also add
>  [[Category:Package_pipewire_test_cases]]
>  and it will make Bodhi show your testcases for all pipewire updates.
>  
Cool, thanks.


>  day, perhaps they can do it a day or two later, and submit results.
> Each
>  result should have a note saying which tool/service was tested. Simple.
>  

Ok, no problem.

>  
_______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Brandon Nielsen]

On 2/18/21 10:16 AM, Kamil Paral wrote:
[Snip]
>  
>  
>  I think we're overcomplicating this unnecessarily. Of course it would be 
>  nice if all major teleconferencing tools offered an echo service for 
>  unregistered users, and if we are aware of some of those, we should 
>  include links/instructions. But this is a community test day, and so we 
>  can use the strengths of the community to test this. There is a high 
>  chance most participants are already familiar with some of these tools 
>  and have their accounts registered. They even probably have family 
>  members or co-workers or other events they regularly talk to/attend to. 
>  So why overthink this? Just ask people to run the Live image/upgrade to 
>  specific package versions and start their preferred teleconferencing 
>  tool and test whether it works as usual. If they can't do it on that 
>  very day, perhaps they can do it a day or two later, and submit results. 
>  Each result should have a note saying which tool/service was tested. Simple.
>   
Mumble supports both local and server loopback. Additionally the initial 
setup wizard is probably a good indicator if devices are working 
correctly. Unfortunately I don't know of a good publicly available 
testing server.

[Kamil Paral]

On Thu, Feb 18, 2021 at 8:37 PM Brandon Nielsen <nielsenb(a)jetfuse.net&gt;
wrote:

>  Mumble supports both local and server loopback. Additionally the
> initial
>  setup wizard is probably a good indicator if devices are working
>  correctly. Unfortunately I don't know of a good publicly available
>  testing server.
>  
We already have local recording use case covered. The point of the new
testcase is to test widely used teleconferencing solutions (most of them
proprietary), in browsers and specialized apps, because their functionality
has been vitaly important for a lot of people in the past year and probably
will continue being so for some time.

[Lukas Ruzicka]

The current version of the test cases for Fedora Audio Test Day are here:

   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_PipeWire_default
   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_PipeWire_CLI
   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_ALSA_backend
   -
   https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Selected_Applications...
   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Pavucontrol_Basics
   -
   https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Pavucontrol_Recording
   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Pavucontrol_Mixing
   -
   https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Pavucontrol_Add_Remove
   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Jack_Applications
   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Jack_Midi_Routing
   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Bluetooth_Devices
   - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Video_Conferencing

Please, if you feel like you would like to add something to them, let me
know as soon as possible. Otherwise, I will take them as finished and will
proceed with the next steps towards the real Audio Test Day.

Have a nice time.

On Fri, Feb 19, 2021 at 12:36 PM Kamil Paral <kparal(a)redhat.com&gt; wrote:

>  On Thu, Feb 18, 2021 at 8:37 PM Brandon Nielsen
> <nielsenb(a)jetfuse.net&gt;
>  wrote:
>
> > Mumble supports both local and server loopback. Additionally the initial
> > setup wizard is probably a good indicator if devices are working
> > correctly. Unfortunately I don't know of a good publicly available
> > testing server.
> >
>
>  We already have local recording use case covered. The point of the new
>  testcase is to test widely used teleconferencing solutions (most of them
>  proprietary), in browsers and specialized apps, because their functionality
>  has been vitaly important for a lot of people in the past year and probably
>  will continue being so for some time.
>
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Sumantro Mukherjee]

On Fri, Feb 19, 2021 at 7:23 PM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:

>  The current version of the test cases for Fedora Audio Test Day are
> here:
>
>     - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_PipeWire_default
>     - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_PipeWire_CLI
>     - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_ALSA_backend
>     -
>     https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Selected_Applications...
>     -
>     https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Pavucontrol_Basics
>     -
>     https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Pavucontrol_Recording
>     -
>     https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Pavucontrol_Mixing
>     -
>     https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Pavucontrol_Add_Remove
>     - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Jack_Applications
>     - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Jack_Midi_Routing
>     - https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Bluetooth_Devices
>     -
>     https://fedoraproject.org/wiki/QA:Testcase_PipeWire_Video_Conferencing
>
>  Please, if you feel like you would like to add something to them, let me
>  know as soon as possible. Otherwise, I will take them as finished and will
>  proceed with the next steps towards the real Audio Test Day.
>
>  Have a nice time.
>
>  
The testcases to me look good, lets fix a date for the test day!!
-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

[Lukas Ruzicka]

>  The testcases to me look good, lets fix a date for the test day!!
>  
Sudhir suggested to have two Fedora Audio Test Days.
One should be as soon as possible, the other could be later in the cycle,
but definitely soon enough to enable fixing of possible issues.

Lukas




>  --
>  //sumantro
>  Fedora QE
>  TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Sumantro Mukherjee]

On Fri, Feb 19, 2021 at 9:24 PM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:
> >
> >
> >
> > The testcases to me look good, lets fix a date for the test day!!
>
>
>  Sudhir suggested to have two Fedora Audio Test Days.
>  One should be as soon as possible, the other could be later in the cycle, but definitely
> soon enough to enable fixing of possible issues.
>
>  Lukas 
How about next week or 01 or 02 march?


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED

[Joseph Pesco]

Is there some value in running the test cases in a vm before switching to bare metal? I
thought
I'd do a dry run in a vm to collect all the bits and pieces.

Joe

[Lukas Ruzicka]

Some of them can be run in a VM for sure, but you might run into unknown
waters when it comes to using USB external sound cards and some kind of
application sound routing, because you might not be able to simulate that
in the VM, where the sound device is just a bridge to the real one on the
hardware.
The testcases are therefore practical and bare-metal oriented.

On Mon, Feb 22, 2021 at 7:58 AM Joseph Pesco <information(a)josephpesco.info&gt;
wrote:

>  Is there some value in running the test cases in a vm before
> switching to
>  bare metal? I thought
>  I'd do a dry run in a vm to collect all the bits and pieces.
>
>  Joe
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Frantisek Zatloukal]

On Mon, Feb 22, 2021 at 10:43 AM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:

>  Some of them can be run in a VM for sure, but you might run into
> unknown
>  waters when it comes to using USB external sound cards and some kind of
>  application sound routing, because you might not be able to simulate that
>  in the VM, where the sound device is just a bridge to the real one on the
>  hardware.
>  The testcases are therefore practical and bare-metal oriented.
>
>  
You can set up usb passthrough through virt-manager or VirtualBox. After
you do that, the guest gains complete control of that usb device and it
should work/behave like it wasn't even in a vm.

You can get there through "Show virtual hardware details", "Add
Hardware",
"USB Host Device", then choose a device you wish to hand of to the guest.
Beware that the selected device won't be available on host for use while
the vm is up and running.

-- 

Best regards / S pozdravem,

František Zatloukal
Quality Engineer
Red Hat

[Lukas Ruzicka]

>  You can set up usb passthrough through virt-manager or VirtualBox.
> After
>  you do that, the guest gains complete control of that usb device and it
>  should work/behave like it wasn't even in a vm.
>
>  You can get there through "Show virtual hardware details", "Add
> Hardware",
>  "USB Host Device", then choose a device you wish to hand of to the guest.
>  Beware that the selected device won't be available on host for use while
>  the vm is up and running.
>  
Thanks, I will try to see if that is possible.

:)



>  --
>
>  Best regards / S pozdravem,
>
>  František Zatloukal
>  Quality Engineer
>  Red Hat
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Lukas Ruzicka]

>  You can set up usb passthrough through virt-manager or VirtualBox. After
>  you do that, the guest gains complete control of that usb device and it
>  should work/behave like it wasn't even in a vm.
>  
I can confirm that you can use USB Passthrough to send the USB sound cards
to the Virtual Machine which then can use them without limitations. This is
also valid for MIDI USB controllers.

I think that with using the USB Passthrough strategy, the PipeWire could be
also tested on VMs.

I will update the test cases.



>  You can get there through "Show virtual hardware details", "Add
> Hardware",
>  "USB Host Device", then choose a device you wish to hand of to the guest.
>  Beware that the selected device won't be available on host for use while
>  the vm is up and running.
>
>  --
>
>  Best regards / S pozdravem,
>
>  František Zatloukal
>  Quality Engineer
>  Red Hat
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

-- 
 已通过Tutanota 安全发送，立即注册您的加密无广告邮箱！ 
 https://tutanota.com


2021年2月23日 07:08 来自 lruzicka(a)redhat.com:

> >
> > You can set up usb passthrough through virt-manager or VirtualBox. After you do that,
> the guest gains complete control of that usb device and it should work/behave like it
> wasn't even in a vm. 
> >
>
>  I can confirm that you can use USB Passthrough to send the USB sound cards to the Virtual
> Machine which then can use them without limitations. This is also valid for MIDI USB
> controllers.
>  I think that with using the USB Passthrough strategy, the PipeWire could be also tested
> on VMs.
>
>  I will update the test cases.
>
>   
>
> >
> > You can get there through "Show virtual hardware details", "Add
> Hardware", "USB Host Device", then choose a device you wish to hand of to
> the guest. Beware that the selected device won't be available on host for use while
> the vm is up and running.
> >
> > -- 
> >
> > Best regards / S pozdravem,
> >
> > František Zatloukal
> > Quality >> Engineer
> > Red Hat
> > _______________________________________________
> >  test mailing list -- >> test(a)lists.fedoraproject.org
> >  To unsubscribe send an email to >> test-leave(a)lists.fedoraproject.org
> >  Fedora Code of Conduct: >>
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> >  List Guidelines: >> https://fedoraproject.org/wiki/Mailing_list_guidelines
> >  List Archives: >>
> https://lists.fedoraproject.org/archives/list/[e-mail]
> >  Do not reply to spam on the list, report it: >>
> https://pagure.io/fedora-infrastructure
> >
>
>
>  -- 
>
>  Lukáš>  > Růžička
>
>
>  FEDORA QE> , > RHCE
>
>
>  Red Hat  <https://www.redhat.com>
>
>
>  Purkyňova 115
>
>
>  612 45 Brno - Královo Pole
>
>
>  lruzicka(a)redhat.com&gt;    
>
>
>  TRIED>  > AND PERSONALLY>  > TESTED> , ERGO>  > TRUSTED> .
> <https://redhat.com/trusted>
>  


yeah, Thanks...... but this email seams to be strange...

For I didn't ask anything about USB Passthrough or GPU passthrough,I made it work a
long times ago, and I wrote my email to apply to join the QA group for contribution...

Anything wrong?

[Lukas Ruzicka]

Hello Jetsaman,

this has been the first time I have seen you in this thread, so I am not
sure who you are. I tried to answer to Joseph Pesco why the tests were
designed for bare-metal. Now it turns out, they can be performed without
issues on VMs, too.

If you are not Joseph Pesco, I believe that you have misread the messages
in the list. Your joining the QA group is very needed and welcome, but it
is not the topic of this thread, so please should you need more information
on how to join the QA, please let me know in a different conversation.

Thank you.
Lukas



On Tue, Feb 23, 2021 at 1:50 PM jetsaman--- via test <
test(a)lists.fedoraproject.org&gt; wrote:

>  --
>  已通过Tutanota 安全发送，立即注册您的加密无广告邮箱！
>  https://tutanota.com
>
>
>  2021年2月23日 07:08 来自 lruzicka(a)redhat.com:
>
>
>  You can set up usb passthrough through virt-manager or VirtualBox. After
>  you do that, the guest gains complete control of that usb device and it
>  should work/behave like it wasn't even in a vm.
>
>
>  I can confirm that you can use USB Passthrough to send the USB sound cards
>  to the Virtual Machine which then can use them without limitations. This is
>  also valid for MIDI USB controllers.
>
>  I think that with using the USB Passthrough strategy, the PipeWire could
>  be also tested on VMs.
>
>  I will update the test cases.
>
>
>
>
>  You can get there through "Show virtual hardware details", "Add
> Hardware",
>  "USB Host Device", then choose a device you wish to hand of to the guest.
>  Beware that the selected device won't be available on host for use while
>  the vm is up and running.
>
>  --
>
>  Best regards / S pozdravem,
>
>  František Zatloukal
>  Quality Engineer
>  Red Hat
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>
>
>
>  --
>
>  Lukáš Růžička
>
>  FEDORA QE, RHCE
>
>  Red Hat
>  <https://www.redhat.com>
>
>  Purkyňova 115
>
>  612 45 Brno - Královo Pole
>
>  lruzicka(a)redhat.com
>
>  TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>
>
>
>
>
>  yeah, Thanks...... but this email seams to be strange...
>
>  For I didn't ask anything about USB Passthrough or GPU passthrough,I made
>  it work a long times ago, and I wrote my email to apply to join the QA
>  group for contribution...
>
>  Anything wrong?
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>  

-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>

[Sumantro Mukherjee]

On Tue, Feb 23, 2021 at 6:20 PM jetsaman--- via test <
test(a)lists.fedoraproject.org&gt; wrote:

>  --
>  已通过Tutanota 安全发送，立即注册您的加密无广告邮箱！
>  https://tutanota.com
>
>
>  2021年2月23日 07:08 来自 lruzicka(a)redhat.com:
>
>
>  You can set up usb passthrough through virt-manager or VirtualBox. After
>  you do that, the guest gains complete control of that usb device and it
>  should work/behave like it wasn't even in a vm.
>
>
>  I can confirm that you can use USB Passthrough to send the USB sound cards
>  to the Virtual Machine which then can use them without limitations. This is
>  also valid for MIDI USB controllers.
>
>  I think that with using the USB Passthrough strategy, the PipeWire could
>  be also tested on VMs.
>
>  I will update the test cases.
>
>
>
>
>  You can get there through "Show virtual hardware details", "Add
> Hardware",
>  "USB Host Device", then choose a device you wish to hand of to the guest.
>  Beware that the selected device won't be available on host for use while
>  the vm is up and running.
>
>  --
>
>  Best regards / S pozdravem,
>
>  František Zatloukal
>  Quality Engineer
>  Red Hat
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it:
>  https://pagure.io/fedora-infrastructure
>
>
>
>  --
>
>  Lukáš Růžička
>
>  FEDORA QE, RHCE
>
>  Red Hat
>  <https://www.redhat.com>
>
>  Purkyňova 115
>
>  612 45 Brno - Královo Pole
>
>  lruzicka(a)redhat.com
>
>  TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>
>
>
>
>
>  yeah, Thanks...... but this email seams to be strange...
>
>  For I didn't ask anything about USB Passthrough or GPU passthrough,I made
>  it work a long times ago, and I wrote my email to apply to join the QA
>  group for contribution...
>
>  Anything wrong?
>  
Hey jetsaman,

It indeed is the same list, where you might have dropped your first email
when you expressed your willingness to contribute. This is also the same
list we (Fedora QA) team
use to communicate changes for release criteria, gather community review
for test cases, talk about bugs, and a bunch of activities related to
day-to-day testing. If I can help you get
started with testing, feel free to ping me off-list!

-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

[Kamil Paral]

On Tue, Feb 23, 2021 at 1:12 PM Lukas Ruzicka <lruzicka(a)redhat.com&gt; wrote:

> > You can set up usb passthrough through virt-manager or VirtualBox. After
> > you do that, the guest gains complete control of that usb device and it
> > should work/behave like it wasn't even in a vm.
> >
>
>  I can confirm that you can use USB Passthrough to send the USB sound cards
>  to the Virtual Machine which then can use them without limitations. This is
>  also valid for MIDI USB controllers.
>
>  I think that with using the USB Passthrough strategy, the PipeWire could
>  be also tested on VMs.
>
>  I will update the test cases.
>  
I would be careful with considering such test cases as passed and on par
with bare metal tests. When it is routed to a VM, it still goes through the
host USB stack. Unexpected things can happen. We might mention it as a
testing option, sure, but we should also ask people to append a note saying
"usb-passthrough to a VM" or similar to their result submissions, so that
we can distinguish them.