Trac for test cases
ducat...@gmail.com
management system to track and monitor test cases. Has anyone used
trac for this somehow.? It would be great if we could have our defect
tracking and test case system both in trac.
any thoughts wold be great
Noah Kantrowitz
python unittest framework.
--Noah
Dirk
Noah Kantrowitz wrote:
> I am currently deploying Bitten[1] for this, using setuptools and the
> python unittest framework.
I've been trying to decide between bitten and the buildbot plugin
(target language is C++, if it matters). Can anybody give a comparison
between the two? What does one do that the other doesn't?
Thanks
Dirk
Matt Good
Hrm, "everything"? Currently the BuildBot plugin is just a skeleton
and doesn't offer any functionality yet. Of course BuildBot itself is
well established, but if you want to integrate it with Trac you'll need
to do it yourself.
-- Matt Good
Noah Kantrowitz
On the other hand Bitten is very well integrated with Trac, but has
less support on the build side ;-)
--Noah
Dirk
> > Hrm, "everything"? Currently the BuildBot plugin is just a skeleton
> > and doesn't offer any functionality yet. Of course BuildBot itself is
> > well established, but if you want to integrate it with Trac you'll
> > need
> > to do it yourself.
>
> On the other hand Bitten is very well integrated with Trac, but has
> less support on the build side ;-)
I knew it couldn't be that easy. :)
Can anybody give me a hint about activity on both of these projects? It
looks like BuildBot got a code drop in April and nothing after that,
while bitten was a diploma thesis and a Google SoC project, both of
which are over now. Doesn't look good for either, but at least bitten
has a bunch of open tickets. ;) Is there something going on behind the
scenes that's not immediately visible?
Is anybody but the initial developers using either one of those? How
successfully?
Thanks
Dirk
Don
testing integration with Trac.
Does anyone know how Bitten compares to Trac-cc?
Any other options?
Thanks,
Rainer Sokoll
> Can anybody give me a hint about activity on both of these projects? It
> looks like BuildBot got a code drop in April and nothing after that,
> while bitten was a diploma thesis and a Google SoC project, both of
> which are over now.
Bitten's author, Christopher Lenz, is subscribed to this list; thus
there are good chances to get a valid answer here :-)
Rainer
Peter Kropf
With my current work schedule, I should be able to get back to it part
time and have a working plugin over the next few weeks. Let me know if
that'll help...
- Peter
Doug Douglass
We've been using Trac-cc for several months on a single Trac-managed java project that's composed of approx. 10 components that represent a dozen java components, a couple services and a half dozen webapps, all inter-related (hence the single Trac project). Installation was a snap -- really like Tracs plugin architecture. I get the feeling Bitten is a more complex install/configuration.
The only shortcoming we've found with Trac-cc is that it is geared mostly to reporting of a single CC build project, which makes some sense as Trac is also geared toward managing one project. Since we have at least one build per component, we compensate by using CC log names that include the component name. This works OK except for build failure logs, for which it appears CC doesn't provide a means to control the log file name.
There's also ContinuTrac (see TracHacks) which integrates the Apache Maven Continuum CI system. We're a big maven shop so this is very compelling for us, just waiting for some enhancements to Continuum before re-evaluating versus CC/Trac-cc.
Hope that helps, let us know if/how you decide.
Doug
Lars Stavholm
> Noah Kantrowitz wrote:
>>> Hrm, "everything"? Currently the BuildBot plugin is just a skeleton
>>> and doesn't offer any functionality yet. Of course BuildBot itself is
>>> well established, but if you want to integrate it with Trac you'll
>>> need
>>> to do it yourself.
>> On the other hand Bitten is very well integrated with Trac, but has
>> less support on the build side ;-)
>
> I knew it couldn't be that easy. :)
>
> Can anybody give me a hint about activity on both of these projects? It
> looks like BuildBot got a code drop in April and nothing after that,
> while bitten was a diploma thesis and a Google SoC project, both of
> which are over now. Doesn't look good for either, but at least bitten
> has a bunch of open tickets. ;) Is there something going on behind the
> scenes that's not immediately visible?
Well, in my experience, bitten is actively maintained.
We use bitten at <http://linadd.org> (have a look at the
Build Status button). If you want build configuration
examples to get you started, let me know (we mostly use
the infamous ./configure + make + make install combo.
Whenever we've had problems, we got the answer or solution
from the author within a day or a few days.
> Is anybody but the initial developers using either one of those? How
> successfully?
Bitten works very nicely, we've used it for about six months now.
There are integration points with test cases that we haven't started
using yet, so I couldn't tell you about that, but for the builds
it works just great. IMHO it's the best choice for Trac integrated
build system.
Dirk
Hi Peter,
Peter Kropf wrote:
> I originally started the buildbot plugin but haven't finished it yet.
> With my current work schedule, I should be able to get back to it part
> time and have a working plugin over the next few weeks. Let me know if
> that'll help...
I'd certainly be very interested, as right now bitten seems to be more
nicely integrated, but a little behind in functionality.
Can you give us some ideas of which things you want to add? I'm not a
good python person, but if there are simple things I can try helping
out.
Yours
Dirk