Re: QA team schedule tasks

2019-01-29 Thread Sumantro Mukherjee 
On Tue, Jan 29, 2019 at 9:01 PM Ben Cotton  wrote:

> Hi all,
>
> Here's a draft of the F31 QA schedule with your feedback incorporated:
>
> https://fedorapeople.org/groups/schedule/f-31/f-31-quality-tasks.html
>
> Please review it and let me know if anything looks amiss. You can
> reply to this email or add a comment to the Pagure ticket at:
>
> https://pagure.io/fedora-project-schedule/issue/89
>
> --
> Ben Cotton
> Fedora Program Manager
> TZ=America/Indiana/Indianapolis
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Hey Ben,

The test day bits look great. Thanks :)
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: QA team schedule tasks

2019-01-29 Thread Ben Cotton 
Hi all,

Here's a draft of the F31 QA schedule with your feedback incorporated:

https://fedorapeople.org/groups/schedule/f-31/f-31-quality-tasks.html

Please review it and let me know if anything looks amiss. You can
reply to this email or add a comment to the Pagure ticket at:

https://pagure.io/fedora-project-schedule/issue/89

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Self-introduction: David Bauer

2019-01-29 Thread David Bauer 
Hi Sumantro,

thank you for your help and the brief introduction. I have already done some 
kernel regression tests and testing some updates. I will familiarize myself 
step by step with the different areas and will then see what suits me best and 
where I can contribute the most.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Greetings!

2019-01-29 Thread Sumantro Mukherjee 
On Tue, Jan 29, 2019 at 6:34 PM Thomas S. Clayborne 
wrote:

> Hello all, after using Linux for nearly 6 years now and finally finding a
> project I feel compelled to give back to, I am joining you all here.
>
> I have a pretty solid background in CS and Mechatronics engineering, and
> spent most of my time as a college student employed as a QA Test Engineer.
>
> While I'd love to contribute directly to source development of Fedora,
> it's not something I can take on the responsibility of at the moment.
>
> Happy to have the opportunity to give back, and i can't wait to get
> acquainted with you all.
>
> - Tom
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org



Hey Tom!


Welcome to Fedora QA, I have sponsored your FAS group request you by now.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30 (about to start).  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 30 Rawhide 20190121.n.1),
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|}} . 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|}} 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 Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.



[1] https://fedoraproject.org/wiki/QA:Updates_Testing

[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Rawhide_20190121.n.1_Summary?rd=Test_Results:Current_Summary

[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc

[4] https://bugzilla.redhat.com/ 

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.


We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

Thanks
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Greetings!

2019-01-29 Thread Thomas S. Clayborne 
Hello all, after using Linux for nearly 6 years now and finally finding a 
project I feel compelled to give back to, I am joining you all here. 

I have a pretty solid background in CS and Mechatronics engineering, and spent 
most of my time as a college student employed as a QA Test Engineer. 

While I'd love to contribute directly to source development of Fedora, it's not 
something I can take on the responsibility of at the moment.

Happy to have the opportunity to give back, and i can't wait to get acquainted 
with you all.

- Tom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduction

2019-01-29 Thread Marcin Szydelski 
Thank You Sumantro,

I already joined FAS qa group. Thanks.

I started with kernel and bodhi tests. Thanks for showing me more
opportunities.



Pozdrawiam/Best regards,
Marcin Szydelski
http://pl.linkedin.com/in/marcinszydelski
mob. +48 793433899


wt., 29 sty 2019 o 12:34 Sumantro Mukherjee 
napisał(a):

>
>
> On Mon, Jan 21, 2019 at 1:37 AM Marcin Szydelski 
> wrote:
>
>> Hi,
>>
>> I am very happy to join this community. I do use RH* distros for more
>> than 20 years and want to help improve Fedora, which currently is my
>> primary desktop os. :)
>>
>> I work as a Senior Ops in the financial industry. My main specialization
>> is GT.M database and core banking platform based on it.
>> My name is Marcin. I am from Poland, Wrocław.
>>
>> Pozdrawiam/Best regards,
>> Marcin Szydelski
>> http://pl.linkedin.com/in/marcinszydelski
>> mob. +48 793433899
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
>
> Hey Marcin,
>
>
> Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
> you have, I have sponsored you by now. If you haven't send me a email with
> your FAS ID and I will approve.
>
> You can start off by testing updates in [http://bodhi.fedoraproject.org/]
> for Fedora 28, Fedora 29, and Fedora 30 (about to start).  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 30 Rawhide 20190121.n.1),
> 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|}} . 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|}} 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 Open QA[
> https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.
>
>
>
> [1] https://fedoraproject.org/wiki/QA:Updates_Testing
> 
> [2]
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Rawhide_20190121.n.1_Summary?rd=Test_Results:Current_Summary
> 
> [3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
> 
> [4] https://bugzilla.redhat.com/ 
>
> Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
>
>
> We have test days coming happening now which is a nice place to start,
> please stay tuned to the @test list and help us testing!
> The current test day can be found on
> https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
> Test days schedule can be found on the fedocal
> https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
>
> Thanks
>
> //sumantro
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html

Re: Self-Introduction: Kris Eberwein

2019-01-29 Thread Sumantro Mukherjee 
On Wed, Jan 9, 2019 at 1:06 AM Kris Eberwein 
wrote:

> Hello all,
>
> I’m brand new to Fedora and the Test team and wanted to say hi to
> everyone. I’m a Data Engineer for a very large company and have been using
> RHEL and CentOS for about seven years in DevOps and Hadoop Environment
> roles.
>
> I mainly write Python, Java, and SQL, but I’ve been exposed to a little
> bit of everything over the years.
>
> I’m 41 years old, and live in Florida, USA with my wife and two kids. Well
> anyway, nice meeting everyone—can’t wait to get to work.
>
>
> Kris Eberwein
>
> IRC: keberwein
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org



Hey Kris,


Welcome to Fedora QA, I have sponsored your FAS group request you by now.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30 (about to start).  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 30 Rawhide 20190121.n.1),
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|}} . 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|}} 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 Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.



[1] https://fedoraproject.org/wiki/QA:Updates_Testing

[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Rawhide_20190121.n.1_Summary?rd=Test_Results:Current_Summary

[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc

[4] https://bugzilla.redhat.com/ 

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.


We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

Thanks

//sumantro
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduction

2019-01-29 Thread Sumantro Mukherjee 
On Mon, Jan 21, 2019 at 1:37 AM Marcin Szydelski 
wrote:

> Hi,
>
> I am very happy to join this community. I do use RH* distros for more than
> 20 years and want to help improve Fedora, which currently is my primary
> desktop os. :)
>
> I work as a Senior Ops in the financial industry. My main specialization
> is GT.M database and core banking platform based on it.
> My name is Marcin. I am from Poland, Wrocław.
>
> Pozdrawiam/Best regards,
> Marcin Szydelski
> http://pl.linkedin.com/in/marcinszydelski
> mob. +48 793433899
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


Hey Marcin,


Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven't send me a email with
your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30 (about to start).  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 30 Rawhide 20190121.n.1),
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|}} . 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|}} 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 Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.



[1] https://fedoraproject.org/wiki/QA:Updates_Testing

[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Rawhide_20190121.n.1_Summary?rd=Test_Results:Current_Summary

[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc

[4] https://bugzilla.redhat.com/ 

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.


We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

Thanks

//sumantro
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Self-introduction: David Bauer

2019-01-29 Thread Sumantro Mukherjee 
On Sat, Jan 26, 2019 at 10:12 PM David Bauer  wrote:

> Hi at all,
>
> I'm using Linux since more then 15 years. Most of the time as a deb
> distro hopper. But my journey was over as i found Fedora and the
> rpm-based distributions.
>
> I think to contribute here in the QA team is a very good opportunity to
> give something back to the FOSS and especially Fedora.
>
> I'm 38 years old, from Germany and working for a software company as 3rd
> Level Support. I'm not a programmer but have some basic knowledge in
> Python.
>
>
> --
> Beste Grüße / Best Regards
>
> David Bauer
>
> IRC: dbxx
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.or
> 



Hey David.


Welcome to Fedora QA, I have approved your request.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30 (about to start).  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 30 Rawhide 20190121.n.1),
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|}} . 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|}} 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 Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.



[1] https://fedoraproject.org/wiki/QA:Updates_Testing

[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Rawhide_20190121.n.1_Summary?rd=Test_Results:Current_Summary

[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc

[4] https://bugzilla.redhat.com/ 

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.


We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

Thanks

//sumantro
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Self Introduction: Glen Kaukola

2019-01-29 Thread Sumantro Mukherjee 
Hey Glen,


On Sun, Jan 27, 2019 at 12:47 AM Glen Kaukola  wrote:

> Hi there,
>
> I'm Glen Kaukola, long time Red Hat, CentOS, and Fedora user.
>
> I've always been informally involved in Fedora QA just through testing and
> filing bug reports.  I also do a bit of triage on bugzilla every now and
> again.  Once in a while I even dive in to some code and try my hand at
> fixing things.
>
> At one point, not too too long ago, I was getting geared up to start
> helping with some of the QA tooling, but never followed through with it.
> If memory serves I maybe became frustrated with something or other.  I
> forget who was helping me with all that at the time.
>
> At any rate, I have a lot more free time these days and would once again
> like to get more formally involved with QA.
>
> Thanks,
> Glen Kaukola
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org



Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven't send me a email with
your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30 (about to start).  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 30 Rawhide 20190121.n.1),
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|}} . 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|}} 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 Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.



[1] https://fedoraproject.org/wiki/QA:Updates_Testing

[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Rawhide_20190121.n.1_Summary?rd=Test_Results:Current_Summary

[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc

[4] https://bugzilla.redhat.com/ 

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.


We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

Thanks

//sumantro
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org