Carl Nagle
Principal Software Developer
SAS Institute, Inc
location_on United States
Member since 7 years
Share
Carl Nagle
Specialises In (based on submitted proposals)
Carl Nagle, SAS Institute Inc.
A Principal Software Developer at SAS Institute focusing for the past 17 years on the development, integration, and evolution of enterprise software test automation tools. The Project Lead for the opensource SAFSDEV project on SourceForge. For more than 30 years Carl has been responsible for the engineering of both hardware and software testing systems. This incluces the design and engineering of advanced electronics for analog and digital subsystems testing with embedded firmware for high-end power generation and communications systems. This naturally evolved, over technological time, into the development of advanced software testing systems and frameworks. Carl and his team thrive on solving "impossible" test automation scenarios across multiple processes, platforms, and technologies.
-
keyboard_arrow_down
Case Study: Integrating Selenium Technologies With Others
45 Mins
Case Study
Advanced
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. -
-
No more submissions exist.
