Hey everyone - some comments on the recent test plans out for review: * F12 Install Test Plan - https://www.redhat.com/archives/fedora-test-list/2009-June/msg00529.html Comment: One question on the F12 Install Test Plan - what do the priorities mean? Will the lower priority tests be performed later? When time permits? Not at all? * Rawhide Acceptance Plan - https://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan Comment: On the rawhide plan - the strategy section lists these parts: Repo sanity, Installability, and Basic Functionality - it would be good to follow the same organization in the test case section. * On test plans in general - Two challenges that I'm thinking about/always dealing with are: -> What level of detail to include for test cases? I'm trying to strike a balance between having enough test case information in the plan doc so that the reviewers can comment - but not too much so that the plan doesn't (a) become a burden to the author and (b) duplicate the actual test programs. Someone suggested to me that we follow a twitter model - a 140 char -> How to get reviewers to review the plan? This is always an issue. I'm hoping to be able to get different reviewers to review diff parts of the plans. I'm hoping that this more targeted approach will get folks to review the plans as being asked to review an entire plan - especially a long plan doc - can be intimidating. Stay tuned. The key is to find reviewers who have an interest and direct stake in the parts of the plan that you ask them to review. For Fedora, can you target some specific reviewers at all? --Len D. -- Len DiMaggio (ldimaggi@xxxxxxxxxx) JBoss by Red Hat 314 Littleton Road Westford, MA 01886 USA tel: 978.392.3179 cell: 617.872.3673 http://www.redhat.com -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
