Re: New member introduction

[Sumantro Mukherjee <sumukher@xxxxxxxxxx>]

Hey Uditanshu,

On Wed, Apr 17, 2019 at 8:12 PM Uditanshu Kumar <uditanshu1990@xxxxxxxxx> wrote:

hi team,

This is Uditanshu Kumar , I'm 19 years old . Currently pursuing Btech in Information Technology from Haldia Institute of technology . Presently working in the field of Linux and high end technologies like Machine learning , Big Data , Cloud computing and Devops tools like Ansible. I want to work with QA team and packaging team 

Thanks and regards,

Uditanshu Kumar

_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you have, I have sponsored you by now. If you haven’t then please apply and send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 28, Fedora 29, and Fedora 30. 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 30 Branched 20190415.n.2), 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_30_Branched_20190415.n.2_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

--

//sumantro

Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED

_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx