Thank you very much for the instructions Sumantro! I'll start by testing updates for f26.

2017-08-21 10:20 GMT+02:00 Sumantro Mukherjee sumukher@redhat.com:

----- Original Message -----

...

From: "Andreas Nazlidis" andreas221b@gmail.com To: test@lists.fedoraproject.org Sent: Monday, August 14, 2017 12:33:11 AM Subject: Self-introduction: Andreas Nazlidis

Hi! I want to start contributing to the QA team. I have been using

fedora for

...

about one year and linux since 2011. I think it's time to start

contributing

...

to the fedora project because i really like the distro.

I have basic knowledge in C/C++ and Python with which i implement

numerical

...

methods.

My name is Andreas Nazlidis, i am 33 years old and i currently live in Munich, Germany. I am a computational physicist.

I should mention that my laptop doesn't support virtualization so i want

to

...

have a productive system and at the same time the ability to help the QA team. I would appreciate any suggestions. Thank you very much in advance!

my IRC: anazli9

---

test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org

Hey Andreas,

First of all, Welcome and thanks for showing your interest in Fedora QA. You can start by sending a qa group membership.

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@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org