18. 10/28/2014
First, pick engine(s)
Gotchas:
• IE can only run reliably on a Windows OS
Ramification: testing solution requires Windows
• Latest Safari will only run on Mac hardware
Ramification: no AWS option and good luck hosting a
Mac in the UITS server room…
19. 10/28/2014
Next, pick driver
Gotchas:
• IE Compatibility Mode is not reliable: http://stackoverflow.com/a/11418046
• TrifleJS is “very much in beta” and cannot emulate
versions on Windows Server 2012
• WebDriver is slow
• Node.js solutions target a specific layout engine
• Very little Sahi documentation and small community
24. 10/28/2014
Why bother?
- Jackson Murtha
http://iterate.blendinteractive.com/preventing-upgrade-headaches-with-selenium-webdriver/
25. 10/28/2014
Making the right choice
• Avoid choice paralysis http://addyosmani.com/blog/front-end-choice-paralysis/
“The challenge is that when presented with an abundance of choice, you
can feel increasingly unsure of whether yours is the right one. Instead of
being happy with our decisions, we’re filled with anxiety. Did I pick the
wrong one? Would I have been better off with something else? What
would my friends have used? ... If you’re an experienced developer
speaking to someone stuck on a decision, try to help them simplify their
options.” - Addy Osmani
• Unit vs. Functional http://www.helpscout.net/blog/functional-testing-casperjs/
“No one cares that your Unit tests are passing if your application doesn’t
function. Unit testing makes sure you are using quality ingredients.
Functional testing makes sure your application doesn't taste like crap. ...
[In] the real world, most developers barely have time for one kind of
automated test, let alone two. If that describes you, I would strongly
encourage you to go with Functional testing.” - Brett Jones
27. 10/28/2014
Eas(ier) Button
• Getting a test environment up and running is half
the battle. Do yourself a favor and just pay out.
• If getting budgetary approval is akin to an act of
Congress, at the very least use our AWS
CloudFormation template:
https://bitbucket.org/uitsweb/selenium-grid-ec2
35. 10/28/2014
Next Steps
• Update Selenium Grid template to use NAT private
subnet
• Firewall exception to allow AWS Selenium Grid to
access test sites (or use SSH reverse proxy)
• Update Selenium Grid template to use Modern.IE VMs
• Drush script for dynamically obtaining top menu links
• Update our Drupal automation tool to launch (and
respond to) automated testing of top site pages
• Set up Appium on Mac OS X server and arrange colo
• Profit!
