[ejabberd] Automated tests.

Jonas Ådahl jadahl at gmail.com
Thu Dec 2 13:33:17 MSK 2010

On Thu, Dec 2, 2010 at 12:06 AM, Badlop <badlop at gmail.com> wrote:
> 2010/11/20 Inoshiro Linden <inoshiro at lindenlab.com>:
>> I am writing some modifications to ejabberd.  Is there an automated
>> test framework?  I do not see an obvious one, though I am new to
>> erlang.
> In case you are still wondering about that.
> From what I know, there are three test frameworks for erlang code:
> * EUnit: http://www.erlang.org/doc/apps/eunit/chapter.html
> * Common Test: http://www.erlang.org/doc/apps/common_test/basics_chapter.html
> * Quickcheck (proprietary): http://www.quviq.com/
> I cannot offer you hints and recommendation because I didn't yet use
> any of them.
> No test framework is used in ejabberd yet.
> BTW, I'm using Dialyzer
> http://www.erlang.org/doc/apps/dialyzer/dialyzer_chapter.html
> in ejabberd master branch, but that doesn't count as a testing
> framework I guess.


Another tool useful when writing tests for ejabberd modules is meck or
erly_mock (you can find both on github). By mocking (or mecking) the
ejabberd_modules you use, you can without having to start an ejabberd
server test your modules behaviour and interaction with (a fake)


More information about the ejabberd mailing list