----- sudeshna sur <sudeshnas...@gmail.com> wrote:
> Hi all,
> 
> My name is Sudeshna Sur. I am interested in contributing to fedora project
> in qa and getting involved in it. I am basically a newbie in using linux
> but want to enhance my skills by learning and contributing for the same.
> 
> I have completed my grads in 2016 on Computer Science. My area of interests
> include data mining, data analytics.
> 
> Looking forward to contribute in fedora QA.
> 
> Thanks
> Sudeshna Sur

Hey Sudeshna,

First of all, Welcome and thanks for showing your interest in Fedora QA. Please 
apply for qa FAS group sponsorship and let me know off list with your FAS ID!

You can start off by testing updates in [http://bodhi.fedoraproject.org/] for 
Fedora 25 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 27 Beta 1.5), 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].



[1]https://fedoraproject.org/wiki/QA:Updates_Testing
[2]https://fedoraproject.org/wiki/Test_Results:Fedora_27_Beta_1.5_Summary?rd=Test_Results:Current_Summary
[3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4]https://bugzilla.redhat.com/

We have a test day coming up for testing major changes in F27. You can find the 
announcements on @test-announce list and community blog.

Upgrade test day is on 2017-10-11

We are currently doing our best to kinda test F27, it will be great if you 
start off
with release validation.

Feel free to get in touch , whenever you get stuck :)


Thanks
//sumantrom
_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Reply via email to