Hi all!
Let me introduce myself.
My name is Danil Grigorev, I am 44 years old.
I live in Togliatti, Russia.
I have some experience as a system administrator
and worked with Fedora and CentOS.
I don't have any software testing experience,
but hope to get some while being a part of The Fedora Project QA team.
I would appreciate if someone could approve my membership in the qa group.
Sincerely,
Danil Grigorev.
_______________________________________________
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
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 then please apply and send me an email with your FAS ID and I will approve.
You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 29, Fedora 30, and Fedora 31. 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 32 Rawhide 20200122.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 {resultPASS|<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 {resultFAIL|<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.
Fedora QA dashboard is currently being developed which is here https://taskotron.fedoraproject.org/landing_page/
Other Blogs to read:
- 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_32_Rawhide_20200122.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!
_______________________________________________ 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
