We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We would like to make our testing environment as isolated as much as possible.
To start with, we should run mongodb in a dedicated container and clean its state for each test.
Eventually we will need to integrate more 3rd-party components and docker-based test fixtures will help use a lot.
Use docker-compose or similar to set up clear testing environment, pinning all dependencies. Add component in the compose.yaml file corresponding to all bits and pieces. Can be based on https://github.com/SuperDuperDB/superduperdb-stealth/blob/main/tests/material/supervisord/supervisord.conf.
Currently we have an environment variable SUPERDUPERDB_TEST_REMOTE to toggle integration tests on-off. Potentially necessary to refactor.
SUPERDUPERDB_TEST_REMOTE
The text was updated successfully, but these errors were encountered:
thejumpman2323
No branches or pull requests
Why
We would like to make our testing environment as isolated as much as possible.
To start with, we should run mongodb in a dedicated container and clean its state for each test.
Eventually we will need to integrate more 3rd-party components and docker-based test fixtures will help use a lot.
How
Use docker-compose or similar to set up clear testing environment, pinning all dependencies. Add component in the compose.yaml file corresponding to all bits and pieces. Can be based on https://github.com/SuperDuperDB/superduperdb-stealth/blob/main/tests/material/supervisord/supervisord.conf.
Currently we have an environment variable
SUPERDUPERDB_TEST_REMOTE
to toggle integration tests on-off. Potentially necessary to refactor.What
The text was updated successfully, but these errors were encountered: