On Tue, 2020-09-01 at 12:23 -0500, Klein Kravis wrote: > Hello QA team. I'm just saying hello before I get to work on testing > the new F33 nighty. I've been a Fedora user for about 6 months now > (Ubuntu for 2 years before) Before I started contributing here I > worked on docs for the Gnome foundation. I'm excited to get to work! > I hope to see y'all on IRC sometime. Hello Klein, and welcome. I've sponsored your apllication to the QA Fas group right now. It is a good time to join the QA team. :-) As you know Fedora 33 is on its way to be released in less than a couple of months. [1] So it is always a good thing that people perform as many test as possible before the release. And as you may already know, this week is the Fedora Test Week for Btrfs [2] Test days schedule can be found on the fedocal https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day 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 nominated for testing (Fedora 33 Branched 20200822.n.0), you can run test cases which are mentioned [3] and submit your results in the test matrix. Note that each of the test cases[4] 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 [5] 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 You can start off by testing updates in [ http://bodhi.fedoraproject.org/] for Fedora 31, Fedora 32, and Fedora 33. 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 viz "pending" & "testing". You can read much about update testing here [6]. You can also, use fedora-easy-karma for giving out feedbacks. 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://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://communityblog.fedoraproject.org/contribute-at-the-fedora-test-week-for-btrfs/ [3] https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200822.n.0_Summary?rd=Test_Results:Current_Summary [4] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [5] https://bugzilla.redhat.com/ [6] https://fedoraproject.org/wiki/QA:Updates_Testing Feel free to ping us on IRC if you need any help #fedora-qa@freenode (or on Telegram 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
