With modern software development moving at a rapid pace, automation engineers may find it difficult to keep up with frequent changes. Incorporating parts of the testing process into everyone's workflow, this creates the potential for automated testing to mirror software delivery. Description: With modern software development moving at a rapid pace, automation engineers may find it difficult to keep up with frequent changes. But if parts of the testing process are incorporated into everyone's workflow, this creates the potential for automated testing to mirror software delivery. My goal is to make software testing more accessible to entire product and engineering teams by providing familiar tools that allow individuals to easily contribute to the automation process. For this talk, I will explore how we can meet developers halfway by using the javascript-based testing framework WebdriverIO, demonstrate how product managers can create living documentation and test cases using Cucumber, and talk about sharing page objects and testing libraries across multiple services using NPM. Code Examples: https://github.com/dcypherthis/gtr-test-cucumber https://github.com/dcypherthis/gtr-test-mocha-bdd https://github.com/dcypherthis/gtr-test-xray

1. Jumpstarting Selenium Testing in
Your Organization
Josh Cypher - Quality Automation Engineering Lead
November 2016

3. WE’RE ON A MISSION
TO HELP MARKETERS DO THEIR VERY BEST WORK.

4. CUSTOMER EXPERIENCE
AN EXPERIENCE YOU AND YOUR TEAM WILL LOVE.

5. THE TESTING PYRAMID
Source: http://watirmelon.com

6. Quality As Part Of The Delivery
Process

7. QUALITY AS PART OF THE DELIVERY PROCESS
• Test at each development stage
• Unit test ALL THE THINGS
• Identify boundaries between services
• Test for behavior, not just function
• Keep Exploring

8. CUSTOMER EXPERIENCE
AN EXPERIENCE YOU AND YOUR TEAM WILL LOVE.

9. All Automation Engineers are Developers
All Developers Are Testers

10. THE TESTING PYRAMID
Source: http://watirmelon.com

11. Testing For Behavior

12. Cucumber
WHAT
+ BDD Framework for writing plain-english
statements and mapping them to test code
+ Built around Given, When & Then
statements that make up the Gherkin
syntax
+ Features describe Value propositions
+ Scenarios evaluate Expectations
WHO
+ Business People
WHY
+ Produces Contextual Errors
+ Describes Customer Intentions

13. Why Javascript?

14. Lets Use Selenium!

15. Selenium
WHAT
+ Tool for automating web application testing by
sending commands to Native Browser API's
+ Self-contained Library that is Framework-Agnostic
+ Supports Multiple Browsers, Proxies, & Devices
WHY
+ Provide a Friendly API to help write and maintain
tests
+ Bring Modularity & Realism to the testing
experience
HOW
+ Sends actionable commands to the browser and
returns data used for making assertions via the
JSON Wire Protocol

16. WebdriverIO

17. Cucumber...SALAD
+ Cucumber draws relationships between
Gherkin Statements & Step Definitions
+ Test code Lives in the step definitions at it's
highest level
REGEX SUPPORT
+ Cucumber supports parameterization
through Regular Expressions
+ We can leverage regex to create a few very
Abstract step definitions that power many
variations of tests

18. UI AUTOMATION:
The Tester's Rube Goldberg Machine

19. The Tester's Rube Goldberg Machine
UI AUTOMATION:

20. Not All Assertions Are Created Equal

21. 1. Receptacle Picked Up
2. Waste Out Of Can
Unit Tests Passed:

22. Design Patterns

23. The Page Object Pattern
+ CSS selectors can often change in test code, Breaking all of our automation
+ We place these selectors and functions in domain-specific page objects that are
shared across the Global Scope
+ We can instantiate page objects as needed for efficiency
ANOTHER LEVEL OF ABSTRACTION
+ The page objects become the API that interacts with the user interface
+ One change to a single selector is fixed in One Place
+ Pages can Inherit, Extend, or work in Isolation of one another

24. Dependency Injection

25. So Now What?
Let's share it with everyone!

26. Page Objects
UI Map
Utility
Classes
Router
Dependency
Injector
Steps/Specs
Selenium
Assertions

27. NPM Install your-test-library
HOW
+ Wrap all your page objects, test data, utility classes, etc in a Publishable Package
+ Treat this code like Production code
+ Push updates to the library when the front-end changes.
+ Document and treat this like any public-facing API
WHY
+ Test with Whatever, Wherever
+ Have a single source of truth for ALL your testing needs.
+ Get developers involved in the process

28. Distributed Testing

29. Surgeon General's Warning:
-Using PhantomJS for UI
Testing Accomplishes nothing
and Can lead to Flaky Results /
CANCER

30. WILL IT BLEND?
PUTTING IT ALL TOGETHER
+ We test specifics from the Gherkin layer
+ Step definitions support multiple parameters by
leveraging regex
+ Page Objects are instantiated one at a time
through dependency injection
+ Assertions are only made at the Step definition
level
+ Page objects live a completely decoupled
"testing library"

31. DEMO TIME!
LET’S TAKE A LOOK!

32. THANKS FOR LISTENING!
LET’S DISCUSS.
github.com/dcypherthis
@joshuacypher
jcypher@myemma.com

33. Examples
AUT - https://guitar-practice-app.herokuapp.com/
https://github.com/dcypherthis/gtr-test-xray
https://github.com/dcypherthis/gtr-test-cucumber
https://github.com/dcypherthis/gtr-test-mocha-bdd