Closed nathany closed 8 years ago
Similar situation -- I'm working on making more of my tests async and Ecto 2.0. I'm currently using solutions in my PRs #44 and #45:
MyApp.TestingAdapter
that has similar contents to what you have there, with the Repo hardcoded in. My rationale for not patching Mailman for this was because Mailman should not be dependent on Ecto.Thanks.
I agree it makes sense to not depend on Ecto. Does using independent test processes have any significant impact on how quickly tests run?
In my case, it's speeding tests up because the central TestServer was the bottleneck when doing a bunch of mailer tests in parallel.
Very nice. Thanks a bunch.
I'm gonna close this issue since you're obviously on top of it.
When upgraded a Phoenix project to Ecto 2.0-beta.2 we see the following error in our mailer tests:
There are two solutions to this issue, as documented in Ecto.Adapters.SQL.Sandbox.
For now we're using Shared mode, which works but runs the mailer tests synchronously. To have all the tests run concurrently, we could use Allowances in TestingAdapter:
We've tested this out, but with the name of our Repo hard coded. Do you think it would be possible to get this working?