-
Notifications
You must be signed in to change notification settings - Fork 16
Description
Hi there,
I'm currently experimenting with docker images and found that it is really hard to use capybara while running the browser in one of the selenium provided docker images e.g. this one.
I'm not entirely sure it's a real problem as on an integration server you would probably just run both the tests and the browsers either in the same image or in two images whose runtime is managed by the build service anyway.
However, in my local environment where I have pytest starting and stopping the docker container as a fixture, I have run up against the problem that capybara-py tries to exit the browser in a atexit() handler. This is very nicely test framework independent, but also really hard to extend, as I cannot easily schedule a fixture cleanup after that particular atexit() handler.
Is there a way that I'm missing to control when capybara tries to kill the browser? Ideally I could control the lifetime of the browser from a fixture too, as that would give natural control to me.