7 Commits

Author	SHA1	Message	Date
David Robertson	9982ab24ee	Use different device names for each test	2023-05-15 19:14:09 +01:00
David Robertson	af893f526b	update tests	2023-04-04 22:25:39 +01:00
Kegan Dougal	ca6ceb28da	BREAKING: Change the API to refer to lists by keys not index positions ... This provides more flexibility to refer to lists as well as delete them.	2022-12-20 13:32:39 +00:00
Kegan Dougal	aa28df161c	Rename package -> github.com/matrix-org/sliding-sync	2022-12-15 11:08:50 +00:00
Kegan Dougal	f4a5200150	bugfix: ensure room name calculation updates are correct ... Previously we would fail to update to the correct room name because we didn't remove the client from the list of Heroes.	2022-09-07 15:26:46 +01:00
Kegan Dougal	5b0e8568ea	tests: move Match* functions to testutils/m ... In preparation for migrating end-to-end style integration tests to be actual end-to-end tests. The intended split is: - Does the test exclusively use the public sliding sync API for test assertions? - Does the test exclusively use the public sync v2 API for configuring the test? If the answer to both questions is YES, then they should be end-to-end tests. Some examples of this include testing core functionality of the API like room subscriptions, multiple lists, filters, extensions, etc. Some examples of tests which are NOT end-to-end tests include: - Testing connection handling (e.g sending multiple duplicate requests) - Ensuring outstanding requests get cancelled. - Testing restarts of the proxy. - Testing out-of-order responses. - Benchmarks. These all involve configuring the test / asserting different things, which would be extremely difficult to reliably engineer using a real homeserver.	2022-07-26 10:11:06 +01:00
Kegan Dougal	75c3579f9e	refactor: move integration tests to tests-integration directory ... Add tests-e2ee directory for end-to-end tests which require a synapse server.	2022-07-25 15:06:13 +01:00