Agile Dev West 2017 - Software Testing

In test automation, we often must use several tools that have been developed or acquired over time with little consideration of an overall plan or architecture, and without considering the need for integration. As a result, productivity suffers and frustrations increase. Join Mike Sowers as he shares experiences from multiple organizations in creating an integrated test automation plan and developing a test automation architecture. Mike discusses both the good (engaging the technical architecture team) and the bad (too much isolation between test automators and test designers) on...

Ever since distributed software became popular, developers have been choosing whether to use monolithic architectures or service-oriented architectures. With the advancement of cloud infrastructure and the widespread implementation of agile methodologies, the latter approach has been getting much easier. David Litvak describes how a monolithic application—due to its ever increasing technical debt—can become too big to support. He explores how to gradually reduce the size by extracting its components into smaller services, so ultimately the application is decoupled and highly...

Even though most teams appreciate the benefits of test automation, it is commonly viewed as too time-consuming to be included as part of an agile sprint. This results in automation being done in isolation, typically months after the user story has been completed. This can lead to several problems including automation team members being disengaged and missing key aspects of the requirements, as well as teams going through a period where new features are being introduced but no regression testing is occurring. Angie Jones provides agile-friendly approaches to test automation that allow teams...