----- Original Message ----- > From: "Dirk Gottschalk" <dirk.gottschalk1980@xxxxxxxxxxxxxx> > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Wednesday, April 5, 2017 9:01:56 PM > Subject: Introduction > > Hi, > > my name ist Dirk, I'm 36 years old from Aachen, Gernamy. > > I'm a software developer, system and network administrator and I use > Fedora since it's first release. > > Release 25 was the first release which brought me in trouble after > upgrading from Fedora 24. I could fix all issues, so everything is > okay. That is the reason for my decision to test the new release before > something goes wrong and I want to share my results of this tests whith > you, so that it could be possible to solve eventually appearing > problems before the new release becomes final. > > If you have any questions, feel free to ask. > > Regards, > Dirk > > -- > Dirk Gottschalk, Aachen > Tel.: 01573 / 1152350 > eMail: dirk.gottschalk1980@xxxxxxxxxxxxxx > > _______________________________________________ > test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx > Hey Dirk, First of all, Welcome and thanks for showing your interest in Fedora QA. I've sponsored it now. :) You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 24 , 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 alpha (Fedora 26 Alpha 1.7), 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 There is a three part series in Fedora community blog which can help you starting some of the validation testing and update testing. We also have a test day coming up on 6th. You can read up https://fedoraproject.org/wiki/Test_Day:2017-04-06_AnacondaBlivetGUI for more info. [1]https://fedoraproject.org/wiki/QA:Updates_Testing [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.7_Summary [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [4]https://bugzilla.redhat.com/ Thanks Sumantrom _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
