The document discusses test automation in brownfield applications. Some key challenges mentioned include code that is difficult to test, engineering challenges, infrastructure challenges, and dealing with large volumes of test data. Meaningful code coverage through testing is also noted as a challenge. The document advocates testing key use cases, defects, and new features as a way to start with automation. It also emphasizes building quality systems that provide value.

1. Test Automation in
Brownfield Applications

2. My name is Shawn and
I’m a software developer

3. A programmer is going out for a stroll one
evening. His wife asks him to swing by the
store and pick up a gallon of milk, and if they
had eggs, to get a dozen. He returned with
twelve gallons of milk and said "They had
eggs."
3

4. 4

5. Our existences are about
precise communication...and
communication is about
feedback loops

6. Our existences are about
precise communication...and
communication is about
feedback loops

7. 7

8. Time
8

9. Release to
Test
Release to
Production
Time
8

10. Late Defect Discovery Results in
Significant Rework
Release to
Test
Release to
Production
Time
8

11. Release to
Test
Release to
Production
Time
9

12. Release toRelease to
Test Production
Time
9

13. Let’s shift the focus from
Bug detection to bug
prevention.

14. http://www.isixsigma.com/industries/software-it/software-defectprevention-nutshell/
11

15. Functional Acceptance Test
Automation
• Implementing changes more efficiently
• Shortened feedback loop
• Higher product quality
• Less rework
• Better work alignment to priority
• Helps make systems easier to modify
• Regression
12

16. Functional Acceptance Test
Automation
• Implementing changes more efficiently
• Shortened feedback loop
• Higher product quality
• Less rework
• Better work alignment to priority
• Helps make systems easier to modify
• Regression
13

17. 14

18. 14

19. Workflow
15

20. Brownfield
Applications

21. Can we benefit?

22. Can we benefit?
We can improve our system going
forward
!
The goal is building quality systems
that provide value

23. How to start

24. How to start
•
Test KEY use cases

25. How to start
•
Test KEY use cases
•
Test defects

26. How to start
•
Test KEY use cases
•
Test defects
•
Test new features

29. Your application might be
hard to test

30. There are engineering
challenges

31. There are infrastructure
challenges

32. How will you deal with
the new volume of data?

33. How will you deal with
the new volume of data?
Test automation generates TONS of data, some good some bad,
all must be processed.

34. How do we know if
we’re doing a good job?

35. Meaningful code coverage
is hard.

36. • Your code might be hard to test
• There are engineering challenges
• There are infrastructure challenges
• If a goal is a shortened feedback loop,
how will you deal with the new volume of
data?
• How do we know if we’re doing a good
job?
• Meaningful code coverage is a challenge.
26

38. Shawn Wallace
!
shawn.wallace@centricconsulting.com
Twitter: @ShawnWallace
Blog: blog.shawnewallace.com
http://www.about.me/shawnwallace

39. Q&A
For more information...
• This Presentation on GitHub - https://github.com/shawnewallace/intro-to-atdd.git
• cukes.info
• Gojko Adzic
– cuke4ninja.com
– Specification by Example
• https://github.com/aslakhellesoy/cucumber/wiki
• http://groups.google.com/group/cukes
• http://www.cheezyworld.com
• The Cucumber Book, Matt Wayne, Aslak Hellesøy: http://pragprog.com/book/hwcuc/thecucumber-book
• The Rspec Book, David Chelimsky: http://www.pragprog.com/titles/achbd/the-rspecbook
• http://simpleprogrammer.com/2011/11/21/
understanding-the-vertical-slice/
• http://www.deltamatrix.com/2012-04-17-04-37-50/
horizontal-and-vertical-user-stories-slicing-the-cake