Hi Sumantrom,
Thank you very much for warm welcome :-)
Thanks,
Dominic Geevarghese
4096R/43EACB09
On Mon, Aug 21, 2017 at 12:11 PM, Sumantro Mukherjee <sumukher(a)redhat.com>
wrote:
----- Original Message -----
> From: "Dominic P Geevarghese" <dominicpg(a)gmail.com>
> To: test(a)lists.fedoraproject.org
> Sent: Friday, August 18, 2017 9:15:45 PM
> Subject: Introduction - Dominic Geevarghese
>
>
> Fellow members,
>
> I am excited to meet the QA community and I would like to be part of
Fedora
> QA contributors.
>
> I am Dominic Geevarghese ( 4096R/43EACB09 ) , using various distros
including
> RHEL/CentOS/Fedora/Suse in professional life and Fedora on my personal
> hardware. My irc nick is dominicpg and I am available on most of the
> #fedora-* channels.
>
> --
> Cheers,
> Dominic Geevarghese
>
> _______________________________________________
> test mailing list -- test(a)lists.fedoraproject.org
> To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
>
Hey Dominic,
First of all, Welcome and thanks for showing your interest in Fedora QA. I
have sponsored your QA group request.
You can start off by testing updates in [
http://bodhi.fedoraproject.org/]
for 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 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.n.3_Summary
[
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.
Thanks
//sumantrom
_______________________________________________
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org