Closed tvdeyen closed 5 years ago
I'm not sure about this.
I like the idea to allow use a different driver than poltergeist, but I don't think the best way should be try to match any specific driver.
Instead we can create a different helper for each driver, and let the user load the driver he prefer.
Instead we can create a different helper for each driver, and let the user load the driver he prefer.
@ccarruitero I like that idea, but currently we hard coded poltergeist
and are forcing every extension that uses this feature helper to also install the poltergeist
gem. This is mainly a hotfix for that problem. Contributions to separate the adapter code from the rspec feature spec setup code is more then welcome.
Also, which other driver could be added? In the supported drivers list:
RackTest
does not support jsCapybara-webkit
is going EOLSo at the moment I think there are no other option.
@kennyadsl give approval?
@tvdeyen sure, it’s already approved!
@kennyadsl ah, dang, we need a second one, right? :)
Closed in favour of #16
Instead of having a hard dependency to poltergeist for extensions feature specs, we allow to use selenium-webdriver as well. Error out with warning if non of them are present.