Scratch that previous query - I eventually figured Google would know the answer - low and behold it did. Please excuse my laziness this evening.
Thanks,
Jack
Sent: Monday, September 26, 2016 at 9:03 PM
From: "Jack Winch" <jwinch@xxxxxxxxxxxx>
To: test@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Self-introduction: Jack Winch (jwinch)
From: "Jack Winch" <jwinch@xxxxxxxxxxxx>
To: test@xxxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Self-introduction: Jack Winch (jwinch)
Hi Sumantro,
Thanks for you warm welcome and words of advice (as well as your group sponsorship). Would you kindly mind pointing me towards a high level view of the development cycle and how each version of the various 'flavours' of the Fedora Core become a part of the six monthly stable releases?
Many Thanks,
Jack
Sent: Monday, September 26, 2016 at 3:39 AM
From: "Sumantro Mukherjee" <sumukher@xxxxxxxxxx>
To: "For testing and quality assurance of Fedora releases" <test@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Self-introduction: Jack Winch (jwinch)
From: "Sumantro Mukherjee" <sumukher@xxxxxxxxxx>
To: "For testing and quality assurance of Fedora releases" <test@xxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Self-introduction: Jack Winch (jwinch)
Hey Jack!
First of all , welcome to fedora qa team. Please consider sending a sponsor request in the qa FAS group.
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 alpha candidate, 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_20160912.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!
Thanks
Sumantro
----- Original Message -----
> From: "Jack Winch" <jwinch@xxxxxxxxxxxx>
> To: test@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Sunday, September 25, 2016 8:48:06 PM
> Subject: Self-introduction: Jack Winch (jwinch)
>
> Hi All,
> My name is Jack and I'm an 18 year old applications engineer, based in the
> UK. I have worked for Rolls-Royce plc for two years now and they are
> sponsoring me through my education as an electrical and electronics engineer
> (later forking me off into software engineering). For the past seven months
> I have been working as a QA tester for a new instructional system - it's
> purpose is to take measurement and test requirements from development
> engineers and produce the required technical instructions/documents/data
> aquisition system configuration files, to allow for the rigging of
> instrumentation on the experimental engine and for the configuration of the
> test data systems. I have also been involved in the comissioning and
> validation of new measurement hardware/data acquisiton system architecture
> for a new test rig being built by RR in Dahlewitz, Germany.
> For those who may be curious, my LinkedIn profile may be found here:
> https://www.linkedin.com/in/jack-winch
> Although I may be young, still a little wet behind the ears and some may say
> 'naive', I am a highly enthusiastic and knowledge hungry individual, who has
> a passion for learning, as well as a passion for being involved with
> inovative projects such as the Fedora project. I have spent a lot of time
> working within the different spins of Fedora (we use Fedora extensively
> within RR) and it would be amazing if you could put my high energy,
> enthusiasm and current technical experience to use, within the QA group.
> I look forward to hearing from some of you and I am eager to help in whatever
> manner you see fit.
> Many Thanks and Kind Regards,
> Jack Winch
>
> _______________________________________________
> test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
>
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
First of all , welcome to fedora qa team. Please consider sending a sponsor request in the qa FAS group.
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 alpha candidate, 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_20160912.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!
Thanks
Sumantro
----- Original Message -----
> From: "Jack Winch" <jwinch@xxxxxxxxxxxx>
> To: test@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Sunday, September 25, 2016 8:48:06 PM
> Subject: Self-introduction: Jack Winch (jwinch)
>
> Hi All,
> My name is Jack and I'm an 18 year old applications engineer, based in the
> UK. I have worked for Rolls-Royce plc for two years now and they are
> sponsoring me through my education as an electrical and electronics engineer
> (later forking me off into software engineering). For the past seven months
> I have been working as a QA tester for a new instructional system - it's
> purpose is to take measurement and test requirements from development
> engineers and produce the required technical instructions/documents/data
> aquisition system configuration files, to allow for the rigging of
> instrumentation on the experimental engine and for the configuration of the
> test data systems. I have also been involved in the comissioning and
> validation of new measurement hardware/data acquisiton system architecture
> for a new test rig being built by RR in Dahlewitz, Germany.
> For those who may be curious, my LinkedIn profile may be found here:
> https://www.linkedin.com/in/jack-winch
> Although I may be young, still a little wet behind the ears and some may say
> 'naive', I am a highly enthusiastic and knowledge hungry individual, who has
> a passion for learning, as well as a passion for being involved with
> inovative projects such as the Fedora project. I have spent a lot of time
> working within the different spins of Fedora (we use Fedora extensively
> within RR) and it would be amazing if you could put my high energy,
> enthusiasm and current technical experience to use, within the QA group.
> I look forward to hearing from some of you and I am eager to help in whatever
> manner you see fit.
> Many Thanks and Kind Regards,
> Jack Winch
>
> _______________________________________________
> test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
>
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
