Skip to content

Commit 517da84

Browse files
docs: add info about testing with different versions and the rosetta setup for Mac (#4707)
1 parent 252dab8 commit 517da84

File tree

2 files changed

+10
-4
lines changed

2 files changed

+10
-4
lines changed

.evergreen/run-orchestration.sh

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,9 @@ echo "MONGODB_VERSION=${VERSION}"
99
export TOPOLOGY=${TOPOLOGY}
1010
echo "TOPOLOGY=${TOPOLOGY}"
1111

12+
export ARCH=${ARCH}
13+
echo "ARCH=${ARCH}"
14+
1215
export AUTH=${AUTH}
1316
echo "AUTH=${AUTH}"
1417

test/readme.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -118,6 +118,8 @@ npm run check:test
118118
> [!NOTE]
119119
> 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.
120120
121+
[../drivers-evergreen-tools/.evergreen/run-orchestration.sh](../drivers-evergreen-tools/.evergreen/run-orchestration.sh) has a number of settings that can enabled using env vars. Take a look at that script/repo for more information.
122+
121123
The output will show how many tests passed, failed, and are pending. Tests that we have indicated should be skipped using `.skip()` will appear as pending in the test results. See [Mocha's documentation][mocha-skip] for more information.
122124

123125
In the following subsections, we'll dig into the details of running the tests.
@@ -130,6 +132,7 @@ By default, the integration tests run with auth-enabled and the mongo orchestrat
130132
AUTH='noauth' TOPOLOGY='server' bash .evergreen/run-orchestration.sh
131133
AUTH='noauth' npm run check:test
132134
```
135+
133136
### Testing Different MongoDB Topologies
134137

135138
As we mentioned earlier, the tests check the topology of the MongoDB server being used and run the tests associated with that topology. Tests that don't have a matching topology will be skipped.
@@ -509,7 +512,7 @@ The following steps will walk you through how to run the tests for CSFLE.
509512
```bash
510513
npm install mongodb-client-encryption
511514
```
512-
> [!NOTE]
515+
> [!NOTE]
513516
> If developing changes in `mongodb-client-encryption`, you can link it locally using `etc/tooling/fle.sh`.
514517
515518
2. Load FLE credentials and download crypt_shared
@@ -521,8 +524,8 @@ source .evergreen/setup-fle.sh
521524
```
522525
523526
> [!NOTE]
524-
> By default, `setup-fle.sh` installs crypt_shared. If you want to test with mongocryptd instead, set the RUN_WITH_MONGOCRYPTD environment variable before
525-
> sourcing `setup-fle.sh`.
527+
> By default, `setup-fle.sh` installs crypt_shared. If you want to test with mongocryptd instead, set the RUN_WITH_MONGOCRYPTD environment variable before
528+
> sourcing `setup-fle.sh`.
526529
527530
3. Run the functional tests:
528531
```bash
@@ -550,7 +553,7 @@ All of this is handled in the csfle/azurekms and csfle/gcpkms folders in drivers
550553
551554
#### Azure KMS
552555
553-
1. Provision an Azure server. You must set the `AZUREKMS_VMNAME_PREFIX` variable:
556+
1. Provision an Azure server. You must set the `AZUREKMS_VMNAME_PREFIX` variable:
554557
555558
```bash
556559
export AZUREKMS_VMNAME_PREFIX: "NODE_DRIVER"

0 commit comments

Comments
 (0)