Hi all,_______________________________________________Good day!I'm Melvin George, with an eye for details... and faults.I'm from Bangalore, India. Presently pursuing opportunities in product management with interest in defining Quality and UAT for products.I started using OpenSuse about 8 years ago. But, about 5 years ago is when I used the black and white screen of CentOS extensively, while I owned the backend systems at a mobile app startup. It would give me the pleasure to realise products that care for the user and adapt to user's needs as a caring human would.Thanks a lot for your time. Looking forward to knowing about each of you.Until then, let's find some bugs, redefine quality standards and make the coolest sidekick OS for users around the world!--
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-leave@lists.fedoraproject.org
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@lists.fedoraproject.org
Hey Melvin,
Welcome to Fedora QA, It will be great if you apply for qa FAS group. Thanks Adamw for sponsoring!
You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 29, Fedora 30 and 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 viz “pending” & “testing”. You can read much about update testing here [1]. You can also, use fedora-easy-karma 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 31 Rawhide 20190601.n.0), you can run test cases which are mentioned [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
For Automation, you can start looking at Open QA[https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.
[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2] https://fedoraproject.org/wiki/Test_Results:Fedora_31_Rawhide_20190601.n.0_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
We have test days coming happening now which is a nice place to start, please stay tuned to the @test list and help us testing!
The current test day can be found on https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day