-
Notifications
You must be signed in to change notification settings - Fork 545
Testing (legacy)
If you contribute to the C++ driver, you'll need to test your changes. The driver comes with a number of tests to ensure its functionality and performance. There are a few different kinds of tests within the driver's codebase.
Note: if you are running OS X Mavericks or above, you may need to include the --osx-version-min=10.9 flag to the commands below.
Unit tests do not require a running mongod, and in fact will not run if you have a mongod running locally on port 27000. These tests are designed to test individual components of the driver in isolation, and the test files are found in the same directory as the things they test (so, bson_validate.cpp and bson_validate_test.cpp are both found in src/mongo/bson). The different unit tests are listed here.
Build all the unit tests with scons:
> scons build-unit
Build and run all the unit tests:
> scons unit
Build an individual unit test:
> scons build-full/test/name
Build and run an individual unit test:
> scons run-full/test/name
Integration tests require a local mongod to be running on port 27999. These tests are located in src/mongo/unittest. Additionally, some tests require the parameter enableTestCommands to be set.
Example mongod invocation to be executed prior to running integration tests:
> mongod --port 27999 --setParameter enableTestCommands=1
There is a list of the different integration tests here.
Build all the integration tests:
> scons build-integration
Build and run all the integration tests:
> scons integration
Individual integration tests can be run in the same way as individual unit tests, shown above.
Note: to run the SASL integration tests, you should build with the --use-sasl-client flag.
The driver includes a number of example programs of its use. The examples are listed here, and the source files are found in src/mongo/client/examples. The examples expect a mongod to be running locally on port 27999.
Build the examples with scons:
> scons build-examples
Build and run the examples:
> scons examples
Run the unit tests, integration tests, and examples with scons:
> scons test
--cache - use an object cache for builds.