Re: Self-introduction: Julian Schlüntz

[Sumantro Mukherjee]

----- Original Message -----
>  From: "Julian Schlüntz" <julian(a)schluentz.de&gt;
>  To: test(a)lists.fedoraproject.org
>  Sent: Thursday, July 12, 2018 1:16:51 AM
>  Subject: Self-introduction: Julian Schlüntz
>  
>  Hello everyone,
>  
>  my name is Julian Schlüntz, I have been using Fedora for a long time (I
>  think since Fedora Core 3) and it is time I started contributing. I like
>  testing stuff and figuring out problems, so I figured QA would be the
>  right place for me.
>  
>  I am from Germany, 31 years old and have some development experience.
>  My IRC nickname is 'gapophustu'.
>  
>  Cheers
>  
>  _______________________________________________
>  test mailing list -- test(a)lists.fedoraproject.org
>  To unsubscribe send an email to test-leave(a)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/[e-mail]...
>   
Hey Julian!

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If you have, I have
sponsored you by now.

You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 27,
Fedora 28, and Fedora 29.  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 29 Branched 20180923), 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].



https://fedoraproject.org/wiki/QA:Updates_Testing
https://fedoraproject.org/wiki/Test_Results:Fedora_29_Branched_20180923.n...
https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
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