----- Original Message ----- > From: "Yves (Opvelp)" <yves.haegeman@xxxxxxxxx> > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Saturday, October 15, 2016 6:13:01 PM > Subject: Self-introduction: Yves Haegeman > > Hi Folks, > > Via this way , I would like to introduce myself briefly. > > My name is "Yves Haegeman". > I am living in Belgium and I'm 54 years old. > My first (professional) contact with UNIX-like systems was in 1987 (HP-UX). > Since that moment I have not hesitated 1 second , staying for a long time in > this "highly challenging & interesting" Unix/Linux domain for several > projects & reasons. > > - Database related : Oracle,DB2 LUW,MySQL,MaxDB > - ERP related : Oracle eBusiness & SAP > - Legacy applications : Oracle development with forms,reports,pl/sql > - Process computing (Chemistry) : C, C++ , Pro-C > > I also try to combine the above listed in order to build a strong “helicopter > view” (e.g. tackling performance & architectural challenges). > > Many thanks to accept my membership to this fedora test community. > > Below you will find my coordinates in case someone wants to contact me. > > Bye, > Yves Haegeman > Kapelstraat 20 > 3360 Opvelp > M: +32 473 96.72.61 > yves.haegeman@xxxxxxxxx > https://be.linkedin.com/in/yvesh/ > > PS : I'm currently running Fedora 24 & testing Fedora 25 Beta on a couple of > mini-servers (all purpose). Hey Yves Haegeman, First of all , welcome to fedora qa team. Send an request to the FAS group and I will sponsor you ! 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, 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_Branched_20161013.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 Thanks Sumantro _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
