Gerard Meszaros advises on using the right abstraction level and automation tools when creating unit or system-level tests.
Roy Rapoport discusses canary analysis deployment and observability patterns he believes that are generally useful, and talks about the difference between manual and automated canary analysis.
Baraa Basata introduces Ansible, comparing it with Chef and Capistrano and exploring automation principles: disposable servers, package management, and applying design principles to infrastructure.
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.
Janet Gregory explains how testing activities are included throughout the Agile process, and how a tester can add value, discussing ATDD (Acceptance Test Driven Development), and exploratory testing.
Terry Bunio outlines the requirement of a tSQLt-based ETL test framework, showing how tests execute in a demonstration.
John Hughes discusses automated testing techniques that can catch more code defects, with war stories from the likes of Ericsson, Volvo Cars, and Basho Technologies.
Seb Rose explores the choices a team needs to make when considering which Agile test practices to adopt, urging teams to practice, practice, practice until they are happy with the way they code.