----- Original Message -----
From: "David Wynter" <david.wintour(a)gmail.com>
To: test(a)lists.fedoraproject.org
Sent: Thursday, June 29, 2017 3:11:01 PM
Subject: Self-Introduction
Hi All,
My Name is David and im a Security Architect for a Telco in the UK
I have been using Linux generally in many capacities since i was 13 (30 now)
Tried many different flavours for many different reasons but always seem to
circle back to fedora and find the community inc info the easiest to get
stuck in on.
I have been contributing when i can on QA via bodhi but am keen to do more,
if i can just find some more spare time :) . Im also keen to expand beyond
Bodhi and contribute further so may fire some questions to the more
experienced folk here.
I will try and get more active via IRC also.
FAS: wynter919
IRC: octoray919
PGP:
https://pgp.key-server.io/0x73814AE713A515B7
Many Thanks
David
_______________________________________________
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
Hey David,
First of all, Welcome and thanks for showing your interest in Fedora QA. I would like you
to apply for QA FAS group.
You can start off by testing updates in [
http://bodhi.fedoraproject.org/] for Fedora 24 ,
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 build (Fedora 26 Branched 20170628), 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_26_Branched_20170628...
[
3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[
4]https://bugzilla.redhat.com/
We have a test day coming up tomorrow, which is where we are going to test if everything
upgrades smoothly from F25 to F26. More about the test day can be found
[
https://fedoraproject.org/wiki/Test_Day:2017-06-30_Upgrade_Test_Day].
Thanks
//sumantrom