esl / ejabberd_tests Goto Github PK

exml's xmlelement record's body attribute is called children now.
Fix the tests to use the new name.

The exml_query:path function doesn't accept elements as a path component any more. Use the new exml_query:paths instead.

The new exml code is to be found in api_cleanup branch

Hi, After running make quicktest it fails due to error reaching a dependency. Explicitly the error is below. Not sure if it is an error in the way dependency is being pulled or if I am doing anything incorrect.

Operating system: Ubuntu 14.04
erlang 18.1

Cloning into 'mochijson3'...
Pulling lhttpc from {git,"git://github.com/waisbrot/lhttpc.git", "824a89316d59353181990f5a461157751ca67907"}
Cloning into 'lhttpc'... fatal: reference is not a tree: 824a89316d59353181990f5a461157751ca67907
ERROR: git checkout -q 824a89316d59353181990f5a461157751ca67907 failed with error: 128 and output: fatal: reference is not a tree: 824a89316d59353181990f5a461157751ca67907
ERROR: 'get-deps' failed while processing /home/ejabberd_tests/deps/katt: rebar_abort make: *** [get-deps] Error 1

When running the test suites, via 'make test', against ESL ejabberd init_per_suite is always skipped for each suite - a sample of my logs are below. I am new to erlang/ejabberd and escalus so I'm having trouble investigating the cause. Is there documentation available for ejabberd_tests? Thanks in advance.

Testing ejabberd_tests.tests.login_SUITE: Starting test, 6 test cases
Testing ejabberd_tests.tests.login_SUITE: *** SKIPPED *** init_per_suite
Testing ejabberd_tests.tests.login_SUITE: TEST COMPLETE, 0 ok, 0 failed, 6 skipped of 6 test cases

Details in issue comments.

Some suites try to use output of escalus:delete_users as new Config but this function returns just ok. It is difficult to notice, because CT doesn't scream about failed end_per_suites and does not stop testing. Example of such suite is sm_SUITE, there can be more of them.

Create tests for issue esl/MongooseIM#185

This is an addendum to #131, which actually got me to that issue.

Now, escalus seems to just authenticate with the server, regardless of whether the server advertises auth mechanisms or not, so it might be a very good idea to have a check for that either in escalus directly or here.

I think each group or at least groups: moderator, admin (including admin_membersonly), occupant and owner should be moved to their own suites. Current muc_SUITE.erl file is far to big... ~4k lines of code...

The cert file could be for example send over RCP, saved on the MongooseIM machine and the server can be restarted. When all the tests are finished, the cert file can be removed.

Kate (with jid carol@localhost) sometimes receives this:

     {xmlel,<<"presence">>,
         [{<<"type">>,<<"unavailable">>},
          {<<"to">>,<<"carol@localhost/res1">>},
          {<<"from">>,<<"carol@localhost/res1">>}],
         [{xmlel,<<"status">>,[],
              [{xmlcdata,<<"Replaced by new connection">>}]}]}

Are there any plans for writing pep/geoloc tests? We are having some people reporting problems with pep on our network, and it would be nice to prove whether it's the client or server's fault ;-)

Presence stanzas from Carol can be received in next tests.
There are two ways to solve this:

1. split group "moderator" into two: with and without Carol.
2. wait for an empty room in init_per_testcase.

We need tests for this. More information here: http://www.mail-archive.com/[email protected]/msg23590.html

It may require some changes in escalus and MongooseIM as well.

Add test case where xml's content contains some special characters.
See esl/MongooseIM#203 there is example stanza.