Thanks so much!
On Apr 20, 1:18 pm, yoheeb <[email protected]> wrote:
> On Apr 20, 9:39 am, Olemis Lang <[email protected]> wrote:
>
> > On Thu, Apr 16, 2009 at 7:10 PM, Si Chen <[email protected]> wrote:
>
> > > Hi there, I'm from the opentaps Open Source ERP + CRM project
> > > (www.opentaps.org) We've been using trac internally for over a year
> > > now--thanks so much, everybody.
>
> > > We need a quality management system for manufacturing companies which
> > > use our software. The requirement is for a module which can store
> > > templates of tests with testing steps and range of acceptable values
> > > at each step.
>
> this is entirely unique per group, but I think a combination of the
> TypedTicketWorkflow, MasterTickets, TracForms, and possible the
> TestCaseManagement or QA tracker plugins. You might want one of the
> ticket templating ones as well depending on the implementation.
>
> a system we are experimenting with:we have the following ticket types:
> Feature branch, defect, enhancment, and test, testSuite. A "feature"
> branch is always blocked by a singe testSuite type, and many defect
> and ehancement types. and ehancement or defect is always blocked by a
> singe test type. The workflow for the test, testSuite, and Feature
> branch are highly customized for our process. but the basics are the
> feature branch, defect, enhancment have a state in them "ready for
> test", with an assign to option. the test and testSuite types have
> completely different workflows than a defect or enhancment, and have
> different close states of pass, fail, skipped. They also have no
> verification stage, instead we have a "updateProjFile" state vs.
> "requiresVerification" the ticket then goes to closed after the
> results are in the project file.
>
> We also use the tracForms plugin for our test and testSuite
> templates. however I think we plan to try a switch to the
> TestCaseManagement one, for the source control hook of test cases and
> suites. we are in the testing stages right now anyway, so we can
> experiment a bit.
>
> The hardest part is the highly typed workflow. we still have the
> occassional "dead path" case we never expected to use. Of course, if
> you are specifically tracking tests as a completely separate project,
> your workflow would be less complicated.
>
> In other words, yes, you can do this. The ability to link to other
> things in the wiki (such as tickets, requirements if you use the wiki
> for that, author notes etc. is really nice) and with 11.4, you can
> allow custom fields to be wiki markup, which makes it even easier to
> streamline/link/trace info.
>
> they key is to tailor it to your workflow and organizational needs.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
