[Fedora QA] #96: Proven tester mentor request

Fedora QA trac at fedorahosted.org
Fri Jul 16 19:11:02 UTC 2010


#96: Proven tester mentor request
------------------------------------------+---------------------------------
  Reporter:  metabox                      |       Owner:  jlaska
      Type:  proventester request         |      Status:  closed
  Priority:  trivial                      |   Milestone:        
 Component:  Proventester Mentor Request  |     Version:        
Resolution:  fixed                        |    Keywords:        
------------------------------------------+---------------------------------
Changes (by jlaska):

  * status:  assigned => closed
  * resolution:  => fixed

Comment:

 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 at 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.

-- 
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/96#comment:4>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance


More information about the test mailing list