Hello Igor.
Welcome to Fedora QA, I have sponsored you in the QA FAS group.
You can start off by testing updates in
<http://bodhi.fedoraproject.org/> for Fedora 39, Fedora 40, and Fedora
41. 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 with "pending" & "testing". You can read much about
update testing here [1]. You can also use the command fedora-easy-karma
from your terminal for giving out feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/Release Candidate compose versus
certain criteria. For example, let's take the latest compose, you can
run test cases which are mentioned [2] and submit your results in the
test matrix.
Note that each of the test case [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.
Other blogs posts to read (they are dated, but still valuable):
-
<https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/>
-
<https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-2/>
-
<https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-3/>
[1] <https://fedoraproject.org/wiki/QA:Updates_Testing>
[2]
<https://fedoraproject.org/wiki/Test_Results:Fedora_41_Branched_20241012.n.0_Summary>
[3] i.e. <https://fedoraproject.org/wiki/QA:Testcase_USB_fmw>
[4] <https://bugzilla.redhat.com/>
Ciao,
A.
On 16.10.2024 21:10, Igor Jagec wrote:
Hi Fedora QA Team,
I was inspired to join the Fedora QA community after listening to the
recent Fedora podcast on QA – it really resonated with me!
I'm Igor Jagec (FAS nickname: igorjagec). My open source journey began
over 20 years ago with Red Hat 6.2 (pre-Fedora). I even worked as a
professional Linux sysadmin, but my last Linux job ended 10 years ago.
Back then, we never had automated testing and deployment. The industry
has significantly changed since then, so I'm eager to reboot my career
by getting back to my Linux roots and learning modern practices. I've
already had some fun participating in testing F40 to F41, and I'm keen
to get more involved in Fedora QA and gradually increase my
contributions.
In the long run, I'm interested in learning Ansible, Python, openQA,
and other relevant and transferable skills, but I want to start with
something manageable. I understand that consistency is key. What are
the next steps? Should I reach out to sponsors directly via Matrix?
Looking forward to getting involved!
Best regards,
Igor Jagec
--
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
