Thank you!
Right now I'm familiarizing myself with Bodhi and fedora-easy-karma, and going over their respective documentation.
I have setted up 7 VMs for testing (Cinnamon, Xfce, LXDE, LXQt, MATE, KDE, GNOME ) and I use GNOME as default to test Stable.
Question: Is there any consideration I should have while testing in the VMs instead of physical machines?
-------- Original Message --------Subject: Re: Self-introduction: AlejandroLocal Time: 25 December 2017 2:29 PMUTC Time: 25 December 2017 17:29From: sumukher@xxxxxxxxxxTo: Alejandro (0xalen) <0xalen@xxxxxxxxxxxxxx>, For testing and quality assurance of Fedora releases <test@xxxxxxxxxxxxxxxxxxxxxxx>----- Original Message -----From: "Alejandro (0xalen)" 0xalen@xxxxxxxxxxxxxxSent: Saturday, December 23, 2017 5:56:01 AMSubject: Self-introduction: AlejandroHi,My name is Alejandro. I'd like to be a part of the QA team. There's no muchto say: I've been on and off Fedora since F18, and exclusively on it sinceF24.Hopefully I'll be able to help.Have a nice dayAlejandroPGP: 0x545a2d52efbe3b41test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxxTo unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxxHey Alejandro!First of all, Welcome and thanks for showing your interest in Fedora QA. I have sponsored your request!You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 26, Fedora 27, and F28. 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_28_Rawhide_20171128.n.0), 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 [https://fedoraproject.org/wiki/Taskotron]and Open QA[https://fedoraproject.org/wiki/OpenQA].We have a test day coming up for testing major changes in F28. You can find the announcements on @test-announce list and community blog.We are currently doing our best to kinda test F28 Rawhide, it will be great if you start offwith release validation.Happy Holidays! :)Thanks//sumantromtest mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxxTo unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
