Files
matrix-rust-sdk/testing/matrix-sdk-integration-testing
Jonas Platte f2c569440e ui: Remove transaction ID parameter on Timeline methods
There is no reason for it to be configurable in the high-level API,
since the timeline manages local echoes automatically.
2023-09-25 16:50:59 +02:00
..
2023-09-20 14:19:06 +02:00

Matrix SDK integration test

Requirements

This requires a synapse backend with a ci patched configuration. You can easily get it up and running with docker-compose via:

docker-compose -f assets/docker-compose.yml up -d
docker-compose -f assets/docker-compose.yml logs --tail 100 -f

Patches You can see the patches we do to configuration (namely activate registration and resetting rate limits), check out what assets/ci-start.sh changes.

Running

The integration tests can be run with cargo test or cargo nextest run.

The integration tests expect the environment variables HOMESERVER_URL to be the HTTP URL to access the synapse server and HOMESERVER_DOMAIN to be set to the domain configured in that server. If you are using the provided docker-compose, the default will be fine.

Maintenance

To drop the database of your docker-compose run:

docker-compose -f assets/docker-compose.yml stop
docker volume rm -f assets_matrix-rust-sdk-ci-data

or simply:

docker-compose -f assets/docker-compose.yml down -v