Not sure if applicable, but something I've stumbled upon recently: https://testcontainers.com/. See: - https://testcontainers-python.readthedocs.io/en/latest/README.html - https://testcontainers-python.readthedocs.io/en/latest/mongodb/README.html
Perhaps this can help in the subject of this ticket. --- **[tickets:#8065] Run tests with real mongo?** **Status:** open **Milestone:** unreleased **Created:** Thu Mar 10, 2016 10:23 PM UTC by Dave Brondsema **Last Updated:** Thu Mar 10, 2016 10:23 PM UTC **Owner:** nobody We should consider running our test suite with a real mongo database, it would allow better testing of mongo details, for example `aggregate()` calls which `mim` (mongo in memory) cannot emulate at this point. Several things would have to change: * specify real databases in `test.ini` * update `Allura/allura/websetup/bootstrap.py`'s `wipe_database` method to include those database names * make the database names semi-random and distinct so that running the tests in a multiprocess configuration don't use the same db and clobber each others' changes. (`mim` is already isolated per-process since its in memory) * update jenkins to have a real mongo available for tests "mim" is also a bit faster. In my single-process test run it was 70% the time of real mongo. So we'd be sacrificing some speed. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
