1 / 37

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.

zoltan
Download Presentation

Testing in a Velocity Culture

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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.

  3. 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

  4. Ancestry.com Evolution toAgility 2 ½ year period (2010 – present)

  5. Agilityis the constant,incremental flowof business value realization.

  6. Continuous Delivery is consistently and reliably releasing business value increments fast through automated build, test, configuration and deployment.

  7. True agility drives toward a velocity driven culture.

  8. If testing slows you down… …then quality is NOT free. It is actually costing you a lot.

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

  10. Testing in a Velocity Culture • 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?

  11. We are ina “no win” situation.

  12. “I don’t believe in a no-win situation” – Capt. James T. Kirk

  13. Kobayashi Maru

  14. To win we must“change” the rules “Cheat”

  15. The Ten Commandmentsof Testing

  16. #1 - Nuture“quality is everyone’s responsibility” attitude. No longer be identified as Quality Assurance. QA could be“Quality Assistance” (Atlassian)

  17. #2 – Devs Shalt Test “Continuous Testing”

  18. #3 – Devs Shalt Write All Automated Tests (or, almost all)

  19. Examples • Google • Facebook • Thoughtworks • Atlassian • Microsoft (moving this direction)

  20. #4 - Regression tests shalt be automated If regressions aren’t automated this is a waste of time.

  21. #5 – Software Engineers in Test (SET) Shalt Enable Devs to Test If you are testing features or code then…?

  22. SET = Software Engineer in Test • 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.

  23. #6 - Test Engineers Shalt Enable Devs to Test

  24. Test Engineer • 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.

  25. #7 - Thou shalt avoid browser-based automated testing

  26. #8 – TEs shalt think in terms of productivity

  27. “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

  28. #9 – Leverage users and user-like testing earlier and more frequently. Internal dog-fooding Frequent customer betas Crowd-sourcing (uTest)

  29. #10 - Thou shalt have high impact

  30. Experience report @ Ancestry.com A lean startup experiment Bonnie Bingham, Test Engineer Social Apps

  31. Story of a New Team • 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

  32. Lean Startup & Testing • Validated Learning from users • Find early adopters • Get out of the building • Avoid waste • Kill a feature • Fail • Summary

  33. As a testing professional, can you adapt to testing in a velocity culture?

  34. Thank You.Q & A

More Related