Thanks Sumantro. Appreciated!
On Jan 30, 2018 10:06, "Sumantro Mukherjee" <sumukher@xxxxxxxxxx> wrote:
----- Original Message -----
> From: "Francis Gesora" <fgesora@xxxxxxxxx>
> To: test@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Monday, January 29, 2018 1:10:15 PM
> Subject: Self introduction: Francis Gesora
>
> Hello,
>
> Great joining the QA / Testing team. I have 9 years experience using Linux ,
> 5 of those as a Fedora and Red Hat. I have extensive knowledge of Linux in
> general and i have specific interest in modular and package testing.
>
> Thanks guys.
>
>
> --
> Regards,
> Francis Gesora.
> IRC: gesora
>
>
> _______________________________________________
> test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to test-leave@lists.fedoraproject.org
>
Hey
Welcome to Fedora QA, I have sponsored your request for qa group. :)
You can start off by testing updates in [http://bodhi.fedoraproject.org/ ] for Fedora 26 and Fedora 27. 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 28 Rawhide 20180126.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 Taskotron [https://fedoraproject.org/wiki/Taskotron ]
and Open QA[https://fedoraproject.org/wiki/OpenQA ].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_28_ Rawhide_20180126.n.0_Summary? rd=Test_Results:Current_ Summary
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_ Live_luc
https://bugzilla.redhat.com/
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
Thanks
//sumantrom
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@lists.fedoraproject.org
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
