----- Original Message ----- > From: "Dhanesh B. Sabane" <dhanesh95@xxxxxxxxxxx> > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Thursday, May 25, 2017 11:09:43 PM > Subject: [Self-Introduction] Dhanesh B. Sabane (dhanesh95) > > Aloha team! > > My name is Dhanesh B. Sabane and I'm from Maharashtra, India. I've been a > Fedora contributor since May 2016 and I started off with CommOps. Gradually > I made my way through Marketing, Join SIG and RPM Packaging. > > As a software engineer, I've always focused on improving my development > skills which means QA is not particularly my forte. But, I always wanted to > learn how to efficiently test/debug programs. That is the only way to ensure > that your software is worthy enough. > > With my current attempts to improve my testing skills, I think joining this > team will facilitate the whole learning process. I'll also get some badges > and cookies too! That's never bad. :P > > It would be great if someone from the team is available to mentor me and help > me find tasks that I can work on. Looking forward to being an integral part > of this team. > > TL;DR: > > Name: Dhanesh B. Sabane > Location, Timezone: Maharashtra, India UTC+5:30 > FAS username: dhanesh95 > IRC Nick: dhanesh95 > > -- > Dhanesh B. Sabane [dhanesh95] > Web : https://dhanesh95.gitlab.io > > > _______________________________________________ > test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx > Hey Dhanesh First of all, Welcome and thanks for showing your interest in Fedora QA. I would like you to apply for QA FAS group. :) You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 24 , Fedora 25 and Fedora 26. 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 alpha (Fedora 26 Branched 20170513), 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]. [1]https://fedoraproject.org/wiki/QA:Updates_Testing [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170513.n.0_Installation [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [4]https://bugzilla.redhat.com/ PS we have a on-boarding call happening , here is a poll link which you can use to vote your preferred timing :https://beta.doodle.com/poll/hz6hcdx79f88g56r#table PPS : I will close this poll by tonight 10pm IST. [For the time being its 3rd June 2017 1400 UTC - 1500 UTC] Thanks //sumantrom _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
