History

Jonas Platte 6e15e34700 Use bool::then where applicable		2023-09-26 10:14:04 +02:00
..
assets	tests(notification): add integration tests for notification events	2023-08-04 17:41:47 +02:00
src	Use bool::then where applicable	2023-09-26 10:14:04 +02:00
.gitignore	chore: use local volumes for testing server	2023-01-31 14:03:43 +00:00
Cargo.toml	tests(notification): add integration tests for notification events	2023-08-04 17:41:47 +02:00
README.md	chore: use local volumes for testing server	2023-01-31 14:03:43 +00:00

README.md

Matrix SDK sliding sync integration test

A test harness and tests for integration testing sliding sync against a full synapse server and sliding sync proxy

Requirements

This requires a synapse backend with a ci patched configuration and a sliding-sync-proxy. 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 down -v

Then remove the local data stored at ./data.