Closed nottoseethesun closed 10 years ago
interesting, yes we can add the support, However I would like to understand what makes camme-webdriverjs easier than Selenium webdriverjs ? Can you please give us more details on that ?
In Selenium webdriverjs, it's comparatively hard to do jobs such as text extraction from an html element. Fortunately, that sort of thing is possible in browser-side code (such as when using yui tests). But not all such code should go in the actual assertion modules.
Also, the camme/webdriverjs has just about every convenience method possible, where Selenium webdriverjs has the bare minimum. It is also terse, compared to Selenium webdriverjs.
Also, with camme/webdriverjs , the target javascript context (the web app's) is left untouched, as anything a test would need to do can be done from the nodejs context when using the camme/webdriverjs .
Although test code is fairly lightweight and non-intrusive, the camme/webdriverjs enables complete confidence that the test target is unmodified by test code.
Closing this issue since this particular discussion has come to a close.
I find writing tests with the camme/webdriverjs to be much easier than with Selenium's webdriver. Does Arrow support it or can it be easily switched to support it?
If not, the team may want to consider adding support for https://github.com/camme/webdriverjs .