[erlang-questions] common_test and multiple nodes

Bernie Duggan bernie@REDACTED
Wed Jun 29 02:32:30 CEST 2011

Hi list,
I'm in the process of writing up some common_test based tests for a system
we're developing. While common_test seems to basically be pretty cool, I
have one thing that I can't quite see how to do (of course I may be looking
at the problem entirely the wrong way, too).

Our code can be looked at as behaving like a client-server system (actually
it's more like a peer-peer, but it's easier to explain this way and doesn't
really affect the question). What I'd like to be able to do is fire up a
server on one node with some test hooks (so that we can watch what's
happening), and a client on another node. Then, we have tests running on
both of them to ensure that a) the client is seeing the responses it's
expecting, and b) the server is behaving internally the way we expect for
the given client input.

It seems like common_test has /most/ of what I want for this as part of the
"large scale testing" features (ability to start up remote nodes and run
tests on them, having failures fed back to the master node etc). Except that
I can't see a way to guarantee that, for example, client_test_1 runs on the
client node at the same time as the corresponding server_test_1 runs on the
server node. It looks like the large scale testing stuff is basically
designed to run a whole pile of tests in parallel across multiple nodes,
without any interaction between them. Is this correct? If not, what am I
missing? If so, are there any suggestions for an alternative approach to the


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20110629/9595b48f/attachment.htm>

More information about the erlang-questions mailing list