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.
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.
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.
Ivan Inozemtsev discusses the automated testing difficulties of an Eclipse-based application’s UI, introducing the RCP Testing Tool, how it helps and how it is implemented underneath.
Jeff Morgan shares lessons learned helping organization adopt test automation, along with techniques for keeping the automation code simple, clean and maintainable.
John Hughes discusses automated techniques that can improve testing, with war stories from Ericsson, Klarna and Volvo Cars, showing how to nail the hard stuff.
Emma Armstrong shows how to use Selenium and NUnit to automate web testing for C# applications. The sessions is useful to developers of other languages that Selenium supports – Java, Python, Ruby.
Dmytro Mindra discusses the tools and practices used for a game engine: Unit Testing and Test automation, Unity Runtime Test Framework, Continuous Integration, Game Test Framework, Performance Tests.
Wojciech Seliga shares from experience how complex it can be to deal with thousands of tests -unit, functional, integration, performance- for Atlassian JIRA and what they did to bring it under control
Patrick Smacchia shares code analysis-related practices - structuring code, measuring code quality, automated tests, code contracts, reporting progress, trending- based on his experience with NDepend.