Selenium WebDriver 3 was
released three days ago! Since there is 5 years between versions 2 and
3, a lot changes are expected in this major release. For teams with existing
test suite, here comes the question:
Will there will be a lot of work to upgrade existing test
scripts to Selenium WebDriver 3?
My short answer: Selenium WebDriver 3 is a drop-in replacement for
Selenium WebDriver 2.53. As I am a test engineer, my statement is backed by
testing. I executed my test suite for ClinicWise : 520 user
story level Selenium WebDriver test scripts in Ruby.
Before the testing, I upgraded Chrome to the latest version 2.54
and BuildWise Agent1.7 with latest
Selenium-WebDriver 3.0 gem (the latest chromedriver 2.24 is
embedded in BuildWise Agent).
I triggered a build to run all tests (not changed) in BuildWise,
which distributed these 520 tests to 6 BuildWise Agents to run them in
parallel. Here is the result:
All tests pass. In terms of performance, I couldn't compare
precisely because test scripts were assigned to different build machines.
Overall, it seemed slightly faster.
For my another test suite for SiteWise (the content management system I developed), I did
find an issue: a test failure on file uploading in a modal dialog within
unknown error: cannot determine loading status
from unknown error: missing 9aea000394714d2fbb20850021f6204f2256b9cf),platform=Windows NT 6.1.7601 SP1 x86_64)
# ./vendor/source/selenium-webdriver-3.0.0/lib/selenium/webdriver/remote/response.rb:69:in `assert_ok'# ./vendor/source/selenium-webdriver-3.0.0/lib/selenium/webdriver/remote/response.rb:32:in `initialize'
However, I believe this is an issue with the chromedriver with
Chrome 54. The test passed with Chrome 53.
My suggestion: before upgrading to Selenium WebDriver, make sure
test execution of your test suite is reliable (it is easier to say than getting
it done, I know) and lock down the version of Browser and WebDriver (such as
chromedriver). Then upgrade.
Five years after Selenium 2, finally, Selenium WebDriver 3 is released. For testwise users who want to be an early adopter of Selenium WebDriver 3, We release the following TestWise beta versions supporting latest Selenium WebDriver:
There is no built-in support for Selenium WebDriver from Firefox 47+, you need GeckoDriver. Installation of GeckoDriver is the same as ChromeDriver. We received several enquires on TestWise no longer works with Firefox 47+. The solution is to download the working version of GeckoDriver and put it in the PATH.
GeckoDriver is still in beta, and we had issues with one version works on Firefox 47 but not 48. To avoid the hassles for TestWiser Community Edition users, We switched the default (and only) browser to Chrome. This makes sense too, as Chrome is the most used browser and the convenience of built-in support for Firefox no longer exists.
David Thomas, one of Agile Manifesto author, publishd this article Time to kill Agile. He suggested: "So I think it is time to retire the word 'Agile.'". In this recent interview, David Thomas, says This is all to do with the fact that "agile" has become meaningless."
This surely upsets many agile coaches, who makes money with the word 'Agile'. There are surely a few of them are really good and know what they are talking about, but most are not. Let's put it in test, try to answer questions below:
How often do your project release your software?
How do you honestly think customers' confidence on the product?
How do you do regression testing?
The objective of Agile, if my still use this word, is to release software frequently to product with high quality. I think the reason that Agile word lost the meaning due to it does not quantify the "frequently" and "high quality".
High Quality: every release must pass full automated regression tests
Frequently: multiple times a day to production, yes, in a matter of hours.
Sound impossible? Facebook release twices a day, is Facebook doing Agile? Comparing to Facebook, how are you doing Agile? Have a look at the Facebook's test lab:
IE has over 60% browser market (Chrome was just released)
Selenium WebDriver wasn't not released yet
Now Chrome dominates in browsers and Selenium WebDriver dominates web testing, no questions about it. The first editions of PWTA uses RWebSpec, an extension of Watir. In later revisions, I added a chapter for Selenium WebDriver.
For the second edition, I changed sample projects to Selenium WebDriver, as a result, a large percentage of screenshots and test scripts updated. But the essence of the book: maintainble test design and test refactoring remains. I even added more examples of applying these techniques to Watir, RWebSpec and Capybara.
The print version of 2nd edition shall be available next month. If you already purchased the 1st edition of Leanpub ebook, you can get this update free.