61c3a2a2c7
* sliding sync: infer the storage key from the loop id and user id * chore: rename `sync_id` to `id` * chore: check that the sliding sync id is less than 16 chars * chore: rejigger the storage key creation logic Now the prefix is visible only in the `format_storage_key_prefix` function, and other `format_storage_key` function will be based off that. * chore: update sliding sync README with API updates and fix outdated information * chore: clippy + fix test Signed-off-by: Benjamin Bouvier <public@benj.me>
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.