----- Original Message ----- > From: "chagol chana" <chagolchana47@xxxxxxxxx> > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Thursday, November 23, 2017 6:53:59 PM > Subject: Self Introduction > > Hey, > > I am chagolchana, I have been using Fedora linux for last 2 months. I want to > contribute back to the project starting with QA. It will be good if someone > can help me get started. I am good with RTFM as well :) > > > Regards > ~chagolchana > _______________________________________________ > test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx > Hey, First of all, Welcome and thanks for showing your interest in Fedora QA. It will be awesome if you can start off by sending an group request for 'qa'. 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 27 Branched 20171020.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_20171124.n.0_Summary?rd=Test_Results:Current_Summary https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc https://bugzilla.redhat.com/ We are currently doing our best to test F27 Modular Server, it will be great if you start off with release validation. You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Branched_20171123.n.1_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Branched_20171123.n.1_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Branched_20171123.n.1_Base https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Branched_20171123.n.1_Server P.S. There is a test day coming on 2017-11-30 , it's Kernel 4.14 [https://fedoraproject.org/wiki/Test_Day:2017-11-30_Kernel_4.14_Test_Day] 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@xxxxxxxxxxxxxxxxxxxxxxx
