Skip to main content

Agile Testing


TL Acceptance Test-Driven Development: Principles and Practices NEW
Ken Pugh, Net Objectives
Tue, 11/10/2015 - 1:00pm

Defining, understanding, and agreeing on the scope of work to be done is often an area of discomfort for product managers, developers, and quality assurance experts alike. The origin of many items living in our defect tracking systems can be traced to the difficulty of performing these initial activities. Ken Pugh introduces acceptance test-driven development (ATDD), explains why it works, and outlines the different roles team members play in the process. ATDD improves communication among customers, developers, and testers. ATDD has proven to dramatically increase productivity and reduce delays in development by decreasing re-work. Through interactive exercises, Ken shows how acceptance tests created during requirement analysis decrease ambiguity, increase scenario coverage, help with effort estimation, and act as a measurement of quality. Join Ken to examine issues with automating acceptance tests including how to create test doubles and when to insert them into the process. Explore the quality of tests and how they relate to the underlying code.

Read more
TN Advanced Test Automation in Agile Development
Rob Sabourin,
Tue, 11/10/2015 - 1:00pm

Agile teams are charged with delivering potentially shippable software at the end of each iteration. In fact, some high-performing agile teams with advanced automation can ship working software every day. They achieve regression confidence with extensive automated test suites and other advanced practices. Rob Sabourin shares automation techniques to improve story and feature testing, exploratory testing, and regression testing. Explore ways that test-driven development (TDD) techniques, precise test and tool selection, appropriate automation design, and team collaboration can be combined to fully integrate testing into agile delivery teams. Learn how automation supports and drives agile testing activities, and how test automation is implemented in diverse organizations. Rob illustrates many types of automation with sample test descriptions, source code, and test scripts. See examples of automated tests for TDD, acceptance test-driven development, and behavior driven-development. Leave with a new toolkit of agile automation methods and techniques.

Read more

Concurrent Sessions

AW2 Data-Driven Software Engineering for Agile Teams
Viktor Veis, Microsoft
Wed, 11/11/2015 - 11:30am

Remember the old days when software engineering teams used to tune software until it passed quality gates, gave golden bits to marketing, and finally threw a big release party? The world was simple, and writing code that worked according to a specification was enough to be a star developer. Viktor Veis says that world has changed. Software now often dials back home to record information about its usage and health. This telemetry flows back to engineering teams who are accountable for making sense out of this data. This is a fundamental shift in the software engineer role. Teams who can leverage data-driven engineering will delight customers by learning more about customers than they know about themselves. Teams who ignore data-driven engineering will continue based on assumptions and eventually lose competitive nerve. Join Viktor to learn how to start data-driven engineering today. Discover a practical approach that sometimes deviates from classical data science but is easy to learn and apply.

Read more
AW10 Getting the Most Value from Feedback Systems: Daily, Every Sprint, and Every Release
Satish Thatte, VersionOne
Wed, 11/11/2015 - 2:45pm

Agile methods are empirical. You must inspect and adapt to make agile work. This requires using effective feedback systems which are vital to your success. Agile teams often suffer from agile feedback systems that are dysfunctional—non-existent, delayed, or no learning from feedback. Satish Thatte explains three agile feedback systems—daily, sprint, and release—and their associated value and challenges. Satish discusses how to improve these feedback systems so they are beneficial to each team member, the project, the program, and the organization. The key is to use templates that capture information and show if the double feedback loops (basic as well as learning feedback loops) are working properly, and then to leverage connections among the agile feedback systems. As a bonus, every delegate receives these templates refined with feedback by industry users during the past six years.

Read more
AT1 Agility without Complexity: Fast and Efficient
Geoff Perlman, Xojo, Inc.
Thu, 11/12/2015 - 10:00am

The Agile Manifesto was stated in less than seventy words. Now, fourteen years later, layer upon layer have been added to it. What was supposed to be a simple philosophy has exploded into a gigantic industry. Much of this layering makes agile seem overly complex. We know developers want to focus on getting their work done, unhindered by rules and regulations. Developers should know the priorities of what to work on, do their work, report their progress, and be held accountable. This process should be supportive, not burdensome. Geoff Perlman shows how a small engineering team built a large project (Xojo) with new releases regularly, using a simplified agile process that gets the job done without adding complexity to the lives of the team. If your team is grumbling about your agile processes, join Geoff as he shows you how to focus on the “meat” of agile so you can be both fast and efficient—without the complexity.

Read more
AT8 Large-Scale Agile Test Automation Strategies in Practice
Geoff Meyer, Dell, Inc.
Thu, 11/12/2015 - 11:30am

After providing an introduction to several key agile testing concepts—including the Automation Triangle and the Test Automation Quadrants—Geoff Meyer discusses approaches to effectively deliver automated testing. Geoff shares practical insights and demonstrates how they were employed in the test automation strategies developed for several large-scale agile projects at Dell. He shows how the overall test strategy and implementation of each underlying agile concept was influenced by the realities of the project’s organization structure, application architecture, incumbent tools, and tester skillsets. Geoff explores the similarities of the projects from their common goals of establishing automated regression suites, achieving in-sprint automation, and test staffing approaches. More importantly, he delves into the implications of organizational structures and how they led to divergent approaches to test strategy from the choice of automation frameworks to the decisions to automate at the REST/SOAP-based API level or UI level.

Read more
AT9 Our Journey to Agile in the Microsoft Developer Division
Gregg Boer, Microsoft
Thu, 11/12/2015 - 1:30pm

This is the story about the Microsoft Developer Division and their two-year journey to agile—from shipping every three years to shipping every three weeks. In the old days, long stabilization phases were part of its DNA. Managers were rewarded for micromanagement. Commitments were made months in advance. Maintaining the appearance of meeting commitments was valued over transparency. Gregg Boer shares how this organization within Microsoft transitioned to one that values agile principles—controlling technical debt, enabling teams, eliminating bogus commitments, and rewarding transparency. When applying agile to such a large, traditional organization, the key to success is allowing autonomy at the team level, while ensuring alignment with the organization. Gregg shares successes as well as colossal failures. Learn how management sets direction while teams own their own backlog, how communication up and down can be transparent and healthy, and other lessons on their journey to agile.

Read more
AT10 Software Craftsmanship and Agile Code Games
Mike Clement, Greater Sum
Thu, 11/12/2015 - 1:30pm

Musicians and athletes spend most of their time practicing—not performing. If as software developers we just learn on our job and don’t practice, we will continue to make mistakes on code meant for customers. We must improve the quality of our skills which will, in turn, improve the quality of our code. Mike Clement believes we must take time to practice, allowing ourselves to improve our skills and develop better “code sense.” Learn how the Software Craftsmanship Manifesto provides a framework for us to improve in our craft. By learning a variety of code games, we can assemble a full toolbelt of activities to help us improve. We then can take these games and give others the opportunity to improve and thus raise the level of the whole community. Join Mike to take a whirlwind tour of some different agile code games and discover what it means to become a true software craftsman.

Read more
AT12 Automated Continuous Test Selection Methods for DevOps
Marc Hornbeek, Spirent Communications
Thu, 11/12/2015 - 1:30pm

Static, fixed test suites often do not work well with DevOps—especially in large-scale  environments—because the test suites are either too large to execute in the fast continuous integration cycle times or they consume too many resources to be efficient. As the scale of continuous testing for DevOps systems increases in size and complexity, test selection should be automated. Marc Hornbeek shares a comparison of test selection methodologies that resolve the inherent conflicts in coverage, resources, and time for continuous testing. Marc provides instructions on how to implement a test selection tool which uses both software change information and system level risks to create a scalable solution that suits DevOps cycles and conserves resources. As a bonus, Marc provides instructions on how to automate test results analysis and gives each session attendee a free copy of a DevOps Best Practices Assessment Tool.

Read more