From Fedora Project Wiki

Line 26: Line 26:


* A virtual machine or a bare metal machine
* A virtual machine or a bare metal machine
* An installation of Fedora 34 (any Desktop Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest [https://www.happyassassin.net/nightlies.html nightly image].
* An installation of Fedora 34 (any Desktop Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest [https://openqa.fedoraproject.org/nightlies.html nightly image].


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

Revision as of 09:14, 8 April 2021

Audio Test Day

Date 2021-04-09
Time all day

Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

This Test Day will focus on Pipewire by Default

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

You can chat with us on IRC. See the infobox on top of the page to learn the right IRC channel.

Prerequisite for Test Day

  • A virtual machine or a bare metal machine
  • An installation of Fedora 34 (any Desktop Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest nightly image.

How to test?

Visit the results page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.

Reporting bugs

All bugs should be reported into Bugzilla, in most cases against the Pipewire component. If you are unsure about exactly how to file the report or what other information to include, just ask us on IRC (see instructions above).

Test Results

The test results will be reported back here after the test day ends.