Thanks for the info sumantron. Regards. On Mon, 2017-10-23 at 00:02 -0400, Sumantro Mukherjee wrote: > > ----- Original Message ----- > > From: "Shaun A" <thebeardedhermit@xxxxxxxxxxx> > > To: test@xxxxxxxxxxxxxxxxxxxxxxx > > Sent: Monday, October 23, 2017 9:18:38 AM > > Subject: Self-Introduction: Shaun Assam > > > > Hello fellow Fedorians, my name is Shaun Assam and I'd like to join > > the > > QA team. I've been providing feedback and karma for packages in > > fedora- > > testing and believe my participation in QA would allow a greater > > outlet > > to collaborate with the community. > > > > I feel my experience in Technical Support can provide some helpful > > feedback from the perspective of the average end-user and deliver > > some > > insightful ideas for the community's consideration. I also have > > experience working on technical documentation and in my spare time > > I > > research and analyze the quality of digital audio to enhance the > > joy of > > music (using Fedora as the OS for my digital jukebox of course.) > > > > I thank you for your consideration and look forward to working more > > closely with a community dedicated to making Fedora the best Linux > > distribution. > > > > Regards, > > > > Shaun Assam > > IRC: sassam > > _______________________________________________ > > test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > > Hey Shaun, > > > First of all, Welcome and thanks for showing your interest in Fedora > QA. I have already sponsored your request for qa group. > > You can start off by testing updates in [http://bodhi.fedoraproject.o > rg/] for Fedora 25 Fedora 26 and Fedora 27. 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 27 > Branched 20171020.n.0 ), 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://fedorapro > ject.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_27_Branched_201 > 71020.n.0_Summary?rd=Test_Results:Current_Summary > [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc > [4]https://bugzilla.redhat.com/ > > > > We are currently doing our best to test F27, it will be great if you > start off > with release validation. > > Feel free to ping us on IRC if you need any help. :) > > > Thanks > //sumantrom > _______________________________________________ > test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
