Download to read offline
Uploaded byPavel Chunyayev
Want Continuous Delivery? Give testing a priority! 16-6-2016, Friss, Utrecht
The document emphasizes the importance of prioritizing testing in the continuous delivery process to ensure that products remain releasable. It outlines various stages of continuous delivery, including planning, developing, building, testing, and releasing, while advocating for a culture of collaboration and quality integration throughout the process. Lean principles are highlighted as essential for optimizing workflows and delivering fast results in software development.
More Related Content
Similar to Want Continuous Delivery? Give testing a priority! 16-6-2016, Friss, Utrecht
Want Continuous Delivery? Give testing a priority! 16-6-2016, Friss, Utrecht
- 1. Want Continuous Delivery? Givetesting a priority! Build the quality in and keep the product releasable 16-6-2016, Friss, Utrecht Pavel Chunyayev
- 2. @PavelChunyayev Agenda • Continuous Deliveryprocess overview • A story about testing • A story about releasing • Closing ideas
- 3. @PavelChunyayev About me • 12years of IT experience • Lived and worked in Ukraine and Estonia • Moved a year and half ago to the Netherlands • Love cycling • Love Dutch language • Love software development processes • Love working with people
- 4.
- 5. @PavelChunyayev Continuous Delivery Incept • Businessidea • Is needed immediately • Should be validated Plan • Refine • Estimate • Prioritize Develop • Put into sprint • Develop in a branch • Conduct a code review • Merge into master Build • Trigger pipeline • Build • Unit testing • Integration testing • Static code analysis Test • Contract testing • E2E testing • Security testing • Resilience testing Release • Zero-downtime • Canary testing • Rolling deployment • Blue / green deployment Operate • Monitoring • Validation of the idea • Money generation • Disposal
- 6.
- 7. @PavelChunyayev Keep the productreleasable Build quality in
- 8. @PavelChunyayev Build • Test• Release
- 9. @PavelChunyayev Continuous Delivery Incept • Businessidea • Is needed immediately • Should be validated Plan • Refine • Estimate • Prioritize Develop • Put into sprint • Develop in a branch • Conduct a code review • Merge into master Build • Trigger pipeline • Build • Unit testing • Integration testing • Static code analysis Test • Contract testing • E2E testing • Security testing • Resilience testing Release • Zero-downtime • Canary testing • Rolling deployment • Blue / green deployment Operate • Monitoring • Validation of the idea • Money generation • Disposal
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28. @PavelChunyayev The top ofthe pyramid
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36. @PavelChunyayev Build quality in •Testing is not just presence or absence of defects • Testing is not a separate process • Test should not just raise the cost of maintenance • Stop thinking about functional testing only • Quality goal need to be established early in the development process • Automated testing – part of Definition of Done • Test early, move tests to the left • TDD
- 37. @PavelChunyayev Frequent, incremental releases forearly feedback
- 38.
- 39. @PavelChunyayev To practice • Deploysoftware at the end of every iteration (done = released to production). • And then start doing it quicker. • Optimize flow - don’t make ineffective more efficient.
- 40. @PavelChunyayev Optimize the flow •Honour existing processes, records, and controls. • They arose for a reason. • Streamline and simplify all processes, records, and controls. • Challenge the level of ceremony.
- 41.
- 42. @PavelChunyayev Lean principles • Optimizethe whole • Eliminate waste • Deliver fast by managing flow • Build quality into the system • Create knowledge • Defer commitment • Respect people
- 43. @PavelChunyayev Culture • Protect people •Shared goal • Collaboration • Encourage experimentation and learning • Blameless postmortems • Learn to trust • Transparency
- 44. @PavelChunyayev “Developing people andthe system so that together they are capable of achieving successful results is the point.” Mary and Tom Poppendieck
- 45. @PavelChunyayev Continuous Delivery Incept • Businessidea • Is needed immediately • Should be validated Plan • Refine • Estimate • Prioritize Develop • Put into sprint • Develop in a branch • Conduct a code review • Merge into master Build • Trigger pipeline • Build • Unit testing • Integration testing • Static code analysis Test • Contract testing • E2E testing • Security testing • Resilience testing Release • Zero-downtime • Canary testing • Rolling deployment • Blue / green deployment Operate • Monitoring • Validation of the idea • Money generation • Disposal Keep the product releasable Build quality in Improve continuously Build the right culture pavel@levi9.com
Editor's Notes
- #2 Ideas come from all the sources. Questions are welcome. Disagreement is welcome, but after the talk. Yes, but; what if.
- #3 There's always a big gap between a piece of general advice and how it applies in a particular circumstance (which is why consultants are teased for saying "it depends"). There's no way I can know all the particular issues and constraints in your project, so you have to take my half-baked comments and finish them off yourself by deciding how they apply to your circumstances.
- #4 .
- #5 .
- #6 Not every feature is needed. Shorter and shorter release cycles => Release more software in less time.
- #7 TPS Can’t churn out. No manual testing.
- #8 .
- #9 .
- #10 .
- #11 Reproducible and repeatable process (including testing). Potentially shippable product -> Keeping the product releasable
- #12 .
- #13 Testing criteria. Run over and over again.
- #14 .
- #15 No DTAP. Immutable (testing framework?) TTL Docker Framework to allow restart - select arbitrary test
- #16 Building the thing right Building the right thing
- #17 Unit + Integration – level of microservices.
- #18 .
- #19 100% coverage? Test your unit tests. Know exactly what is broken. Feature toggling.
- #20 Connect units together How parts of application work together Feature toggling. Mock or not to mock
- #21 Black box testing. How service works as a whole. Different integrations – pub/sub, request/reply. Feature toggling. Mock or not to mock
- #22 Proof we are still on track Not only selenium Focus on: business flows personas, user journeys BDD + DSL? Data independency Feature toggling, page objects Mock or not to mock
- #23 Communication – via contracts
- #24 * Semantic or not semantic * API versioning - public or also internal? * Transition between versions – testing different versions * Running several versions together
- #25 * Semantic or not semantic * API versioning - public or also internal? * Transition between versioning – testing different versions * Running several versions together
- #26 * Semantic or not semantic * API versioning - public or also internal? * Transition between versioning – testing different versions * Running several versions together
- #27 * Semantic or not semantic * API versioning - public or also internal? * Transition between versioning – testing different versions * Running several versions together
- #28 * Semantic or not semantic * API versioning - public or also internal? * Transition between versioning – testing different versions * Running several versions together
- #29 Testing in production Canary Dark launch Real users, not synthetic transactions Security testing Availability testing Resilience testing
- #30 .
- #31 .
- #32 .
- #33 .
- #34 .
- #35 .
- #36 Unit + Integration – level of microservices. Unit + Integration – inside Contract + E2E - outside The same testing is needed for monolith, but crucial for microservices.
- #37 Shared responsibility.
- #38 Repetition makes mastery. Feedback from users. Feedback to devs, to bussiness
- #39 Think of end-user throughout the whole application lifecycle. A story isn't done until it is being used by real users in production and has been validated to be a useful part of a product.
- #40 .
- #41 In conflict on purpose. This is reality. Evolution, not revolution.
- #42 .
- #43 Kaizen, Japanese for "improvement."
- #44 The most important thing you can build is culture. Don’t imitate, that won’t bring the culture you want. Stamp on problems, not on people! Solve problems, not people.
- #45 .