That’s cool. I wonder if it is possible to have concurrent tests, where each of those tests is running in an isolated database container. As far as I know, Ecto can spawn only one connections pool, that is using one port
hst337
jarlah
Testcontainers for Elixir has module Testcontainers.Ecto. The purpose of this is to start a container, override ecto repo config and shutdown repo and container on system/test exit. The module will temporarely override the configured port with the dynamic host port of the container. So technically (not tested) if you have multiple repos you can run postgres_container for each repo.
0
jarlah
hst337
I meant to ask if it is possible to run two or more tests at the same, while both of them are using the same Repo module, but each of this tests is connected to it’s own testcontainer with db. I guest that it is not possible, since Ecto Repo is a singletone, right?
0
ziinc
That is contradictory to the point of the library, which is to provide full container and service isolation for e2e testing.
0
akash-akya
Not really an answer to your exact question, but we had a similar issue of running tests in parallel in my last job, and we solved it by using a different database for each db connection in the pool.
I wrote about it a bit here - Experimenting with running mysql tests in parallel
Initially I was going to suggest configure option to switch server, but realized that configure hook only comes into play after it is connected to DB, so we can’t really use it to switch different db server running at different port
UPDATE: on second look, you should be able to configure to switch to a different DB server running on a different port for every connection (haven’t tested)
0
jarlah
Maybe you could outline the problem a bit more ? In GitHub actions you can run the tests in partitions, effectively in parallell.
EDIT: You dont have to use partitioning on database name with Testcontainers. Its a new database for each time tests is run in GitHub actions. So Even if its the same database name in every parallell workflow run its different database server
0
