STAREAST 2017 - Agile Testing Session Topics | TechWell

Conference archive

STAREAST 2017 - Agile Testing

Wednesday, May 10

Jess_Lancaster
TechSmith
W4

Pairing: The Secret Sauce of Agile Testing

Video
Add to calendar
Wednesday, May 10, 2017 - 11:30am to 12:30pm

Finding time to learn test techniques, mentor other testers, grow application knowledge, and cross-train your team members is a daunting task with a complicated recipe. What if you could do these things while testing and finding bugs? Enter Pair Testing. What’s that? Well, maybe you’ve heard of pair programming. It’s like that—only you’re testing rather than programming. And it’s the secret sauce of agile testing because it makes your routine, bland testing so much more fun! Testers on Jess Lancaster’s team use pair testing not only to make better software but also to foster better...

Mary_Thorn
Ipreo
W10

Agile Testing at Scale

Add to calendar
Wednesday, May 10, 2017 - 1:45pm to 2:45pm

Over the past twenty years, Mary Thorn has had the opportunity to work at many startups, creating several QA/test departments from scratch. For the past ten years, she has done this in agile software companies. Recently Mary moved from leading small agile test organizations to leading a large agile test organization. She has learned how to lead agile testers and agile testing in large contexts. Mary takes you through what she has learned, identifies the keys to transitioning your test organization as it grows, and discusses the techniques required to lead it through the changes. Agile...

Jim_Peers
PQA Testing
W16

When the System Creaks: Lessons Learned in Agile Maintenance

Add to calendar
Wednesday, May 10, 2017 - 3:00pm to 4:00pm

We often talk about agile in terms of development of new systems, sometimes called greenfield projects. These scenarios present us with a “cleaner” version of agile. But Jim Peers is asking the question: What about agile methodologies when applied to the maintenance of a mature product? A mature product brings into play many more variables—addition or upgrading of features, addressing technical debt, bug fixing, security and accessibility concerns, and working with an aging codebase. And each variable brings its own challenges. By necessity, these scenarios can force us to adapt our work...