[erlang-questions] Integration testing in Erlang
Thu Jun 14 14:49:18 CEST 2007
Kirill Zaborski wrote:
> But I do not get it - why do you need 2 different test frameworks?
> Does not Yatsy include functionality of EUnit?
Yes you can do similar kind of tests with Yatsy.
However, EUnit is much more light-weight. We are using:
Yatsy - for system tests.
It can execute on the target node or from a remote node.
We test major parts of our system where we prepare DB contents,
setup timeouts and config data. We run tests both within the
target node as well as remotely via our Xml-Rpc interface.
EUnit - for unit tests (i.e in general development where appropriate).
While you are developing code you define input and expected output
for local code in the module and run the EUnit generated test/0
function until your assertions are fulfilled.
> On 6/14/07, Torbjorn Tornkvist <tobbe@REDACTED> wrote:
> Kirill Zaborski wrote:
>>> A bit scarce docs, placing some simple example will be useful.
>> There are some edoc info in the code,
>> but yes, the docs are lacking a bit.
>> I started to implement an example for an app in jungerl
>> but got side-tracked. I will try to finish the example.
>>> How does yatsy differ from test_server and EUnit?
>> It takes (almost) the same ETS SUITE files as input.
>> The main difference to ETS is that it is available from
>> a public repository and thus can be improved and maintained
>> We (Kreditor) use it for our automatic testsuites both nightly
>> builds as well as integrated with Cruise Control (i.e all test-suites
>> are automatically run as soon as someone does a checkin into our svn repos).
>> We are also using EUnit which is great to use for a test-driven
>> development aproach. See this the excellent blog entry for example:
>>> Integration with Yaws?
>> Yatsy can produce reports as HTML on disk as well as deliver
>> them via the Yaws server that automatically is setup.
>> Cheers, Tobbe
>> erlang-questions mailing list
More information about the erlang-questions