Menu
Test automation guide: How to move away from chain tests
My name is Erwin Manders, I am currently a Solution Architect for Rabobank in the Netherlands. Previously, I have many years of java development experience in high scalable and distributed application environments. Since this year I am working as a solution architect within online access management domain of Rabobank, working on the next generation of solution to provide our customers with a smooth and future-proof way for authentication and authorizations.
I am a speaker since a few years, with keywords being Java, Reactive programming, Cloud Native & Continuous delivery. My colleagues describe me as a very energetic speaker. I prefer to give code examples in every talk, and make sure that my audience can use my examples in their daily practise.
Abstract
How often do you deploy your features to production? Is your team able to deploy to production on Friday afternoon? Does your product owner ask you to perform chain tests before approving your change?
Many teams nowadays have embraced the value of automated unit and integration testing, but these tests alone do not fully guarantee our feature is working and many teams still do some form of chain testing before moving to production. We cannot achieve continuous delivery this way, so additional test automation is required to guarantee production stability. Integration of test tools within our langscape helps our development teams to speed up more.
I will demonstrate how Rabobank has achieved continuous delivery by automating various levels of the test pyramid, from unit testing to container smoke tests, contract tests with pactflow.io and A/B testing with split.io. While java will be used as main language in the demo’s, the practises that wil be discussed are applicable to all programming languages
