----- Original Message -----
From: "Romeo Asuncion" <rasunci(a)gmail.com>
To: test(a)lists.fedoraproject.org
Sent: Tuesday, September 26, 2017 2:47:04 AM
Subject: Self-introduction
Hi,
A short intro about myself... I've used Linux for a long time but lately not
so much. I've done sysadmin work in Linux and some coding in Perl and Java.
A lot has changed since then. I want to get involved so I decided to try
test-qa. Hopefully I can be of some help.
--
Romeo Asuncion
rasunci(a)gmail.com
_______________________________________________
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
Hey Romeo,
First of all, Welcome and thanks for showing your interest in Fedora QA. Please apply for
qa FAS group sponsorship and let me know off list with your FAS ID!
You can start off by testing updates in [
http://bodhi.fedoraproject.org/] 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 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|<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_27_Branched_20170817...
[
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.
Kernel Test day is tomorrow hope to see you there.
We are currently doing our best to kinda test F27, it will be great if you start off
with release validation.
Thanks
//sumantrom