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
Ian Cooper reminds what was Kent's original proposition on TDD, what misunderstandings occurred along the way and suggests a better approach to TDD, one that supports development rather impeding it.
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.
Chris Rowett explores the key stages on the DevOps journey: Complete Agile Development, Continuous Delivery, Continuous Validation, and "Closed Loop".
Andrea Burbank discusses the evolution of Pinterest's A/B testing platform and how one can learn from their mistakes to go from simply running experiments to actually deriving insights.
Danielle Jabin shares some of Spotify's key takeaways from their A/B testing efforts and the challenges they faced in building out their A/B testing infrastructure.
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.
David Hussman advises on story mapping: pick an idea, choose someone that might be helped by that idea, build a story map as a way to explore that person’s experience, and start the customer journey.
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.