-
Notifications
You must be signed in to change notification settings - Fork 77
feat: Introduce dual testing with redis and bitmapist-server #84
New issue
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
Conversation
Since the tests now support a previously running instance of the backend, this introduces a protection in case the tests get accidentally connected to production data.
We only need the dev group and: https://docs.astral.sh/uv/concepts/projects/sync/#syncing-development-dependencies > The dev group is special-cased and synced by default.
|
Adding @lukemerrett as a reviewer as he took an interest in going deep into |
modasserbillah
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a test only change and CI already ran the tests on both redis and bitmapist. So, it looks safe and functioning to me. Thanks @jacobo-doist 🎉
|
Thank you @modasserbillah 🙏 |
|
Awesome, thank you for the turnaround on this @jacobo-doist ! |
Tests now run against both Redis and bitmapist-server backends.
Changes
test/conftest.pyto run tests with both backendsdocker-compose.ymlwithredis:7-alpineandbitmapist-server:v1.9.8Testing