Ferrum vs Selenium #560
nicksterious
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Are the authors interested in wider adoption of Ferrum?
Without aiming to build a "drop-in replacement" for Selenium, is there any chance some of the methods can be renamed or at least aliased to use names/arguments similar to selenium?
eg
would have an alias
These do the same thing in both gems yet the syntax is different. #find_element is probably one of the most used method in pretty much every application.
Only asking because at this point most applications are built around Selenium in lack of alternatives and it may be possible to improve developer experience by reducing the friction associated with moving to Ferrum.
Of course nothing's stopping people from building their own wrappers or monkey patching or yet this would mean a lot of migrations would end up on a "later to-do" list rather than "something I can do tomorrow between lunch and tea".
I think Ferrum is very promising, I've spent the better part of this week refactoring some old code to use Ferrum instead of Selenium and found some significant advantages including major boost in performance. Would be nice if other people would decide to step forward from dinosaur age into the light but I realize not everyone might be ready to dedicate time to rewrite/refactor their stuff sooner rather than later.
Thank you for the great work you guys did so far & will be sponsoring the project starting with v1.0!
Beta Was this translation helpful? Give feedback.
All reactions