----- Original Message -----
> From: "Jesse James Whitson" <blazefade@xxxxxxxxxxxxxxxxx>
> To: test@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Wednesday, August 10, 2016 2:58:20 AM
> Subject: Self-Introduction: Jesse Whitson
>
> User name blazefade
>
> Here to Join Quality Assurance Team
>
> First introduced to red hat in 2004 when volunteering at a custom computer
> store
> 2009 had such a hated passion for windows vista I became a permanent Linux
> fan first starting with Ubuntu
> 2010 I became a back track user and learned more about other distros
> including Debian, crunchbang, arch Linux, and Slackware. After spending a
> few years trying most of the popular ones I eventually settled with quad
> booting my system with Kali Linux, arch Linux, Windows, and Sabayon. Arch
> was my main Distro as I enjoyed keeping things simple, to the point and
> minimal.
>
> In 2015 I have merged to fedora as my main Distro with Windows only for bios
> updates.I switch to Fedora for many great reasons. CentOS and RedHat are
> commonly used in businesses and to show I know how to navigate around and
> use a terminal is something I need to prove to people professionally. I love
> fedoras group system as the security and eclipse programs are some of my
> favorite with fedora being the only Distro to make eclipse operate correctly
> by default on Linux. Desktop environments are not reconfigured or modified
> but shown as the developer has intended it's design to be.
> CVE shows fedora as a great building code correctly the first time and I want
> to be part of this awesome group.
>
> I am here to join the quality assurance team.
Hey and Welcome Jesse!
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 nightly, 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_20160807.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
Should you have any question, you reach out to me directly or in the list!
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
