Testing in a Velocity Culture. Utah QA User’s Group January 22, 2013 John Esser Dir. of Engineering Productivity & Agile Development Ancestry.com.
Testing in a Velocity Culture
Utah QA User’s Group
January 22, 2013
Dir. of Engineering Productivity & Agile Development
Ancestry.com is the world’s largest online family history resource with more than 2.2 million members, 10 billion records, and 5 PB genealogical data.
Ancestry.com can help you discover your roots and tell your unique family story.
Rapidly developing and releasing new features and capabilities is today’s key business driver.
“Quality is secondary to speed, and probably lower than that.”-Facebook
2 ½ year period (2010 – present)
Agilityis the constant,incremental flowof business value realization.
is consistently and reliably
releasing business value increments
through automated build, test, configuration and deployment.
True agility drives toward a velocity driven culture.
If testing slows you down…
…then quality is NOT free. It is actually costing you a lot.
Anything that doesn’t contribute to finding the right product is waste.-Lean Startup
And that includes testing.
How do you win?
We are ina “no win” situation.
To win we must“change” the rules
The Ten Commandmentsof Testing
#1 - Nuture“quality is everyone’s responsibility” attitude.
No longer be identified as Quality Assurance.
QA could be“Quality Assistance” (Atlassian)
#2 – Devs Shalt Test
#3 – Devs Shalt Write All Automated Tests
(or, almost all)
#4 - Regression tests shalt be automated
If regressions aren’t automated this is a waste of time.
#5 – Software Engineers in Test (SET) Shalt Enable Devs to Test
If you are testing features or code then…?
#6 - Test Engineers Shalt Enable Devs to Test
#7 - Thou shalt avoid browser-based automated testing
#8 – TEs shalt think in terms of productivity
“People began talking about productivity instead of testing and quality. Productivity is our job, testing and quality are the job of everyone involved in development. This means that developers own testing and developers own quality. The productivity team is responsible for enabling development to nail those two things.”
-Patrick Copeland, Google
#9 – Leverage users and user-like testing earlier and more frequently.
Frequent customer betas
#10 - Thou shalt have high impact
Experience report @ Ancestry.com
A lean startup experiment
Bonnie Bingham, Test Engineer
As a testing professional, can you adapt to testing in a velocity culture?
Thank You.Q & A