Skip to content

DRIVERS-2985 Include empty case in client metadata tests #1840

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
+10 −8
Closed

DRIVERS-2985 Include empty case in client metadata tests #1840

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 10 additions & 8 deletions source/mongodb-handshake/tests/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

### Test 1: Test that environment metadata is properly captured

Drivers that capture values for `client.env` should test that a connection and hello command succeeds in the presence of
Drivers that capture values for `client.env` should test that a connection and hello command succeed in the presence of
the following sets of environment variables:

1. Valid AWS
Expand Down Expand Up @@ -76,7 +76,7 @@ the following sets of environment variables:

### Test 2: Test that the driver accepts an arbitrary auth mechanism

1. Mock the server response in a way that `saslSupportedMechs` array in the `hello` command response contains an
1. Mock the server response in a way that the `saslSupportedMechs` array in the `hello` command response contains an
arbitrary string.

2. Create and connect a `Connection` object that connects to the server that returns the mocked response.
Expand All @@ -93,8 +93,8 @@ test-only backdoor mechanism to intercept the handshake `hello` command for veri
Drivers should verify that metadata provided after `MongoClient` initialization is appended, not replaced, and is
visible in the `hello` command of new connections.

There are multiple test cases parameterized with `DriverInfoOptions` to be appended after `MongoClient` initialization.
Before each test case, perform the setup.
There are multiple test cases with `DriverInfoOptions` parameters to be appended after `MongoClient` initialization.
Before each test case, perform the following setup.

#### Setup

Expand Down Expand Up @@ -124,6 +124,7 @@ Before each test case, perform the setup.
| 2 | framework | 2.0 | null |
| 3 | framework | null | Framework Platform |
| 4 | framework | null | null |
| 5 | null | null | null |

#### Running a test case

Expand All @@ -148,15 +149,15 @@ Before each test case, perform the setup.

- All other subfields in the `client` document remain unchanged from `initialClientMetadata`.

## Test 2: Multiple Successive Metadata Updates
### Test 2: Multiple Successive Metadata Updates

Drivers should verify that after `MongoClient` initialization, metadata can be updated multiple times, not replaced, and
is visible in the `hello` command of new connections.

There are multiple test cases parameterized with `DriverInfoOptions` to be appended after a previous metadata update.
Before each test case, perform the setup.
There are multiple test cases with `DriverInfoOptions` parameter to be appended after a previous metadata update. Before
each test case, perform the following setup.

### Setup
#### Setup

1. Create a `MongoClient` instance with:

Expand Down Expand Up @@ -184,6 +185,7 @@ Before each test case, perform the setup.
| 2 | framework | 2.0 | null |
| 3 | framework | null | Framework Platform |
| 4 | framework | null | null |
| 5 | null | null | null |

#### Running a test case

Expand Down
Loading