> I'd say an
> easy-to-read guide in "how can I help?" section on our wiki could be more
> visible.
>
As one of the newbies (joined in March 2018) I will wholeheartedly say
Great Idea! I'm still trying to figure this out. The only things the
wiki seems to point to are testing updates and running the standard test
cases. I certainly understand these are both important, but Coconut is
running most of the tests these days leaving apparently little a for a
human to do.
I need to highlight something here. It's the very opposite. OpenQA (coconut) does very little testing actually, just the basics. It is a large portion of our test matrices, that's correct, but it's just a tiny bit of all the combinations and installation+system workflows you can perform. Following the test cases is of course helpful, but the most beneficial thing you can do is just to play with the installer/system, explore, try whether this or that works. That has a much better chance of finding bugs than those beaten paths in the test cases. Test cases are just for the basics, because we can't defined a million test cases for every possible button click. There are so many things out there that can be tested.
Every time you find a bug, please report it, propose it as a blocker if it is very severe, or perhaps discuss it or notify us on the test list. If there isn't a test case for it and a wiki box to fill out, that doesn't matter at all.
We probably do a very bad job communicating this :/
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
