On Sat, Jan 26, 2019 at 10:12 PM David Bauer <dbxx@posteo.net> 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-leave@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.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|<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 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