On Tue, 2010-12-21 at 17:11 +0000, Adam Williamson wrote: > Hi, everyone. So, in the recent debate about the update process it again > became clear that we were lacking a good process for providing > package-specific test instructions, and particularly specific > instructions for testing critical path functions. > > I've been working on a process for this, and now have two draft Wiki > pages up for review which together describe it: > > https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_SOP_test_case_creation > https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_SOP_package_test_plan_creation I've now converted one package's set of test cases to the proposed new system to serve as an illustration. I used the Radeon driver, xorg-x11-drv-ati . This was a good example as there's a lot of them, and they split neatly into critpath, core and extended to illustrate the optional advanced categorization system. So, see: https://fedoraproject.org/wiki/Category:Package_xorg-x11-drv-ati_test_cases and note that one of the test cases is also in: https://fedoraproject.org/wiki/Category:Critical_path_test_cases you can also see at https://fedoraproject.org/wiki/Category:Test_Cases how this tracks back to that overall category - no test cases are in it directly, it's all hierarchical. thanks! I'm planning to work on a mockup for the f-e-k and bodhi integration this afternoon to show how we envision this all being used to kick ass, I think that'll make it clearer. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
