#96 Proven tester mentor request
Closed: Fixed None Opened 13 years ago by metabox.

Hi, this is a proven tester issue to request for a Proven Tester Mentor as described here https://fedoraproject.org/wiki/QA/JoinProvenTesters


Been working with redhat based distros for > 10 years.
Have been submitting bugs for F12 via debuginfo framework for last 12 months.
Unless I have to, I work exclusively with KDE4.
I am a QA person by trade not a dev, but have reasonable shell and Python experience.
I really enjoy performance testing and test automation frameworks.
here is my CV on linkedin http://www.linkedin.com/profile?viewProfile=&key=5833908&locale=en_US&trk=tab_pro

Greetings Mark!

Replying to [ticket:96 metabox]:

Hi, this is a proven tester issue to request for a Proven Tester Mentor as described here https://fedoraproject.org/wiki/QA/JoinProvenTesters

I'll be happy to sponsor you into the proventesters group. Please take a moment to read through the [https://fedoraproject.org/wiki/Proven_tester proventester instructions]. As a proventester, our job isn't to exhaustively find all defects in a software update. The focus is to determine whether the proposed software update negatively impacts core system functionality. Pay particular attention to the documented feedback procedures.

Once you have read the instructions, please confirm that you ...
1. have read and understand the instructions, and intend to follow the instructions when testing Fedora critical path updates
2. understand how to enable the update-testing repository
3. are familiar with providing test feedback using either the
[http://bodhi.fedoraproject.org/ Bodhi web interface], or the
[https://fedoraproject.org/wiki/Fedora_Easy_Karma fedora-easy-karma utility]

Based on [http://lists.fedoraproject.org/pipermail/devel/2010-June/137413.html
recently published bodhi statistics], it seems you have an understanding of
points #2 and #3 above. Please let me know if you have any questions or
concerns. Once I hear back, I'll sponsor your membership in the proventesters
group.

Replying to [comment:1 metabox]:

Been working with redhat based distros for > 10 years.
Have been submitting bugs for F12 via debuginfo framework for last 12 months.
Unless I have to, I work exclusively with KDE4.
I am a QA person by trade not a dev, but have reasonable shell and Python experience.
I really enjoy performance testing and test automation frameworks.
here is my CV on linkedin http://www.linkedin.com/profile?viewProfile=&key=5833908&locale=en_US&trk=tab_pro

With an interest and background in test automation, you may also be interested in the [https://fedoraproject.org/wiki/AutoQA AutoQA] project.

Hi and thank you for mentoring me.

Sorry about the delay responding, I have been in hospital having major surgery. I have min one week off and will get some fresh VMs together to start some QAing within the defined framework.

Moving through your points:

1) I understand the basic principal of critical path and how it is used in context of this testing framework. I have read and understand the instructions, and intend to follow the instructions when testing Fedora critical path packages.

2) I understand how to, and commit to enabling the update-testing repository on my testing VMs

3) I am familiar or understand how to provide test feedback using both the bodhi and/or f-e-k

I'm going to spend a bit of time with AutoQA too.

One testing scope type question...There are critical actions applicable to critical path packages - https://fedoraproject.org/wiki/Critical_path_action. Are these supposed to be covered as part of each test for each tester/VM/build or are just one or two selected? Does it matter?

Another one, sorry if I sound really dumb, Is this testing to be executed against F13 or F14 or both? I ask as both are referenced with milestones here https://fedoraproject.org/wiki/Fedora_release_criteria

All the very best

Mark

Replying to [comment:3 metabox]:

Hi and thank you for mentoring me.

You are welcome. I have approved your FAS group membership request, you are now a proventester. Congrats and happy testing!

Sorry about the delay responding, I have been in hospital having major surgery. I have min one week off and will get some fresh VMs together to start some QAing within the defined framework.

Oh goodness! Well, certainly glad to have your contributions while you recuperate.

One testing scope type question...There are critical actions applicable to critical path packages - https://fedoraproject.org/wiki/Critical_path_action. Are these supposed to be covered as part of each test for each tester/VM/build or are just one or two selected? Does it matter?

The critical path actions are a guidepost to help testers understand the types of failures they are looking for when testing the critical path. Unfortunately, there just isn't enough time to test each update in isolation. Most testers typically upgrade packages in batch, and then provide feedback. The only drawback with this method is if something does impact the critical path actions, unless you have a good hunch, you may need to do some detective work to determine which update introduced the critpath regression. In cases like this, if you get stuck, or are looking for guidance diagnosing the root cause ... the test@lists.fedoraproject.org mailing list and #fedora-qa IRC channel are great options to discuss the issue.

Another one, sorry if I sound really dumb, Is this testing to be executed against F13 or F14 or both? I ask as both are referenced with milestones here https://fedoraproject.org/wiki/Fedora_release_criteria

Good question actually. It will depend on what release the update you are testing is for. You're encouraged to test and provide feedback on whatever releases you have available to test. Fedora 14 won't be available using this workflow until it is branched from rawhide later this month (see [http://poelstra.fedorapeople.org/schedules/f-14/f-14-releng-tasks.html task#14]).

Thanks again! Don't hesitate to ask if you have further questions. Check out https://fedoraproject.org/wiki/QA#Communicate for tips on finding the right audience.

Login to comment on this ticket.

Metadata