Testing in a velocity culture
1 / 37

Testing in a Velocity Culture - PowerPoint PPT Presentation

  • Uploaded on

Testing in a Velocity Culture. Utah QA User’s Group January 22, 2013 John Esser Dir. of Engineering Productivity & Agile Development Ancestry.com.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Testing in a Velocity Culture' - zoltan

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Testing in a velocity culture

Testing in a Velocity Culture

Utah QA User’s Group

January 22, 2013

John Esser

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.

R apidly developing and releasing new features and capabilities is today s key business driver

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

Ancestry com evolution to agility
Ancestry.com Evolution toAgility

2 ½ year period (2010 – present)

Agility is the constant incremental flow of business value realization

Agilityis the constant,incremental flowof business value realization.

Continuous delivery
Continuous Delivery

is consistently and reliably

releasing business value increments


through automated build, test, configuration and deployment.

If testing slows you down

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

Anything that doesn’t contribute to finding the right product is waste.-Lean Startup

And that includes testing.

Testing in a velocity culture1
Testing in a Velocity Culture product is waste.

  • Rapid feature delivery (days not weeks).

  • Rapid innovation/feedback.

  • Testing cannot slow you down.

  • Testing must enable productivity.

  • Limited resources—actually you never have enough people or time.

    How do you win?

We are in a no win situation

We are in product is waste.a “no win” situation.

Kobayashi maru

Kobayashi James T. KirkMaru

To win we must change the rules

To James T. Kirkwin we must“change” the rules


The ten commandments of testing

The Ten Commandments James T. Kirkof Testing

1 nuture quality is everyone s responsibility attitude

#1 - James T. KirkNuture“quality is everyone’s responsibility” attitude.

No longer be identified as Quality Assurance.

QA could be“Quality Assistance” (Atlassian)

2 devs shalt test

#2 – James T. KirkDevs Shalt Test

“Continuous Testing”

3 devs shalt write all automated tests

#3 – James T. KirkDevs Shalt Write All Automated Tests

(or, almost all)

Examples James T. Kirk

  • Google

  • Facebook

  • Thoughtworks

  • Atlassian

  • Microsoft (moving this direction)

4 r egression tests shalt be automated

#4 - James T. KirkRegression 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

#5 – Software Engineers in Test (SET) Shalt Enable James T. KirkDevs to Test

If you are testing features or code then…?

Set software engineer in test
SET = Software Engineer in Test James T. Kirk

  • Do not test product features or test the code.

  • Concentrate on getting testing into the workflow of the developer.

  • Focus on enabling automation.

  • Make code testable.

  • Write tools, frameworks, infrastructure.

  • Focus on making the tests run faster and produce better diagnostics.

6 test engineers shalt enable devs to test

#6 - Test Engineers Shalt Enable James T. KirkDevs to Test

Test engineer
Test Engineer James T. Kirk

  • Focus on user concerns/perspective

  • Looks for weak points & holes from a holistic viewpoint.

  • Does not do “menial” things; does not run regressions

  • Wide latitude in role; requires a variety of skills and perspectives.

  • Technical; understand architectures, technologies,assess risk, etc.

7 thou shalt avoid b rowser based automated testing

#7 - Thou shalt avoid James T. Kirkbrowser-based automated testing

“People James T. Kirkbegan 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

#9 – Leverage users and user-like testing earlier and more frequently.

Internal dog-fooding

Frequent customer betas

Crowd-sourcing (uTest)

Experience report @ ancestry com

Experience report @ Ancestry.com frequently.

A lean startup experiment

Bonnie Bingham, Test Engineer

Social Apps

Story of a new team
Story of a New Team frequently.

  • No code, seriously

  • We decided to use node.js

  • How can Testing be successful at this point?

  • A GREAT dev team

    • Included in everything

    • Build code every day, fix bugs

  • Insert and evangelize Lean Startup principles

Lean startup testing
Lean Startup & Testing frequently.

  • Validated Learning from users

  • Find early adopters

  • Get out of the building

  • Avoid waste

  • Kill a feature

  • Fail

  • Summary

Thank you q a

Thank You. velocity culture?Q & A