Thanks a lot Sumantro Mukherjee, I will go through the resources you shared and let you know.

On Wed 26 Sep, 2018, 2:25 PM Sumantro Mukherjee, <> wrote:

----- Original Message -----
> From: "Abdul Rehman" <>
> To:
> Sent: Wednesday, September 5, 2018 11:28:56 PM
> Subject: To join Fedora testing and quality assurance
> Hi,
> I am currently testing on Screen keyboard of Fedora using OpenQA and I found
> a bug which I would like to discuss on the list. So request to join me in
> the list.
> --
> Regards,
> Abdul Rehman Quadri
> _______________________________________________
> test mailing list --
> To unsubscribe send an email to
> Fedora Code of Conduct:
> List Guidelines:
> List Archives:
Hey Abdul!

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

I think you already had a word with Adamw but here's something more you can look into, if you are looking to contribute to Fedora QA. :)

You can start off by testing updates in [] 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 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:

For Automation, you can start looking at Taskotron[]
and Open QA[].

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
Test days schedule can be found on the fedocal

test mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives: