Teams are sometimes asked to turn a mess of undocumented, poorly structured legacy code into a robust product under impossible deadlines. Test strategies blending automation, exploration, and refactoring can help focus development efforts and converge even the most chaotic projects. But, where do you start? Join Jonathan Solórzano-Hamilton as he shows how automation can help drive products into a state of release readiness. Learn how refactoring, test-driven development, SOLID principles, dependency injection, and mocking frameworks help break down complex development problems into actionable chunks to delivering reliable, self-documented, and high-performing products. Jonathan walks you through the concepts of “Single responsibility”, “Open/closed”, “Liskov substitution”, “Interface Segregation”, and “Dependency Inversion”.

QA departments always feel the pressure to start testing quickly, even if the ever-changing software being tested isn’t ready. A bought-in test automation strategy can keep a project on track.

The cognitive skills of testing are being threatened by two major forces: the assumption that automation can replace all other forms of testing, and the acceptance of lower quality by consumers. You might be feeling like you’re living on an eroding island, but there is a way to adapt and even thrive using your testing skills. Your project still needs to have someone who will question assumptions, examine design, create experiments, analyze data, and report meaningful metrics. It needs your social skill to connect teams who work in silos, bring customer insights to light, and track risks that no one seems to make time to think about. For twenty-two years, Jon was a tester, test manager, test trainer, and test consultant. Now he’s a senior program manager and uses his testing skills differently. What’s your experience? Jon will ask you a few questions via an anonymous polling app and show the results during the session.

Thanks to the trend toward DevOps and continuous delivery, traditional testing isn’t enough. Including test automation in your strategy is a good start, but your testing approach needs to change.