Hello bd6627! Welcome to Fedora QA, I have sponsored your QA group request. You can start off by testing updates in < http://bodhi.fedoraproject.org/> for Fedora 31, Fedora 32, and Fedora 33 (Rawhide). Update testing is where a tester tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to bodhi.fedoraproject.org where you can sort the packages with Fedora Releases and tags with "pending" & "testing". You can read much about update testing here [1]. You can also use the command fedora-easy-karma from your terminal for giving out feedbacks. You can start with Release Validation testing. In Release Validation all you need to do is to check the nightly/TC/RC against certain criteria. For example, let's take the latest compose (Fedora 33 Rawhide 20200804.n.0), you can run the test cases which are mentioned here [2] and submit your results in the test matrix. Note that each of the test cases[3] will have "How to test" section which will have the steps (to be executed sequentially) and if the results match with the expected results you can mark it as pass by editing the wiki page {{result|PASS|<fas_username>}}. Always make sure to check for "Associated release criterion" which can be found on the top of test case page, if your test case fails you can mark it fail by editing the wiki page {{result|FAIL|<fas_username>}} and file a bug at RHBZ [4] under Fedora. You can always find the ‘current’ validation pages using these addresses: <https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test> <https://fedoraproject.org/wiki/Test_Results:Current_Base_Test> <https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test> <https://fedoraproject.org/wiki/Test_Results:Current_Server_Test> <https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test> Keep an eye to Fedora Test Days, they will be announced here and usually in the Community Blog or on the Magazine. They are events useful to test some new feature or big change, and they organized by the QA Team in collaboration with some other team. For Automation, you can start looking at Open QA < https://fedoraproject.org/wiki/OpenQA> its maintained by Adamw. Other Blogs to read: - < https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/ > - < https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-2/ > - < https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-3/ > [1] <https://fedoraproject.org/wiki/QA:Updates_Testing> [2] < https://fedoraproject.org/wiki/Test_Results:Fedora_33_Rawhide_20200731.n.0_Summary > [3] i.e. <https://fedoraproject.org/wiki/QA:Testcase_USB_fmw> [4] <https://bugzilla.redhat.com/> If you still have questions, feel free to reach out on the #fedora-qa IRC or directly via email (or in the Telegram group https://t.me/fedora_qa)! Ciao, A. _______________________________________________ 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
