#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:13 adamwill]: > Honestly, not really, no. =) The thinking behind creating the technically-not-needed combined category was 90% 'half-assing it as I was going along' and 10% for *non*-tool based cases: people just browsing the tests. It's easy via the API for tools to determine which test cases are members of both categories, but it's not easy for a user just browsing the Wiki to do it, AFAIK - there's no easy way to browse pages that are members of both one category and another category in the mediawiki user interface, that I know of. Correct, not without http://www.mediawiki.org/wiki/Extension:Multi- Category_Search > But really, I'm not married to the idea. (That's why I like it, ba-dum tish. Tip your server.) I don't really see any problem with having tools derive the combination themselves - it's not like they'll all be implementing it in wildly different ways, I can't see how that would happen. I can and have, I'd like to stay away from that. We're talking about a *small* set of tools at this point so the fallout would be minimal and manageable, agreed. My main point is, let's do our best to keep test cases and related test case metadata within the realm of TCMS (whether it's wiki or nitrate). -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/154#comment:14> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test