Indeed Mickael, that was the sort of setup I was
imagining, although you take a shared disk or so as a
prerequisite, while I was thinking of sockets on the network. A
disk might do the trick though.... good idea.
I have to think this over in detail. I will inform the list
when things get moving...
Anybody any remarks on Jubula? (or should I ask the jubula
mailing list ;-))
My point of view, is that it's much easier to write and maintain
tests with SWTBot than with Jubula.
The quality of the tooling for Java (Thanks to JDT) and the fluent
API of SWTBot make that it's really easy to write a test.
However if your user/functionnal tester hate programming or hate
having to deal with a textual langague, I understand they may prefer
Maybe a way to achieve that is to write 1 TestCase per
user, and write in your test some synchronization points.
You could use a file to write when a user performed a set
of action, and other user tests will wait for the file to
contain a specific token to go ahead.
// Do Step 1
// Step 1 done
// do Step 4
On Wed, Apr 13, 2011 at 6:26 AM, Tom Brus
> I am specially interested in these
issues because our application needs
> multi user testing and I need
to orchestrate parallel starts of our
> application on multiple machines. If
every instance is running its own test
> in its VM it is just harder to
Someone had forked SWTBot to add RMI support
in order to do just this.
They were building some plugins for pair
programming and needed to
orchestrate 2 eclipse instances from within
This message and any attachment
(the "message") is intended solely for the
addressees and is confidential. If you receive
this message by mistake, please delete it and
notify the sender immediately. Any use not in
accordance with its purpose, any out-spread or
disclosure, either as a whole or partially, is
prohibited except with formal approval. Internet
cannot guarantee the integrity of this message,
therefore BonitaSoft will not be liable for the
message if modified.