You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by James Strachan <ja...@yahoo.co.uk> on 2001/11/15 17:11:39 UTC
distributed test harness anyone?
For some time I've wanted a distributed test harness, along the line of
JUnit & Cactus and the like but that could create a whole bunch of processes
in a network, wait until they've all started and are ready then fire in a
bunch of requests to different processes (from sample test files) at well
defined or random frequencies and track what happened then analyse the
results.
So I guess you could call this both integration testing and performance
monitoring.
I'm mostly thinking of JMS / MOM based test harnesses here, where JMS
publishers and subscribers are created in a network but I suppose it could
be similar for different clusters of web applications or web services. (e.g.
running a simple B2B exchange etc).
My early thoughts was to put something simple together using, say, JJAR to
do the class loading, XML documents to represent the 'proces configuration',
some daemon process to start/stop processes and Messenger & JMS to
distribute the requests, retrieve the results and do the process
coordination - then maybe make the whole thing appear like individual JUnit
test cases with maybe something like xmlunit so it could be integrated into,
say, CruiseControl automated builds.
I just wondered if anyone had any thoughts or ideas on the subject. I bumped
into Vincent by chance today (hey Vincent, small world!) and he had some
good ideas on the subject. I'm sure there are others around here.
James
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Betwixt] Documentation
Posted by robert burrell donkin <ro...@mac.com>.
On Monday, November 19, 2001, at 10:35 AM, James Strachan wrote:
> Hi Robert
hi james
> By all means dive in and add comments whereever you think is a good idea.
> The best way to get a feel for what betwixt can do right now is looking at
> the JUnit test cases in src/test/*.
my head's to small to cope without doc comments ;)
> I've been a bit side tracked with Messenger and dom4j lately but I'd like
> to
> get back to betwixt very soon (a week or so) to do a bean Navigator for
> Jaxen.
a bean navigator sounds pretty cool
> Also it'd be interesting to see how easy it would be to use betwixt
> to generate digester rules from a bean class.
jason's now more interesting in a completely dynamic xml <-> object model
mapper (for use with turbine). you start with a generic mapping pattern,
and then take any xml and any group of object - which together conform to
this pattern - and produce xml from the objects and objects from the xml.
> Betwixt uses introspection to determine a default XML representation model
> for a bean (which can be overridden by providing a custom XMLBeanInfo
> class
> in the same way as BeanInfo in the Java Beans spec).
<snip>
> Though I must admit that right now betwixt is a little one directional;
> the
> ElementDescriptor & AttributeDescriptor take an Expression that when
> evaluated on a bean will return an object - so its an abstraction on
> getting
> a property name, iterating or calling a method etc. This allows a very
> flexible mappings to occur - such as
> mapping a Map using the entrySet() method etc. Though this may make it a
> little harder to write an XML -> Object generator, such as to generate
> digester rules.
i'm interested to see how betwixt approaches the introspection.
plus - of course - i'm fed up of writing object model -> xml code to make
sure that the digestion is working properly...
- robert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Betwixt] Documentation
Posted by James Strachan <ja...@yahoo.co.uk>.
Hi Robert
By all means dive in and add comments whereever you think is a good idea.
The best way to get a feel for what betwixt can do right now is looking at
the JUnit test cases in src/test/*.
I've been a bit side tracked with Messenger and dom4j lately but I'd like to
get back to betwixt very soon (a week or so) to do a bean Navigator for
Jaxen. Also it'd be interesting to see how easy it would be to use betwixt
to generate digester rules from a bean class.
Betwixt uses introspection to determine a default XML representation model
for a bean (which can be overridden by providing a custom XMLBeanInfo class
in the same way as BeanInfo in the Java Beans spec).
e.g. Here's the code that given any Class could determine what elements &
attributes are available in XML...
Class aClass = ...;
XMLIntrospector introspector = new XMLIntrospector();
XMLBeanInfo xmlInfo = introspector.introspect( aClass );
// root element
XMLElementDescriptor root = xmlInfo.getElementDescriptor();
// attributes of root
XMLElementDescriptor[] attributes = root.getAttributeDescriptors();
// child elements
XMLElementDescriptor[] elements = root.getElementDescriptors();
Though I must admit that right now betwixt is a little one directional; the
ElementDescriptor & AttributeDescriptor take an Expression that when
evaluated on a bean will return an object - so its an abstraction on getting
a property name, iterating or calling a method etc. This allows a very
flexible mappings to occur - such as
mapping a Map using the entrySet() method etc. Though this may make it a
little harder to write an XML -> Object generator, such as to generate
digester rules.
James
----- Original Message -----
From: "robert burrell donkin" <ro...@mac.com>
> hi james
>
> i'm quite keen to take a look at betwixt but the documentation's a bit
> sparse.
>
> i could probably create some documentation patches if you like (since i'll
> probably end up writing java doc comments in order to understand it
anyway.
> ..)
>
> - robert
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
[Betwixt] Documentation
Posted by robert burrell donkin <ro...@mac.com>.
hi james
i'm quite keen to take a look at betwixt but the documentation's a bit
sparse.
i could probably create some documentation patches if you like (since i'll
probably end up writing java doc comments in order to understand it anyway.
..)
- robert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
[Betwixt] Documentation
Posted by robert burrell donkin <ro...@mac.com>.
hi james
i'm quite keen to take a look at betwixt but the documentation's a bit
sparse.
i could probably create some documentation patches if you like (since i'll
probably end up writing java doc comments in order to understand it anyway.
..)
- robert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>