Skip to main content

Agile Testing


MF SOLD OUT! Acceptance Test-Driven Development: Mastering Agile Testing
Nate Oster, CodeSquads, LLC
Mon, 06/03/2013 - 8:30am

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.

Read more
TF Agile Project Failures: Root Causes and Corrective Actions
Jeff Payne, Coveros, Inc.
Tue, 06/04/2013 - 8:30am

Agile initiatives always begin with the best of intentions—accelerate delivery, better meet customer needs, or improve software quality. Unfortunately, some agile projects do not deliver on these expectations. If you want help to ensure the success of your agile project or get an agile project back on track, this session is for you. Jeff Payne discusses the most common causes of agile project failure and how you can avoid these issues—or mitigate their damaging effects.

Read more

Concurrent Sessions

AW8 The Agile Tester’s Mindset
Janet Gregory, DragonFire, Inc.
Wed, 06/05/2013 - 2:15pm

On traditional projects, testers usually join the project after coding has started—or even later when coding is almost finished. Testers have no role in advising the project team early regarding quality issues but focus only on finding defects. They become accustomed to this style of working and adjust their mental processes accordingly. On agile projects, where testers must collaborate closely with customers and programmers throughout the development lifecycle, their focus changes from finding defects to preventing them.

Read more
AW12 Transform Your Agile Test Process to Ship Fast with High Quality
Penny Wyatt, Atlassian
Wed, 06/05/2013 - 3:45pm

Until 2009, the Atlassian JIRA team shipped a major release of its software every nine to twelve months. Everything was tested—every story and every bug fix—and everything still contained serious bugs. Story development moved quickly, but after the feature-complete date, several month-long hardening periods were required to make the software actually shippable. Integrating the release into Atlassian’s hosted platform took another three or four months.

Read more