The document details a full-day tutorial by Jim Holmes on developing WebDriver automated tests, emphasizing best practices and strategies for effective testing in software delivery. It covers various testing types, practical coding tips, and the importance of maintaining a reliable test suite. The presentation also highlights the significance of risk and value in determining testing approaches, along with resources for further learning.

1. MB
Full-day Tutorials
Monday, April 30th, 2018
8:30 AM
Develop WebDriver Automated Tests—
and Keep Your Sanity
Presented by:
Jim Holmes
Guidepost Systems
Brought to you by:
350 Corporate Way, Suite 400, Orange Park, FL 32073
888---268---8770 ·· 904---278---0524 - info@techwell.com - http://www.stareast.techwell.com/

2. Jim Holmes
Guidepost Systems
Jim Holmes is an executive consultant at Pillar Technology where he works with
organizations to improve their software delivery process. he is also the
owner/principal of Guidepost Systems which lets him engage directly with
struggling organizations. Since joining the US Air Force in 1982, Jim has been in
various corners of the IT world. He has worked with organizations—ranging from
start-ups to Fortune 10 companies—to improve their delivery processes and ship
better value to their customers. When not at work, you may find Jim in the
kitchen with a glass of wine, playing Xbox, hiking with his family, or banished to
the garage while practicing his guitar.

3. WebDriver That
Won’t Drive
You Crazy
Get Latest
Slides At
http://speakerdeck.com/
jimholmes

4. Jim Holmes
jim@GuidePostSystems.com
github.com/jimholmes
@aJimHolmes
Logistics

5. Time
Exercises
Breaks
Backlog
Goals

6. There Are No
“Best
Practices”
Test the right
things

7. Get the right
coverage
Know the
fundamentals

8. Write good
code
Opening
Exercises

9. What does
“Quality”
mean to you?
If Testing
were a sport,
what sport
would it be?

10. Thanks to Karen Greaves and
Samantha Laing
A Coach’s Guide to Agile
Testing
https://leanpub.com/AgileTesting
What’s
Our Job?

11. Who
guarantees
“quality” ??
Risk

12. Value
Risk and Value
guide all our tests.
ESPECIALLY
WebDriver tests

13. Types of
Testing
“test”
versus
“check”

14. Any failure is
a
starting point
Unit Tests

15. 40 hours TIMES $20 per hour EQUALS $800
Integration
(or Service)
Tests

16. Using Postman
When I call the create item web service
with a new item service template
Then the item shows up in the database
User Interface
(or end-to-end)

17. Using any of our supported browsers
And I don’t have anything in my cart
When I add bacon, tires, and a frog to my cart
Then I will see those items in my cart
Exploratory
Testing

18. Using SQL Injection, malformed data, and
oversized data
I’m going to explore the search product screens
For 45 minutes
To see what interesting (and scary!) stuff I can
find
https://martinfowler.com/articles/practical-test-pyramid.html

19. https://twitter.com/noahsussman/status/836612175707930625
There are no
‘best
practices’
There is no
‘one testing
ring to rule
them all’

20. Security
Accessibility
Scalability
Performance
Usability
Compliance
Mom
Demo
What it looks
like running
together

21. Working With
Risk
Setup

22. Repository
https://github.com/
jimholmes/
SaneWebDriver-CSharp
SaneWebDriver-Java

23. First run in
Eclipse
First run in
Visual Studio

24. Overview
Components
WebDriver APIs
Drivers
Frameworks
Libraries
Tools

25. Browser
BrowserWebDriver

26. BrowserWebDriver
IWebDriver browser = new FirefoxDriver();
browser.Navigate().GoToUrl(“SOMEPLACE”);

27. WebDriver
Bindings Support
Classes.NET
Java
Ruby
Python
JavaScript
Perl
blah blah blah blah
WebDriverWait
ExpectedConditions
etc.
+
HostSystem
Browser
WebDriver
Bindings +
support classes

28. HostSystem
Browser
WebDriver
Bindings +
support classes
Driver
ChromeDriver, eg
HostSystem
Browser
WebDriver
Bindings +
support classes
Driver
ChromeDriver, eg

29. HostSystem
Browser
WebDriver
Bindings +
support classes
Driver
ChromeDriver, eg
HostSystem
Browser
WebDriver
Bindings +
support classes
Driver
ChromeDriver, eg

30. HostSystem
Browser
WebDriver
Bindings +
support classes
Driver
ChromeDriver, eg
HostSystem
Browser
WebDriver

31. HostSystem
Browser
WebDriver
Driver
HostSystem
Browser
WebDriver
Driver
Remote
WebDriver

32. HostSystem
Browser
WebDriver
Driver
Remote
WebDriverHostSystem
Browser
WebDriver
Driver
Remote
WebDriver

33. HostSystem
Browser
WebDriver
Driver
Remote
WebDriverHostSystem
Browser
WebDriver
Driver
Remote
WebDriver

34. HostSystem
Browser
WebDriver
Driver
Remote
WebDriverHostSystem
Browser
WebDriver
Driver
Remote
WebDriver

35. HostSystem
WebDriver
Selenium
Server or
Grid HostSystem
Browser
Driver
Remote
WebDriverHostSystem
Browser
Driver
Remote
WebDriver
Test
Framework
WebDriver
Selenium
Server or
Grid

36. Assert.IsNotNullOrEmpty(
grid.FindElement(
By.CssSelector(SOME_ELEMENT)).Text);
Test Framework
BrowserWebDriver
Driver

37. Language Framework
Test Framework
BrowserWebDriver
Driver
GIVEN I am logged on as a Salesperson
WHEN I create a new lead
THEN that contact appears only in my leads

38. Maintainability
Your Test Suite
should
NOT BE

39. “flaky”
Require lots
of time to
change or fix

40. Your Test Suite
SHOULD
BE
Valuable

41. Reliable
Trustworthy

42. Easy to
Change
How to
get there

43. Team With the
Developers
Small Steps

44. Think Before
You Code
The best code
you write is
that
you don’t

45. Refactor
Code can be
like poetry

46. Think
Plan
Fail
Learn
Fail Less
WebDriver
101

47. The
Basics
Locators
Async

48. Write the First
Test
Refactor

49. Page Objects
Clean Tests
SRP
DRY/moist
Refactor
Again

50. More
Advanced
Concepts
Team With the
Developers

51. Backing APIs
Use Helper
Libraries

52. Testable
Systems
Own the System
Code?
USE THAT
POWER!

53. Hack the
UI
Locators
Custom IDs

54. Better Tests
Hack the
System

55. Feature
Toggles
Mock Services
Better Tests

56. Now
What?
CI/CD

57. Cloud
Parallel

58. Parallelization Solves
Everything!

59. Parallelization Solves
Everything!

60. Parallelization Solves
Everything!
Fix Your Dang System!

61. bit.ly/3HoursTo3Mins
Takeaways

62. Automate High-Value,
High Risk

63. Avoid Overlapping
Coverage
Test Code
is
Production Code

64. Manage Your Data
Build Out APIs

65. Avoid End-To-End
Parallelization as
LAST RESORT

66. bit.ly/leadershipjourney
0) No SharePoint

67. B) Hug your loved
ones
RIGHT NOW
THANK
YOU