Self-introduction: Alejandro

["Alejandro (0xalen)"]

Hi,

My name is Alejandro. I'd like to be a part of the QA team. There's no much to say: I've been on and off Fedora since F18, and exclusively on it since F24.

Hopefully I'll be able to help.
Have a nice day

----
Alejandro
PGP: 0x545a2d52efbe3b41

[Sumantro Mukherjee]

----- Original Message -----
> From: "Alejandro (0xalen)" 
> To: [e-mail]
> Sent: Saturday, December 23, 2017 5:56:01 AM
> Subject: Self-introduction: Alejandro
>
> Hi,
>
> My name is Alejandro. I'd like to be a part of the QA team. There's no much
> to say: I've been on and off Fedora since F18, and exclusively on it since
> F24.
>
> Hopefully I'll be able to help.
> Have a nice day
>
> Alejandro
> PGP: 0x545a2d52efbe3b41
>
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

Hey Alejandro!

First of all, Welcome and thanks for showing your interest in Fedora QA. I have sponsored your request!

You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 26, Fedora 27, and F28.  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_28_Rawhide_20171128.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].

[1]https://fedoraproject.org/wiki/QA:Updates_Testing
[2]https://fedoraproject.org/wiki/Test_Results:Fedora_28_Rawhide_20171128.n.0_S...
[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 F28. You can find the announcements on @test-announce list and community blog.

We are currently doing our best to kinda test F28 Rawhide, it will be great if you start off
with release validation.

Happy Holidays! :)

Thanks
//sumantrom

["Alejandro (0xalen)"]

Thank you!

Right now I'm familiarizing myself with Bodhi and fedora-easy-karma, and going over their respective documentation.
I have setted up 7 VMs for testing (Cinnamon, Xfce, LXDE, LXQt, MATE, KDE, GNOME ) and I use GNOME as default to test Stable.
Question: Is there any consideration I should have while testing in the VMs instead of physical machines?

----
Alejandro
PGP: 0x545a2d52efbe3b41

Sent with [ProtonMail](https://protonmail.com) Secure Email.
> -------- Original Message --------
> Subject: Re: Self-introduction: Alejandro
> Local Time: 25 December 2017 2:29 PM
> UTC Time: 25 December 2017 17:29
> From: [e-mail]
> To: Alejandro (0xalen) , For testing and quality assurance of Fedora releases
>
> ----- Original Message -----
> > From: "Alejandro (0xalen)" [e-mail]
> > To: [e-mail]
> > Sent: Saturday, December 23, 2017 5:56:01 AM
> > Subject: Self-introduction: Alejandro
> > Hi,
> > My name is Alejandro. I'd like to be a part of the QA team. There's no much
> > to say: I've been on and off Fedora since F18, and exclusively on it since
> > F24.
> > Hopefully I'll be able to help.
> > Have a nice day
> >
> > Alejandro
> > PGP: 0x545a2d52efbe3b41
> >
> > test mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> Hey Alejandro!
>
> First of all, Welcome and thanks for showing your interest in Fedora QA. I have sponsored your request!
>
> You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 26, Fedora 27, and F28. 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_28_Rawhide_20171128.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].
>
> [1]https://fedoraproject.org/wiki/QA:Updates_Testing
> [2]https://fedoraproject.org/wiki/Test_Results:Fedora_28_Rawhide_20171128.n.0_S...
> [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 F28. You can find the announcements on @test-announce list and community blog.
>
> We are currently doing our best to kinda test F28 Rawhide, it will be great if you start off
> with release validation.
>
> Happy Holidays! :)
>
> Thanks
> //sumantrom
>
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Sumantro Mukherjee]

----- Original Message -----
> From: "Alejandro (0xalen)" 
> To: "For testing and quality assurance of Fedora releases" 
> Sent: Wednesday, December 27, 2017 8:28:24 AM
> Subject: Re: Self-introduction: Alejandro
>
> Thank you!
>
> Right now I'm familiarizing myself with Bodhi and fedora-easy-karma, and
> going over their respective documentation.
> I have setted up 7 VMs for testing (Cinnamon, Xfce, LXDE, LXQt, MATE, KDE,
> GNOME ) and I use GNOME as default to test Stable.
> Question: Is there any consideration I should have while testing in the VMs
> instead of physical machines?

Awesome. No you can safely use VMs also, it's recommended to be done in a VM especially
things which might break your production system.

Thanks
//sumantro
> Alejandro
> PGP: 0x545a2d52efbe3b41
>
> Sent with ProtonMail Secure Email.
>
> -------- Original Message --------
> Subject: Re: Self-introduction: Alejandro
> Local Time: 25 December 2017 2:29 PM
> UTC Time: 25 December 2017 17:29
> From: [e-mail]
> To: Alejandro (0xalen) , For testing and quality
> assurance of Fedora releases
>
> ----- Original Message -----
>
> From: "Alejandro (0xalen)" [e-mail]
> To: [e-mail]
> Sent: Saturday, December 23, 2017 5:56:01 AM
> Subject: Self-introduction: Alejandro
> Hi,
> My name is Alejandro. I'd like to be a part of the QA team. There's no much
> to say: I've been on and off Fedora since F18, and exclusively on it since
> F24.
> Hopefully I'll be able to help.
> Have a nice day
>
> Alejandro
> PGP: 0x545a2d52efbe3b41
>
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Hey Alejandro!
>
> First of all, Welcome and thanks for showing your interest in Fedora QA. I
> have sponsored your request!
>
> You can start off by testing updates in [ http://bodhi.fedoraproject.org/ ]
> for Fedora 26, Fedora 27, and F28. 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_28_Rawhide_20171128.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 ].
>
> [1] https://fedoraproject.org/wiki/QA:Updates_Testing
> [2]
> https://fedoraproject.org/wiki/Test_Results:Fedora_28_Rawhide_20171128.n.0_S...
> [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 F28. You can find
> the announcements on @test-announce list and community blog.
>
> We are currently doing our best to kinda test F28 Rawhide, it will be great
> if you start off
> with release validation.
>
> Happy Holidays! :)
>
> Thanks
> //sumantrom
>
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>
> test mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]