The driver's automated tests often execute against a running server instance, and tests often access external resources (i.e. databases, collections, files) by the same name. When tests are executed in parallel (As with ctest -jN), the tests will contend with each other on accessing these resources and cause each other to fail. Tests should either:

• Each access separate resources so as not to contend and allow parallel execution, or
• Declare their intention to use a resource exclusively via CMake's RESOURCE_LOCK and/or RESOURCE_GROUPS test properties.

A simple way to address the former is to have a test mangle the name of the database it uses within a server instance.