----- Original Message ----- > From: "Bryan Teague" <bteague003@xxxxxxxxx> > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Monday, August 8, 2016 5:27:35 AM > Subject: Introduction > > Good evening - > > > My name is Bryan Teague, and I’m grateful to have this opportunity to > participate within the QA development of Fedora. > > I am currently finishing up an AAS degree in Computer Programming. > I’ve had a great deal of experience with coding for the dark side > (Microsoft platforms such as C#, VB, utilizing Visual Studio). Was > introduced to Linux recently, and just love this OS. Along with > learning C and kernel development, I am interested in understanding > the different facets of Fedora. Thanks again. Hey Bryan Welcome to Fedora QA! You can start by reading [https://fedoraproject.org/wiki/QA/Join] Once you are done, 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 nightly, you can run test cases which are mentioned [1] and submit your results in the test matrix. Note that each of the test cases[2] 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 [3] 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 You can also do update-testing, 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 [4]. You can also, use fedora-easy-karma for giving out feedbacks. [1]https://fedoraproject.org/wiki/Test_Results:Fedora_25_Rawhide_20160719.n.0_Summary?rd=Test_Results:Current_Summary [2]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [3]https://bugzilla.redhat.com/ [4]https://fedoraproject.org/wiki/QA:Updates_Testing Since , you are into development it will be easy for you to start with OpenQA and Taskotron. Both of these are automated testing tools and you can contribute by writing test cases. Taskotron setting up and installation can be found here [https://bitbucket.org/fedoraqa/libtaskotron] OpenQA , Installation and setting up resources can be found here [https://bitbucket.org/rajcze/openqa_fedora_tools] Should you have any question, you reach out to me directly or in the list! -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
