Agile Testing

Keynotes

Jonathan Kohl, Kohl Concepts, Inc.

Thu, 04/11/2013 - 8:30am

The last exciting era in testing was in the late ‘90s when the web turned technology on its ear, the agile movement overthrew our processes, and the rise of open source gave us accessible and innovative tools. However, since then, Jonathan Kohl finds it has been a lot of the same-old, same-old: more web applications, variants of agile, and testing tool debates. After a while, you start to feel like you’ve “Been there, Done that, Got that t-shirt.” However, testing doesn’t have to be a rehash of all the things you’ve done before. It is an exciting time to be a tester!

Tutorials

TD Planning Your Agile Testing: A Practical Guide

Janet Gregory, DragonFire, Inc.

Tue, 04/09/2013 - 8:30am

Traditional test plans are incompatible with agile software development because we don't know all the details about all the requirements up front. However, in an agile software release, you still must decide what types of testing activities will be required—and when you need to schedule them. Janet Gregory explains how to use the Agile Testing Quadrants, a model identifying the different purposes of testing, to help your team understand your testing needs as you plan the next release.

TI SOLD OUT! Acceptance Test-driven Development: Mastering Agile Testing

Nate Oster, CodeSquads, LLC

Tue, 04/09/2013 - 1:00pm

On agile teams, testers can struggle to “keep up” with the pace of development if they continue employing a waterfall-based verification process—finding bugs after development. Nate Oster challenges you to question waterfall assumptions and replace this legacy verification testing with Acceptance Test-driven Development (ATDD). With ATDD, you “test first” by writing executable specifications for a new feature before development begins.

Concurrent Sessions

W6 Concurrent Testing Games: Developers and Testers Working Together

Nate Oster, CodeSquads, LLC

Wed, 04/10/2013 - 12:45pm

The best software development teams find ways for programmers and testers to work closely together. These teams recognize that programmers and testers each bring their own unique strengths and perspectives to the project. However, working in agile teams requires us to unlearn many of the patterns that traditional development taught us.

W7 Testing Challenges within Agile Teams

Janet Gregory, DragonFire, Inc.

Wed, 04/10/2013 - 12:45pm

In her book Agile Testing: A Practical Guide for Testers and Agile Teams, Janet Gregory recommends using the automation pyramid as a model for test coverage. In the pyramid model, most automated tests are unit tests written and maintained by the programmers,and tests that execute below the user interface—API-level tests that can be developed and maintained collaboratively by programmers and testers. However, as agile becomes mainstream, some circumstances may challenge this model.

W11 An Agile Test Automation Strategy for Everyone

Gerard Meszaros, Independent Consultant

Wed, 04/10/2013 - 2:00pm

Most systems are not designed to make test automation easy! Fortunately, the whole-team approach, prescribed by most agile methodologies, gives us an opportunity to break out of this rut. Gerard Meszaros describes the essential elements of a practical and proven agile test automation strategy. He describes the different kinds of tests we need to have in place and which team members should prepare and automate each kind of test.

W12 How Spotify Tests World Class Apps

Alexander Andelkovic, Spotify

Wed, 04/10/2013 - 2:00pm

In today’s competitive world, more and more HTML5 applications are being developed for mobile and desktop platforms. Spotify has partnered with world-renowned organizations to create high quality apps to enrich the user experience. Testing a single application within a few months can be a challenge. But it's a totally different beast to test multiple world-class music discovery apps every week. Alexander Andelkovic shares insights into the challenges they face coordinating all aspects of app testing to meet their stringent testing requirements.