Thank you for sponsoring me. I'm on vacation now. Can't wait to contribute
when I get back
On Sep 3, 2017 09:08, "Sumantro Mukherjee" <sumuk...@redhat.com> wrote:
>
>
> - Original Message -----
> > From: "sean bailey" <sean.bai...@gmail.com>
> > To: test@lists.fedoraproject.org
> > Sent: Friday, September 1, 2017 8:31:44 PM
> > Subject: Introduction: Sean Bailey
> >
> > Hello everyone!
> >
> > I have been using Linux since I was in my teens. I have recently found
> myself
> > running out of things to do with Linux so I figured one way I could stay
> > busy would be to contribute to the Feodor project.
> >
> > I work with RHEL based Linux daily in my job linux support. I also use
> Fedora
> > on my home computer.
> >
> > Here are some of my contact information:
> >
> > IRC: Ironusmaidenus on freenode
> > Discord: ironusmaidenus
> >
> > I look forward contributing to the project,
> >
> > Sean
> >
> > ___
> > test mailing list -- test@lists.fedoraproject.org
> > To unsubscribe send an email to test-le...@lists.fedoraproject.org
> >
> Hey Sean,
> First of all, Welcome and thanks for showing your interest in Fedora QA.
> I've approved your request!
>
> You can start off by testing updates in [http://bodhi.fedoraproject.org/]
> for 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 compose (Fedora 27 Branched 20170817.n.3),
> 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|}} . 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|}} 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_27_
> Branched_20170817.n.3_Summary
> [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
> [4]https://bugzilla.redhat.com/
>
> We have a test day coming up for testing major changes in F27. You can
> find the announcements on @test-announce list and community blog.
>
> Thanks
> //sumantrom
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
