----- Original Message -----
From: "zhibli" <zhibli(a)redhat.com>
To: test(a)lists.fedoraproject.org
Sent: Saturday, February 3, 2018 1:49:40 PM
Subject: Self-introduction Zhibin Li
Hi guys,
I'm hoping that I can join the QA team. I am now a grade 3 student in
college.
As I get a semester off, no course, in other words, I've got a opportunity to
be
an intern in filesystem-qe team which is a sub-team in Red Hat QA department.
My name is Zhibin Li, I'm 22 years old and from China. I don't whether you
guys
have heard about my school. I study in UESTC in Chengdu, Sichuan Province.
I'm so
interested in all the Linux stuff and that's one of the reasons I get into
Red Hat
to improve my skill on Linux. I'm hoping that I can become part of the fedora
QA
Team because I think there are some connections between Red Hat QA department
and
fedora QA Team and it will eventually help me work better and contribute to
the
open-source community.
Thanks,
Zhibin Li
_______________________________________________
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
Hey Zhibin Li!
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 Fedor26,
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 20180130), 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
For Automation, you can start looking at Taskotron
[
https://fedoraproject.org/wiki/Taskotron]
and Open
QA[https://fedoraproject.org/wiki/OpenQA].
[
1]https://fedoraproject.org/wiki/QA:Updates_Testing
[
2]https://fedoraproject.org/wiki/Test_Results:Fedora_28_Rawhide_20180130....
[
3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[
4]https://bugzilla.redhat.com/
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
off
with release validation.
Thanks
//sumantro