CodernityDB / docs / how_its_tested.rst

How it's tested

We use pytest with pytest-xdist to distribute the tests to multiple CPUs.

What's also worth to note, we tests CodernityDB on python 2.6.x, 2.7.x, pypy (1.9 and dev branch) using Tox, and Jenkins takes care about continuous testing process.

All major parts of CodernityDB has their own test suite. We also test CodernityDB single-thread, multiple-thread (thread-safe, and super-thread-safe) and the gevent one.

There are some patch mechanizm / locks so running the test suite in wrong combination might report wrong results.


Running default test suite on your hardware will cause a lot of IO operations and intense CPU work for several minutes (depends on your hardware). Really do not run tests suite on environments with less than 4 cpu cores without clock at least 2.5GHz, also if you run SSD for personal use, use ramcache instead. Test suite performs more than 24 000 000 system calls to write, read, lseek.


For more details visit or clone our |cdb_repo| and check tox.ini and pytest.ini files.

Whole test suite contains a lot of different tests, that covers naturally all database functions, and probably most of use-cases of them.

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.