I second this.
We use the Erlang Test Server for subsystem tests
and system tests. In the systems we're building
right now, we have some half a million lines of
Erlang code (over a million lines of C), and
about 70 different erlang applications, not
counting the OTP apps. The Test Server is our
main vehicle for stitching together automated
tests, and our testers also write test suites for
system-level tests, similar to those Gordon
described. It works wonderfully.
BR,
Ulf W
> -----Original Message-----
> From: > [mailto:] On Behalf Of
> gordon guthrie
> Sent: den 14 juni 2007 13:16
> To: > Subject: [erlang-questions] Integration testing in Erlang
>>> Kirill
>> Depends on the sort of tests you want to write.
>> The Erlang Test Server will allow you to write as complex
> system tests as you want. It runs through a set of suite and
> test set-up routines, you execute your tests and it tears
> down your environment.
>> Typically I create a new db schema, load it with test data,
> start an application (or applications) and then execute tests
> against the known environment - depending on the product.
>> For large web apps you can use Tsung to record and script the
> http input and run regression tests, or you can use it as a
> 'white noise' tester and fire a million random inputs in and
> then look for crash reports (both work for me) .
>> Gordon
> _________________________________________________________
> Post sent from http://www.trapexit.org> _______________________________________________
> erlang-questions mailing list
>>http://www.erlang.org/mailman/listinfo/erlang-questions>