Quality Assurance in a DevOps World

  • 3,502 views
Uploaded on

My slide deck from SCALE9x / DevOpsDay in LA. I blew the presentation, but hopefully the content had some value.

My slide deck from SCALE9x / DevOpsDay in LA. I blew the presentation, but hopefully the content had some value.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • great slides, Kit. Thanks for the presentation at SCaLE
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
3,502
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
44
Comments
1
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Quality Assurance in a DevOps World Enabling Trust Kit Plummer http://kitplummer.github.com kplummer@maestrodev.com MaestroDevTuesday, February 22, 2011 1
  • 2. DevOps is an ecosystem of... •People (relationships) • Processes (activities) • Product(s) MaestroDevTuesday, February 22, 2011 2
  • 3. Ecosystem… • Applied on top of columnar organizations: – Development/SW eng./design/etc. – Quality assurance/testing/delivery – Product eng./operations/customers MaestroDevTuesday, February 22, 2011 3
  • 4. Current DevOps thinking is... • aligned with the Agile Manifesto, • and prescribes itself as a Cultural (organizational) and Professional (personal) movement . MaestroDevTuesday, February 22, 2011 4
  • 5. MaestroDevTuesday, February 22, 2011 5
  • 6. MaestroDevTuesday, February 22, 2011 6
  • 7. MaestroDevTuesday, February 22, 2011 7
  • 8. MaestroDevTuesday, February 22, 2011 8
  • 9. Trust is the cornerstone... • Patrick Debois math - based on Coveys "4 Cores": • trust = ƒ(character,competence) • character = ƒ(integrity, intent) • competence = ƒ(capabilities, results) MaestroDevTuesday, February 22, 2011 9
  • 10. Trust is a QA deliverable... • Results are the indicator • Testing is the apparatus • Proof of quality is the target MaestroDevTuesday, February 22, 2011 10
  • 11. MaestroDevTuesday, February 22, 2011 11
  • 12. The Continuum (borked) MaestroDevTuesday, February 22, 2011 12
  • 13. Proof == Trust MaestroDevTuesday, February 22, 2011 13
  • 14. Qualty Assuance • Product Control – Requirements – Change – Release • Catch “bugs” before presentation – Functional AND Non-Functional MaestroDevTuesday, February 22, 2011 14
  • 15. Bi-Directional (required) MaestroDevTuesday, February 22, 2011 15
  • 16. QA Frontend • Agile – QA/Testers on team – Stories -> UAT – Continuous Integration MaestroDevTuesday, February 22, 2011 16
  • 17. QA Backend • Test harness(es) – Integration – Functional – Non-functional MaestroDevTuesday, February 22, 2011 17
  • 18. QA’s DevOp Priorities • Testing must be a first-class citizen MaestroDevTuesday, February 22, 2011 18
  • 19. QA’s DevOp Priorities • Testing must be a first-class citizen “We’re not worried about testing...our biggest problem is automating deployment” MaestroDevTuesday, February 22, 2011 18
  • 20. QA’s Priorities (cont.d) • Release management MaestroDevTuesday, February 22, 2011 19
  • 21. Driving Trust via Releases Results (Deliverables) • Proof (Testing) Functional Validated & Versioned (released) Functional & Non-Functional Unit and Integration Integrated & Libraries/Apps Deployed (promoted) MaestroDevTuesday, February 22, 2011 20
  • 22. Dev-QA-Ops Choreography MaestroDevTuesday, February 22, 2011 21
  • 23. Push QA into Ops and Dev • *DD – Behavior DD (Agile QA?) – Pulls non-functional from Ops – Pushes non-functional to Devs • Less Unit, Mo Integration, Less Mock • Automate functional, but to a point • Ops and QA enable Dev testing MaestroDevTuesday, February 22, 2011 22
  • 24. Push QA into Ops and Dev • *DD – Behavior DD (Agile QA?) “BDD has reduced our – Pulls non-functional from Ops prerelease bugs by 80%, – Pushes non-functional to Devs in a side-by-side • Less Unit, Mo Integration, Less Mock • Automate functional, but to a point comparo” • Ops and QA enable Dev testing MaestroDevTuesday, February 22, 2011 22
  • 25. Alternative Perspective • Building missiles – Platform shall have a maximum range of 100km MaestroDevTuesday, February 22, 2011 23
  • 26. Validation and Verification Functional Libraries Apps/Services Functional & Non-Functional Integrated & Modeling & Sims Deployed Algorithms/Designs MaestroDevTuesday, February 22, 2011 24
  • 27. Quality Quality • Tests must be good – More to it than just assertions • True negatives? False Positives? – Testing for Failure • Brittle Tests? Avoid testing content • Changes should come with tests (open sourcey way) MaestroDevTuesday, February 22, 2011 25
  • 28. Truth isn’t Good Enough • Regressions (read blame) – A single version change affects truth • Measuring/Monitoring – Earlier the better • Trending (continuous improvement) – Continuous improvement MaestroDevTuesday, February 22, 2011 26
  • 29. Dev/QA Reporting MaestroDevTuesday, February 22, 2011 27
  • 30. MaestroDevTuesday, February 22, 2011 28
  • 31. DevOps MaestroDevTuesday, February 22, 2011 29
  • 32. Questions http://devopsweekly.com/ MaestroDevTuesday, February 22, 2011 30