Re: Self-introduction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- Alessio Ciregia <alciregi@xxxxxxxxx> wrote:
> Hello. My name is Alessio. I'm an unpretentious sysadmin who works in an Italian hospital. My Linux experience started in 1999 with Red Hat Linux 6, but I have still a bunch of stuff to learn and to understand: first of all the English language :-)
> I would like to contribute in some way to the QA team. Right now I'm reading the wiki. I hope I can be of help in the near future.
> 
> Ciao.
> _______________________________________________
> 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. To get started you need a FAS account and your FAS should be sponsored. You can create your FAS account (assuming you don't have one) https://admin.fedoraproject.org/accounts/.
You will require a membership to Fedora QA group to proceed and you can get apply for 'qa' in here [https://admin.fedoraproject.org/accounts/group/list/]   

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 branched (Fedora 26 Branched 20170307.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_Branched_20170307.n.0_Summary?rd=Test_Results:Current_Summary
[3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4]https://bugzilla.redhat.com/

Thanks 
Sumantrom
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux