On Thu, 2010-12-23 at 14:35 +0000, Adam Williamson wrote:
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_pl...
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
Nice examples, this really helps to visualize the proposed changes.
So if I were acting as f-e-k or bodhi, I would combine the two lists of
cases to show the xorg-x11-drv-ati critpath tests...
* QA:Testcase radeon basic
Did I do that correctly?
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.
[[Category:Test_Cases|X]]
I did a minor tweak so that it would show up under 'X' (for xorg-x11...)
rather than 'P' (for Package_xorg-x11...).
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.
Thanks,
James