Case Study: Integrating Selenium Technologies With Others

tools-and-infrastructure Case Study 45 Mins Advanced test_automation automation_framework remote-web-driver se-builder se-interpreter session-persistence selenium-server selenium-grid selenium-grid-nodes java-rmi 3rd-party-tools java-awt-robot tool-integration
Carl Nagle
Carl Nagle
Principal Software Developer
SAS Institute, Inc

When tasked with producing a comprehensive HTML5 test automation solution for the enterprise we needed to insure we provided extensive value that went well beyond what most existing toolsets individually provided.  We needed to solve some of the most common problems faced by our web testers and developers:

   * Start/Stop shared Selenium browser sessions across different tools with RemoteWebDriver extensions
   * Persist Selenium browser sessions across different testing sessions (tool invocations) with RemoteWebDriver extensions
   * Remove element identification and resolution out of the tests for simpler test maintenance with Maps
   * Automate various test design-time activities for the test developer
   * Simplify common but complex Selenium automation functions for testers with Libraries
   * Intermix Selenium API, 3rd party API, and SeBuilder scripts as needed with SeInterpreter extensions
   * Automatically blend image-based testing with Selenium support where needed (screen/canvas)
   * Automatically blend Selenium support with Java AWT Robot (keyboard/mouse) support where needed
   * Extend the "Selenium with Java AWT Robot" support to remote servers and grid nodes
   * Automatically launch "local" or "remote" Selenium Server, Hub, or Grid nodes if not running


We can discuss each of these issues and how we chose to solve them.  The various solutions along with all source are available as opensource.

 
2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Case Study

Overview each problem and solution for:

   * Start/Stop shared Selenium browser sessions across different tools with RemoteWebDriver extensions
   * Persist Selenium browser sessions across different testing sessions (tool invocations) with RemoteWebDriver extensions
   * Remove element identification and resolution out of the tests for simpler test maintenance with Maps
   * Automate various test design-time activities for the test developer
   * Simplify common but complex Selenium automation functions for testers with Libraries
   * Intermix Selenium API, 3rd party API, and SeBuilder scripts as needed with SeInterpreter extensions
   * Automatically blend image-based testing with Selenium support where needed (screen/canvas)
   * Automatically blend Selenium support with Java AWT Robot (keyboard/mouse) support where needed
   * Extend the "Selenium with Java AWT Robot" support to remote servers and grid nodes
   * Automatically launch "local" or "remote" Selenium Server, Hub, or Grid nodes if not running

Followed by open discussion Q&A

Learning Outcome

Case Study examples of integrating multiple Selenium technologies (Selenium, RemoteWebDriver, SeBuilder, SeInterpreter, Selenium Server, Selenium Grid) with other 3rd party technologies (Java AWT Robot, Java RMI, SAFS, STAF, Eclipse) for comprehensive solutions to HTML5 test automation.

Target Audience

developers, testers, automation engineers, tool integrators, framework itegrators

schedule Submitted 7 years ago

People who liked this proposal, also liked:

  • Herman Ching
    keyboard_arrow_down

    Herman Ching - Using genetic algorithm to do exploratory testing with cucumber and selenium.

    getting-started Experience Report 45 Mins Advanced automation_framework genetic_algorithm cucumber
    Herman Ching
    Herman Ching
    QA Engineer
    Lab49
    schedule 7 years ago
    Sold Out!
    45 Mins
    Experience Report
    Advanced

    Writing selenium tests has an inherent problem in which we can only automate what we know the steps for. It is primarily used for regression and can scale very quickly. We generally optimize regression for sprint's relevant features or have smoke tests to get quicker feedback. In addition negative testing is very expensive to write. This entire process is very manual and the maintenance of tests become more costly than the actual writing of tests. 

    We can change this. By using genetic algorithm and cucumber steps we can create new feature files to discover where in the application may be be problematic. The goal of each individual would be to find the most defect. The two individuals that find the most defects then create children that follows the sequences of how new individuals are form through genetic algorithms. They will breed the next generation of testers which will focus on problematic areas. 

    Let's find out when and if this strategy can be deemed effectively. 

    5 comments
    View Details play_arrow
Selenium Conf 2015

Portland, OR, USA

Tue, 8th - Thu, 10th Sep 2015

email Contact Us
Active Members
help