----- Original Message ----- > From: "Stanislav Zidek" <szidek@xxxxxxxxxx> > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Sent: Thursday, March 23, 2017 11:03:01 PM > Subject: Self-introduction: Stanislav Židek > > Hi, > > I am Standa, a quality engineer from Red Hat, more specifically from BaseOS > Security team where I mostly focus on testing crypto-related libraries and > software (GnuTLS, NSS, OpenSSH and OpenSSL to name "our big four"). > > I have a couple of years of Linux background already, started as sysadmin of > dozens of Gentoo servers (don't laugh!) with Python servers and MySQL > databases in my previous job, which we successfully migrated to CentOS > (really big step forward). As time went forward, I started to be more and > more interested in security topics, which brought me to Red Hat and my > current team. > > Since we (QEs in Red Hat) are encouraged to devote part of our time to > testing Fedora software, I wanted to officially join your ranks to be able > to carry out the first public step on my Fedora-testing journey, which is > organising test day for crypto-policies. > > I don't like long write-ups, so I'll wrap it up here, > S. > > -- > Stanislav Židek > QE BaseOS Security > Red Hat Czech, Brno > > IRC: szidek > GnuPG: E378 3C12 8058 EF79 DE15 10C8 1943 496C 68B1 6848 > Cell: +420 777 613 895 Hey Standa, You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 24 , Fedora 25 and the upcoming 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.2), you can run test cases which are mentioned [2] and submit your results in the test matrix.There are a bunch of kernel panic and video driver bugs , which are known. Before filing one , check the filed bugs. 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. Also, there is a changeset in F26 which is[https://fedoraproject.org/wiki/Changes/OpenSSH_Crypto_Policy] are you planning to have a test day around it? 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 [1]https://fedoraproject.org/wiki/QA:Updates_Testing [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_Alpha_1.2_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
