#EJABBERD TEST ESCALUS MAKE QUICKTEST FULL#
#EJABBERD TEST ESCALUS MAKE QUICKTEST CODE#

By changing image: to build: # image: ejabberd/ecs:latest FROM ejabberd/ecs:latestĬhange my docker-compose.yml from using an image to building the Dockerfile.

The test suite is modular and can be run in parts (to focus on a group of features) or run for a specific backend. It also contains tests for the various backends that ejabberd supports. This means I have to build my own container by creating my own build/ejabbed/Dockerfile. This test suite is a set of end-2-end integration tests that act like XMPP clients connecting with the server and is testing ejabberd at the protocol level. Then I have to make the change permanent. It's intended to be used with Common Test. Directly from Escalus README: Escalus is Erlang library for convenient testing of XMPP servers. Now I can see the certificates load without error in the log. 1 Answer Sorted by: 2 I will recommend using Escalus if you are looking to verify correctness of ejabberd modules. A quick proof of this by going into the container and add ca-certificates and restarting ejabberd: docker-compose exec -u root ejabberd sh These are Let’s Encrypt certs and I know they are trusted, so why the error? Turns out the image ejabberd/ecs:latest doesn’t come with any CA certificates. When I started the service it complains that the certificate is signed by an untrusted CA! ejabberd/conf/certs:/home/ejabberd/conf/certs:rw ejabberd/conf/ejabberd.yml:/home/ejabberd/conf/ejabberd.yml:rw ejabberd/upload:/home/ejabberd/upload:rw ejabberd/database:/home/ejabberd/database:rw Ive looked around for some library or framework which provides a repeatable and structured way of doing benchmarking (much like eunit and common tests do for. Which are mounted using my docker-compose.yml ejabberd: home/ejabberd/conf/certs/fullchain.pem Then add in the location of the certs I’m using: certfiles:

# '/.well-known/acme-challenge': ejabberd_acme Should be easy enough, all I have to do is comment out the acme: stanza and the request_handlers:, maybe just the request_handler: would do it. This meant I could switch to the staging ACME, which would mean untrusted CA certificate errors, or use a previously issued certificate set until my blockage was cleared. The server is restarted again.When running the ejabberd docker image in my container set I ran into a problem where I hit the rate limiter on Let’s Encrypt. In the end_per_suite previously backuped config file is restored and The expected certificate files exists and then produces new config file.Īt the end it restart the server so that the new configuration can be applied. The above snippet backups current server's config file, asserts that Make_ejabberd_node_require_starttls( Config) -> ejabberd_node_utils: modify_config_file(, Restore_ejabberd_node( Config) -> ejabberd_node_utils: restore_config_file( Config),Įjabberd_node_utils: restart_application( ejabberd).Īssert_cert_file_exists() -> ejabberd_node_utils: file_exists( ? CERT_FILE) orelse ct: fail( 'cert file ~s not exists ', ). Make_ejabberd_node_require_starttls( Config1),Įjabberd_node_utils: restart_application( ejabberd),

Setup_ejabberd_node( Config0) -> Config1 = ejabberd_node_utils: init( Config0),Įjabberd_node_utils: backup_config_file( Config1), Init_per_suite( Config) -> setup_ejabberd_node( Config).Įnd_per_suite( Config) -> restore_ejabberd_node( Config). In order to do this define configuration variables in nfig file, for example: It is possible to run tests for various ejabberd configurations. Make quicktest TESTSPEC=custom.spec ADD_OPTS='-pa /full/path/to/erlcloud/ebin' Testing various server configurations Of course TESTSPEC and ADD_OPTS can be specified at the same time: Make quicktest ADD_OPTS='-pa /full/path/to/erlcloud/ebin' spec file (for example to add other suites or remove the existing ones) one must add it to one of the mentioned commands:Īdditional erlang binaries required by custom suites can be added to the path by providing ADD_OPTS parameter to the make command.

#EJABBERD TEST ESCALUS MAKE QUICKTEST FULL#

full ( make test) - this command tests all server configurations defined in nfig file - see the section on various server configurationsīy default both commands are using the default.spec file where options like suites to run, config file(s) and log dir are specified.quick ( make quicktest) - this command tests the current configuration of the server.It's used mainly for ESL's branch of ejabberd,īut one that may be reused in other projects.

#EJABBERD TEST ESCALUS MAKE QUICKTEST CODE#

This repository contains test code for ejabberd/MongooseIM.

Ejabberd test escalus make quicktest