----- Original Message ----- > From: "Ludovic Hirlimann" <ludovic@xxxxxxxxxxxxx> > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Friday, September 21, 2018 11:14:06 AM > Subject: Introduction > > Hi, > My name is Ludovic. Paul-Muadib on freenode. I've been using OSS since > 2000ish. I'm emplyed by mozilla as root , before that I was the QA lead for > Thunderbird and for Joost a video startup company. I've used linux on and > off since 1996 (kernel 1.3.88) with slackware/Debian/RHEL/CentOS - I've also > played with things like Tru64, HP-UX and friends. I'm joigning the QA list, > cause I like running the kernel-test and the wiki needs some edits (like > using pyhton3-fedora). I don't have much free time but I have interest in > non x86 hardware, 28mm platisc soldier and photography. I usually sign my > emails (but have not setup this adrees back on a proper email client since > I've reinstalled my machine. > > Ludo > > -- > https://www.hirlimann.net/Ludovic/carnet/ Hey! Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you have, I are sponsored 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 I will be interested in working with you for creating more test cases for Firefox and Thunderbird! Thanks //sumantrom _______________________________________________ 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
