#152: Test Cases Management
--------------------------+-------------------------------------------------
Reporter: rhe | Owner: rhe
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 15
Component: Wiki | Version:
Resolution: | Keywords: retrospective
--------------------------+-------------------------------------------------
Comment (by jlaska):
I love the idea of doing a test event with a pilot instance of
nitrate/TCMS. It was fun doing that with the semantic-mediawiki, and I
think we learn a lot with that approach. We've all talked about TCMS and
how best to integrate it with our workflow. There are definite
shortcomings to our current wiki-based approach that limit our ability to
growth, but there are plenty of positive lessons learned that I think we
should recognize and prioritize.
Hurry: Would you be willing to start drafting some wiki content so we can
capture this? Either a requirements or technology comparison document? I
don't want this to be a free-for-all 'I want a pony' list of features we
want of a TCMS solution. But perhaps starting with documenting the pro's
and con's with our current wiki-based workflow? The goal for me would be
to identify what our MUST-HAVE and NICE-TO-HAVE's are from any solution.
Ideally, we can use that to determine the best route forward (whether it's
filing bugs/tickets/rfe's against TCMS, or something else).
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/152#comment:2>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
