----- Original Message -----
> From: "Harold Dost" <harolddost@xxxxxxxxx>
> To: test@xxxxxxxxxxxxxxxxxxxxxxx
> Sent: Wednesday, November 9, 2016 3:35:50 AM
> Subject: Self-introduction: Harold Dost
>
> Hey QA,
>
> I have worked on Red Hat machines for most of my professional life,
> and I am making the transition to Fedora as my daily driver. As such I
> thought I would like to give back at some level since I know I would like
> to see Fedora continue.
>
> I am Harold Dost and I live in the Detroit Metro Area, MI, USA. As I said
> before I've been interacting with Linux for a little while, at least since
> 2008.
> I have worked primarily as a Java, Integrations and Web Developer in that
> time. Some server administration has been sprinkled in there at different
> times.
> I also have experience in C and C++ to the extent that I've written some
> simple networked programs for my own learning purposes as well as a simple
> kernel module. As of late my work has been focused on QA for multiple teams.
>
> Hence I thought it would be a good place to start. I do aspire to do
> some development
> contributions in the future, but I've found that testing is one of the better
> ways that I learn about a system. I was thinking that triage may a
> good place for me to
> start since I don't always have the most time. However, let me know if
> there's any better
> places to start.
>
> I hope to be more help than hindrance.
>
> Thank you,
Hey Harold
Thanks for your interest in joining the QA team , we are currently on the verge of releasing Fedora 25 and this is where the last leg of validation is important. The last leg of release validation. 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 branched, you can run test cases which are mentioned [1] and submit your results in the test matrix.
Note that each of the test cases[2] 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 [3] 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
You can also do update-testing, 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 [4]. You can also, use fedora-easy-karma for giving out feedbacks.
[1]https://fedoraproject.org/wiki/Test_Results:Current_Summary
[2]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[3]https://bugzilla.redhat.com/
[4]https://fedoraproject.org/wiki/QA:Updates_Testing
Should you have any questions , feel free to ping me over IRC or shoot a mail to this list!
Thanks
Sumantro
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
