Running tests
We are currently working on adding tests to the codebase. You can run the tests with:
Test requirements
Tests currently require the Kafka, Valkey, and Mongo Docker containers to be running. You can start these services using Docker Compose:
docker compose --profile api up -d
When running the tests, the config file found in tests/config.test.yaml will be used.
Test configuration
The test suite uses a dedicated configuration file separate from the main application config. This ensures that tests run in isolation and don’t interfere with your development environment.
Test configuration file
The test configuration is located at:
This file contains test-specific settings for connecting to the Docker services and other test parameters.
Continuous integration
The test suite runs automatically on every push to the repository and on every pull request. You can check the status of the tests in the “Actions” tab of the GitHub repository.
Make sure all tests pass before submitting a pull request.
Running tests during development
Start Docker services
Ensure the required Docker containers are running:docker compose --profile api up -d
Verify containers are healthy
Check that all containers are running properly: Running specific tests
You can run specific tests by providing a filter pattern:
cargo test <test_name_pattern>
Test output
By default, Cargo captures test output. To see all output including println! statements:
cargo test -- --nocapture
Building for tests
If you want to build the test binaries without running them: