----- Original Message -----
From: "Luke Van Dervoort" <vanluke64(a)gmail.com>
To: test(a)lists.fedoraproject.org
Sent: Sunday, November 26, 2017 3:52:24 AM
Subject: Self Introduction
Hello from sunny California
I just joined the test list and hope to start testing Fedora soon. My name is
Luke Van Dervoort and I have been using Linux at home since the late 90's,
so I at least know the basics. The first linux I got stable on my computer
was slackware and since then have bounced around several distributions. I
currently work doing tech support for a linux based security software and am
looking to help here.
My IRC handle is Dragon 64.
Looking forward to talking with some of you here.
Happy Holidays from the states!
--
Luke Van Dervoort
Life is short, Love someone ...
LLAP
_______________________________________________
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
Hey Luke,
First of all, Welcome and thanks for showing your interest in Fedora QA. It will be
awesome if you can start off by sending an group request for 'qa'.
You can start off by testing updates in [
http://bodhi.fedoraproject.org/] for 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://fedoraproject.org/wiki/Taskotron]
and Open
QA[https://fedoraproject.org/wiki/OpenQA].
https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_28_Rawhide_20171124.n....
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
https://bugzilla.redhat.com/
We are currently doing our best to test F27 Modular Server, it will be great if you start
off
with release validation.
You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:
https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Branched_20...
The individual test result pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Branched_20...
https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Branched_20...
https://fedoraproject.org/wiki/Test_Results:Fedora_Modular_27_Branched_20...
P.S. There is a test day coming on 2017-11-30 , it's Kernel 4.14
[
https://fedoraproject.org/wiki/Test_Day:2017-11-30_Kernel_4.14_Test_Day]
Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
Thanks
//sumantrom