-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Possible incompatibility w/ other gems that work using "parallel_tests" #4
Comments
I removed usage of
|
Thanks for reporting this issue. Are you using a single database for all workers? |
@spemmons For me, I was able to get
Naturally you can remove the
|
In my experience there is enough variation in how to structure tests that I think providing a hook is probably the most generic option. Not all tests require separate databases or a test index. However we could consider providing it by default... I don't think we should expose this by default if it means people come to rely on it though. |
@ioquatix How would you configure workers to use separate databases currently? |
@aaronchi as I understood similar to the parallel_tests (https://github.com/grosser/parallel_tests#add-to-configdatabaseyml), you have to add set env variable: #4 (comment) and then use it in the database.yml (for activerecord). |
Seems like a nice approach, but I'm wondering if it is incompatible with some test gems.
In my case, I'm seeing errors like this
A gem called
database_cleaner
seems to be at fault. Need to review this gem to see if we can do something else...Thoughts?
The text was updated successfully, but these errors were encountered: