@@ -40,6 +40,9 @@ about the types of tests and how to run them.
4040 - [ Kerberos Tests] ( #kerberos-tests )
4141 - [ AWS Authentication tests] ( #aws-authentication-tests )
4242 - [ Container Tests] ( #container-tests )
43+ - [ GCP] ( #gcp )
44+ - [ Azure] ( #azure )
45+ - [ AWS] ( #aws )
4346 - [ TODO Special Env Sections] ( #todo-special-env-sections )
4447 - [ Testing driver changes with mongosh] ( #testing-driver-changes-with-mongosh )
4548 - [ Point mongosh to the driver] ( #point-mongosh-to-the-driver )
@@ -76,7 +79,7 @@ The actual implementations of the spec tests can be unit tests or integration te
7679
7780## Running the Tests Locally
7881
79- The easiest way to get started running the tests locally is to start a standalone server and run all of the tests.
82+ The easiest way to get started running the tests locally is to start a replica set and run all of the integration tests.
8083
8184Ensure the drivers tools submodule is cloned:
8285
@@ -85,16 +88,28 @@ git submodule init
8588git submodule update
8689```
8790
88- Start a ` mongod ` standalone with our [ run-orchestration.sh ] ( .evergreen/run-orchestration.sh ) script with the environment set for the cluster :
91+ Set the ` DRIVERS_TOOLS ` environment variable :
8992
9093``` sh
91- VERSION=' latest' ' server' ' noauth'
94+ export DRIVERS_TOOLS=< path to driver> /drivers-evergreen-tools
95+ ```
96+ 97+ Start a replica set with our [ run-orchestration.sh] ( .evergreen/run-orchestration.sh ) script with the environment set for the cluster:
98+ 99+ ``` sh
100+ VERSION=' latest' ' replica_set'
101+ ```
102+ 103+ Load the new cluster's URI into the environment:
104+ 105+ ``` sh
106+ source mo-expansion.sh
92107```
93108
94109Then run the tests:
95110
96111``` sh
97- npm test
112+ npm run check: test
98113```
99114
100115> ** Note:** the command above will run a subset of the tests that work with the standalone server topology since the tests are being run against a standalone server.
0 commit comments