Josh Lucas wrote:
>
> Jon Stevens wrote:
> >
> > on 8/28/2000 4:04 PM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
> >
> > > I'd like to add in future versions of the TDK and
> > > was wondering if anyone had any pointers.
> > >
> > > 1. A tool like JMeter, except non-GUI (maybe JMeter
> > > has a GUI-free mode) that can be used to run
> > > a testbed against the TDK so that we can make
> > > sure that releases are consistent. Sort of like
> > > a WatchDog for Turbine/TDK.
> >
> > You are asking for two different things here. :-)
> >
> > #1. would be a load testing type tool.
> > #2. would be a regression testing suite.
> >
> > In #1. JMeter or ab is fine. No need to include in the TDK imho.
> > In #2. We should explore using Watchdog or JUnit. I do feel though that this
> > type of thing belongs in each project and not in the TDK itself. The TDK
> > should be simple enough that it doesn't require a lot of regression testing.
>
> Even though it might not 'belong' in the TDK, some sample JUnit tests
> for the sample app might show how it can be used for an individual
> project.
+1, and I think that they do in fact belong in the TDK. It makes sense
to me that a development kit includes samples of everything that you
could produce with it (including tests). If everyone agrees on JUnit, I
will do the necessary work. Thoughts?
--
Daniel Rall <[EMAIL PROTECTED]>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
