----- Original Message ----- > From: "Diego Damián" <diegoaarondv@xxxxxxxxx> > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Friday, June 29, 2018 4:48:33 PM > Subject: Introduction - Diego Damian > > Hi guys, > > My name is Diego Aaron, I'm 26 years old and live at Lima Perú. I have > started using Linux for a couple of months now, since I am preparing for the > LPIC I certification. > I am also learning about Java programming and application testing in a > personal way. I have more experience in configuring Cisco network equipment. > I'm very glad to join at Fedora QA Team. I have working with Red Hat Linux in > my work since six months ago. So, let's time to > contribute with the project. > > So, thanks a lot for some people who accepted me at Fedora Project. > > At my signature I'm sending my contacts fell free if anyone want to contact > me. > > Bye > -- > Att. > > Diego Damian > ------------------------- > Contacts > email: diegoaarondv@xxxxxxxxx > irc nickname: diegoaaron909 Hey Diego, Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you have, I have sponsored you by now. You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 27, Fedora 28, and Fedora 29. 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 29 Branched 20180923), 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_29_Branched_20180923.n.0_Summary?rd=Test_Results:Current_Summary https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc 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 Thanks //sumantro _______________________________________________ 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
