The authors present how lineage-driven fault injection evolved from a theoretical model into an automated failure testing system that leverages Netflix’s fault injection and tracing infrastructures.
Bridget Kromhout discusses how to work with the right level of abstraction with DevOps tooling, how different DevOps pieces fit together into a cohesive solution.
Allison Figus performs live demos of Geb tests driven by Spock. She takes a look at code and behind the code to understand what it means and why Geb is a great way to do functional automated testing.
John Hughes presents automated techniques that can improve testing, focusing on what the code should do rather than which cases should be tested, with war stories from Ericsson, Volvo Cars, and Basho.
Paulmichael Blasucci takes a look at FsCheck, a powerful library for doing property-based testing and sophisticated data generation in the CLR ecosystem.
Melissa Tondi discusses mobile testing, advising on creating a device testing matrix and the balance between devices and emulators, along with a comparison between various automated testing tools.
Ben Straub discusses how automating communication tasks with chat robots can have a feedback effect on people and their culture, and how it can be applied to organizations.
Roy van Rijn explains what mutation testing is and how it works, comparing several Java frameworks (PIT, Jester, Jumble) that enable automatic mutation testing in a continuous build.
This talk will present participants with both aspects of Jubula’s personality: Dr Jekyll: writing tests with the Jubula actions in the ITE; Mr Hyde: writing Jubula tests in Jav
Giannakakis and Dalkitsis present how Shazam releases faster, more predictably and with more features by using BDD and automation testing, without slowing down or hindering the development process.
Kolton Andrus presents how Netflix, in order to harden their systems, designed “Failure as a Service” to allow anyone to test and validate how their systems handle failure.