![]() When the spec is complete, a useful set of automation “atoms†will be in place for the next generation of browser automation to build upon. The Selenium team have been involved with that effort too. All the major browser vendors have their own implementations already up and running. The W3C “WebDriver†specification is nearing the end of its “Candidate Recommendation†period, and should become a standard soon. The new Selenium 3.5 release contains a lot of work to make the standalone server work seamlessly with the w3c version of the protocol, which was one area of roughness. ![]() This is the 3rd tutorial in our multi-part Selenium Tutorials series. With the latest releases, it’s at least as good as the old Firefox driver. In this Selenium IDE Tutorial learn Selenium IDE commands with examples on the Firefox browser: This tutorial is by far one of the most important tutorials to get a hold on Selenium IDE. I don’t think your information about geckodriver is accurate. The fine people at Applitools are helping with this effort. The second thing is that there is an effort to rebuild IDE using modern APIs, to be usable across more than just Firefox. ![]() So what can we do to move forward? The first thing is that there are now a wealth of tools that are stepping up to fill the gap.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |