Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Testing in a continuous delivery world

939 views

Published on

Hey, do you remember what everyone was asking what the role of the tester would be in an agile team? It’s happening again!

And things are changing again. A team that takes on the challenge to release their every commit certainly will take testing seriously. It will need to evolve new ways of testing. It will have new dynamics of testers working with developers. It will find new ways of of interacting with customers, stakeholders and product owners.

In this talk we’ll look at how continuous deployment changes the dynamics of an agile team. How quality moves even more to the center of the stage. How that changes the role of the tester once again. How it changes the role of developers, too. How this practice allows you to put the customer center stage again. And how that, too, has testing competencies at its core. And we’ll not forget DevOps, and how monitoring can be a continuous testing strategy.

Published in: Software

Testing in a continuous delivery world

  1. 1. Testing in a Continuous Delivery World Wouter Lagerweij @wouterla #EuroTestDay 2016
  2. 2. Waterfall Requirements Design Implementation Testing Deployment Maintenance
  3. 3. Waterfall Requirements Design Implementation Testing Deploy
  4. 4. Waterfall Requirements Design Implementation Testing Deployment Maintenance3 - 12+ months
  5. 5. Agile Deployment Exploratory Testing Design and Implement Acceptance Tests Requirements Implement Acceptance Tests Design and Implementation Deployment Sprint start Sprint end Exploratory Testing
  6. 6. Agile Deployment Exploratory Testing Design andRequirements Design and Implementation Deployment Sprint start Sprint end Testing
  7. 7. Agile Deployment Exploratory Testing Design and Implement Acceptance Tests Requirements Implement Acceptance Tests Design and Implementation Deployment Sprint start Sprint end Exploratory Testing 2 - 5 days
  8. 8. Continuous Delivery Requirements Implement one Acceptance Test DeploymentImplementation Exploratory Testing (on production)
  9. 9. Continuous Delivery Requirements Implement one Acceptance Test DeploymentImplementation Exploratory Testing (on production) 2 - 6 hours
  10. 10. Continuous Delivery Requirements Implement one Acceptance Test DeploymentImplementation 2 - 6 hours Exploratory Testing (on production)
  11. 11. Continuous Delivery Requirements Implement one Acceptance Test DeploymentImplementation Exploratory Testing (on production) Monitoring
  12. 12. Continuous Delivery Requirements Implement one Acceptance Test DeploymentImplementation Monitoring Exploratory Testing (on production)
  13. 13. Continuous Delivery Story Implement one Acceptance Test Monitoring Exploratory Testing (on production) Business Goal MVP DeploymentImplementation A/B Testing
  14. 14. Continuous Delivery Story Implement one Acceptance Test Monitoring Exploratory Testing (on production) Business Goal MVP DeploymentImplementation A/B Testing
  15. 15. Hypothesis Driven Development We Believe That <placing recommended jobs on the job description page> Will Result In <increase the number of relevant jobs applicants see> We Will Have Confidence To Proceed When <we see a 2% increase in number of jobs viewed per session and a .5% increase in number of job applications>

×