On Thu, Feb 18, 2021 at 2:58 PM Lukas Ruzicka <lruzicka@xxxxxxxxxx> 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: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 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.
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
