mongo/docs/testing
Sean Lyons e3b66da58e SERVER-109274 Use SIGABRT to dump cores when a debugger is not found (#41844)
GitOrigin-RevId: e140215e33b9bfda7cc5474cb59d9ac2eb29029b
2025-09-29 16:24:49 +00:00
..
OWNERS.yml SERVER-107550: Seed readme docs for resmoke-related tooling (#38540) 2025-07-16 21:10:31 +00:00
README.md SERVER-107550: Seed readme docs for resmoke-related tooling (#38540) 2025-07-16 21:10:31 +00:00
fsm_concurrency_testing_framework.md SERVER-100525: Audit unowned files for StorEx ownership (#34306) 2025-04-10 04:44:12 +00:00
hang_analyzer.md SERVER-109274 Use SIGABRT to dump cores when a debugger is not found (#41844) 2025-09-29 16:24:49 +00:00
otel_resmoke.md SERVER-106150 Rewrite private links to public links when we sync source code from 10gen/mongo to mongodb/mongo (#37153) 2025-06-12 18:23:51 +00:00
resmoke_modules.md SERVER-108972: Support loading resmoke libs and suites from module directories (#40272) 2025-08-19 21:25:48 +00:00

README.md

Testing

Most tests for MongoDB are run through resmoke, our test runner and orchestration tool. The entry point for resmoke can be found at buildscripts/resmoke.py

Concepts

Learn more about related topics using their own targeted documentation:

  • resmoke, the test runner
  • suites, how tests are grouped and configured
  • fixtures, specify the server topology that tests run against
  • hooks, logic to run before, after and/or between individual tests

Basic Example

First, ensure that your python venv is active and up to date:

python3 -m venv python3-venv
source python3-venv/bin/activate
buildscripts/poetry_sync.sh

and you've built the source binaries to run against, eg:

bazel build install-dist-test

Now, run the test content from one test file:

buildscripts/resmoke.py run --suites=no_passthrough jstests/noPassthrough/shell/js/string.js

The suite defined in buildscripts/resmokeconfig/suites/no_passthrough.yml includes that string.js file via glob selections, specifies no fixtures, no hooks, and a minimal config for the executor.