Dirk,
I think if you can convince the management that effort spent on
developing the Trac plugin for your company need will pay off, it is
possible to allocate the time doing it. It is all about the trade-off
decision software organization have to decide. I know it is very hard but
if we as developer of the company can justify the usefulness of the
contribution to Open source software. The community would grow much faster.
I am very new to Trac too. I have to spare my own time doing this.
However, once I can prove that the work I am doing will help the company,
they might actually allow me to work on it as part of my job.
I hope the current trac implementation works out for you. If now, it
might be good idea if you could spend more time writing up the requirement
of the feature that you need in more detail. I try to pick up some
Request-A-Hack ticket as well but most of them are 1 liner. I don't think
it's is really enough for volunteer to do anything about those requests.
I am working on the TracMetrixPlugin. I am trying to apply software
engineering disciplines on this as well. I created the requirement page for
it so that I can communicate with the community. I haven't gone into the
detail on how to track it yet but I plan to create user story from the
requirement document (wiki page) that I have.
Let's keep the conversation going, there might be some people who need
such requirement management system. I know we do but my first priority is
the TracMetrixPlugin.
Best Regards,
Bhuricha Deen
On 4/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> > I have found a test case management tool (Trac plugin) on
> > http://trac-hacks.org/wiki/TestCaseManagementPlugin.
> >
> > Did someone try it already in real usage?
> >
>
> Thanks for the pointer. I had looked into it, but initially I could not
> match the features to my requirements. After rereading the webside
> things look much clearer to me. The main issue, why I skipped this
> plugin initially, was that every test is done as a new ticket. This adds
> a overhead if you have lot's of tests and have to check every ticket, I
> was looking for something "easier". The fact, that the workflow is not
> (was not) customizeable for each ticket type seemed to be a problem for
> me, too.
>
> Nevertheless, we are going to check next week, whether this plugin is
> suitable for our needs.
>
> Still I think, that the different ticket types needs a better separation
> within trac, e.g. a custom fields for each ticket type, custom UI,
> custom workflow, and so on. Additionally I always find myself in trouble
> when I need to tie a ticket/WIKI page to a specific version / branch in
> sourcesafe. The TestCaseManagementPlugin solves this problem by storing
> the cases itself with the software (subversion) and only store the
> concrete test instance within trac. But this behavoir could be improved
> in trac.
>
>
> If I only had time to help in this area ....
>
>
> Dirk
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
