#154: Tracker: critical path test case creation --------------------------+------------------------------------------------- Reporter: adamwill | Owner: adamwill Type: enhancement | Status: new Priority: major | Milestone: Fedora 15 Component: Wiki | Version: Resolution: | Keywords: --------------------------+------------------------------------------------- Comment (by jlaska):
Replying to [comment:9 adamwill]:
here's a draft of a sample test case, for mdadm:
https://fedoraproject.org/wiki/User:Adamwill/Draft_QA_testcase_mdadm_package...
the production name would be QA:Testcase_mdadm_package_software , with
QA:Testcase being our standard prefix for test cases (it's not up for debate within the context of this ticket, if we change it we must change it for all test cases), then 'mdadm' being the source package name, 'package' indicating this (that it's named based on a src.rpm name - perhaps it should come before the name rather than after?), and 'software' being the name of this particular test (referring to software RAID).
Seems sensible from a general best practices point of view (QA:Testcase_%{sourcerpm}_%{userdefined}). The "_package" seems extraneous, but I might be missing something. With regards to finding applicable tests for a certain update, the most important thing is the category structure, right? That's how other tools will locate applicable tests.
what does everyone think, particularly of the naming and the
categorization? I don't quite feel that this one's nailed down yet, if anyone has smart ideas that'd be great.
In the page you linked, that test is in three categories ... 1. Category:critpath_test_cases 2. Category:mdadm_test_cases 3. Category:mdadm_critpath_test_cases I don't yet see the big picture for how the Categories will be grouped/organized, can you provide a hierarchical example?