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.
> 2. The second is a bit of code for a self extracting
> .class file that works from the console so
> that we can get rid of the .tgz/.zip hassle.
I actually don't mind the tgz/zip hassle. I'm -1 on .class because a .jar
would also do the same thing as a .class. The issue is that a lot of web
servers don't have a mimetype for dealing with downloading a .class file
appropriately. tgz and zip are most standard and .jar is moving up there.
for what it is worth, .zip and .jar are the same thing.
-jon
--
http://scarab.tigris.org/ | http://noodle.tigris.org/
http://java.apache.org/ | http://java.apache.org/turbine/
http://www.working-dogs.com/ | http://jakarta.apache.org/velocity/
http://www.collab.net/ | http://www.sourcexchange.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
