From 51b1225fc79b9c24d202efb23a971bfb21540dac Mon Sep 17 00:00:00 2001 From: DMRobertson Date: Tue, 5 Jul 2022 12:25:53 +0000 Subject: deploy: b51a0f4be0287f88a747952fb3cc8132d29df4c8 --- latest/development/contributing_guide.html | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) (limited to 'latest/development/contributing_guide.html') diff --git a/latest/development/contributing_guide.html b/latest/development/contributing_guide.html index 431123734e..3e875cce15 100644 --- a/latest/development/contributing_guide.html +++ b/latest/development/contributing_guide.html @@ -76,7 +76,7 @@ @@ -342,6 +342,18 @@ Here is how to run your local Synapse checkout against your local Complement che

To run a specific test, you can specify the whole name structure:

COMPLEMENT_DIR=../complement ./scripts-dev/complement.sh -run TestImportHistoricalMessages/parallel/Historical_events_resolve_in_the_correct_order
+

The above will run a monolithic (single-process) Synapse with SQLite as the database. For other configurations, try:

+ +

Prettier formatting with gotestfmt

+

If you want to format the output of the tests the same way as it looks in CI, +install gotestfmt.

+

You can then use this incantation to format the tests appropriately:

+
COMPLEMENT_DIR=../complement ./scripts-dev/complement.sh -json | gotestfmt -hide successful-tests
+
+

(Remove -hide successful-tests if you don't want to hide successful tests.)

Access database for homeserver after Complement test runs.

If you're curious what the database looks like after you run some tests, here are some steps to get you going in Synapse:

    -- cgit 1.5.1