-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: Testing
-
None
Replace the existing Atlas test with running the full test suite against an Atlas deployment.
The current Atlas test setup runs the following checks, both with the standard client configuration and with clientOpts.TLSConfig.InsecureSkipVerify = true set.
- Sends legacy hello to "test" database.
- Calls FindOne on "test" collection in the "test" database with filter
{"x": 1}
Those
Some tests cannot be run against Atlas and must be skipped:
- Server failpoints are not supported on Atlas, so exclude any tests that require failpoints from running on Atlas.
Some blockers that need to be resolved:
- Currently, the Atlas deployments are shared CI test environments for all drivers. We need to either create/destroy deployments for each test run or update the tests to prevent database/collection name collisions.
Definition of done:
- The "Atlas test" Evergreen CI task runs the full "standard" test suite (minus the exceptions above) against Atlas instead of a simple hello/find check.
- Remove the existing mongo/testatlas package.
- Add at least one test that tests connecting and querying an Atlas cluster with clientOpts.TLSConfig.InsecureSkipVerify = true set.