Tek Fusion Global, a small company, was required by their U.S. Army contract to validate more than 700 scenarios in their mission-planning mobile application. Performing this validation manually was taking multiple human testers several days to complete. After Chris automated not only the steps to run all these scenarios, but also all the data collection and reporting, this previously monumental time investment shrank to a couple of hours. As a result, the company never had to worry about a delayed release or derailing their other testing efforts again!

At Leidos, a need had been established for automated testing on software for the U.S. Air Force. The issue? No personnel familiar with how to start. Chris quickly laid out the structure, methodology, and best-practices for creating and maintaining automated tests and how to fit automation into their workflow and company structure. What resulted from his efforts were traditional developers writing automated tests, manual testers educated on how to run automated tests, and dev ops able to incorporate nightly test runs into a new CI/CD pipeline. This zero-to-automation-hero story took less than two months to start yielding results!

Engineering Services Network already had some knowledge on running automated tests, but was struggling with the accumulation of technical debt due to inefficient, obtuse testing code. Being in a high-pressure, rapid-release environment, they didn't have time to start over, but desperately needed enhancements and training. Chris reinvigorated their existing test code with cleaner, easier to use, and more efficient test methods and provided weekly training seminars in automation theory and best practices to staff. Using the overhauled test framework, Chris was able to create test suites that reduced days-long testing efforts to mere minutes, keeping releases on time while reducing costs.

A department within Google was making constant adjustments and improvements to one of their mobile applications and expected automated testing to match and reduce their manual testing efforts. The application was unconventional, as most of its features manifested in the use of third-party applications and required extensive and detailed set up to ensure that it was correctly loaded. This, in turn, made manual testing laborious and time-intensive. These unique quirks were no obstacle for Chris, who constructed a unique, flexible test framework to interface with the challenging application. Tests built in this framework were easily worked into the existing release pipeline and could be effectively run by manual testers with minimal training. The framework was so successful, it served as the pilot in an effort to further expand automated testing in related projects at Google.