You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 18, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+38Lines changed: 38 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,3 +112,41 @@ fn main() {
112
112
...
113
113
}
114
114
```
115
+
116
+
Testing
117
+
-------
118
+
119
+
The driver test suite is largely composed of integration tests and behavioral unit-tests, relying on the official [MongoDB specifications repo](https://github.com/mongodb/specifications).
120
+
121
+
The easiest way to thoroughly test the driver is to set your fork up with TravisCI. However, if you'd rather test the driver locally, you'll need to setup integration and specification tests.
122
+
123
+
> NOTE: Each integration test uses a unique database/collection to allow tests to be parallelized, and will drop their dependencies before running. However, effects are _not_ cleaned up afterwards.
124
+
125
+
#### Setting up integration tests
126
+
127
+
All integration tests run on the default MongoDB port, 27017. Before running the tests, ensure that a test database is setup to listen on that port.
128
+
129
+
If you don't have mongodb installed, download and install a version from [the MongoDB Download Center](https://www.mongodb.com/download-center). You can see a full list of versions being tested on Travis in [the travis config](/.travis.yml).
130
+
131
+
After installation, run a MongoDB server on 27017:
132
+
133
+
```
134
+
mkdir -p ./data/test_db
135
+
mongod --dbpath ./data/test_db
136
+
```
137
+
138
+
#### Setting up the specifications submodule
139
+
140
+
Pull in the specifications submodule at `tests/json/data/specs`.
0 commit comments