You're welcome Varun Singh...
On Wed, Dec 14, 2016 at 6:27 PM, Sumantro Mukherjee <sumukher@xxxxxxxxxx> wrote:
> ______________________________
----- Original Message -----
> From: "Varun Singh" <ervarun95@xxxxxxxxx>
> To: test@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Tuesday, December 13, 2016 1:56:19 PM
> Subject: Introduction
>
> Hello everyone,
> I'm Varun, a Computer Science Undergrad working around with Linux for 1.5+
> years. So far I've used CentOS, RHEL 7, Ubuntu, Manjaro, Fedora, Zorin,
> Mint, and Kali. Currently, I'm using Fedora 25. I joined the Fedora Project
> as I'm enthusiastic about open source and I wish to contribute my efforts to
> this community.
>
> I'm a blogger. I create and write articles for Technotification and been
> doing so since Dec '13. I have intermediate experience with System
> Administration on Red Hat based systems, Adobe Photoshop and Adobe
> Illustrator.
>
> I've created the account at FAS and I look forward to contributing to Fedora
> QA, content writing and design.
>
> Thanks and regards,
> Varun Singh.
>
_________________ Hey Varun
> test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to test-leave@lists.fedoraproject.org
>
first of all welcome to Fedora QA. I have sponsored your request to FAS group. You can start off by testing updates in [http://bodhi.fedoraproject.org/ ] for Fedora 24 and Fedora 25 . 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 Rawhide (Fedora_26_Rawhide_20161210.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
[1]https://fedoraproject.org/wiki/QA:Updates_Testing
[2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_ Rawhide_20161210.n.0_Summary? rd=Test_Results:Current_ Summary
[3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_ Live_luc
[4]https://bugzilla.redhat.com/
P.S. I have replied you off list for the contribution pathways for Design and Writing.
Thanks
Sumantro
_______________________________________________
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
