Agile Testing

Tutorials

MB Continuous Delivery: Rapid and Reliable Releases with DevOps

Bob Aiello, CM Best Practices Consulting

Mon, 06/02/2014 - 8:30am

DevOps is an emerging set of principles, methods, and practices that enables the rapid deployment of software systems. DevOps focuses on lowering barriers between development, testing, security, and operations in support of rapid iterative development and deployment. Many organizations struggle when implementing DevOps because of its inherent technical, process, and cultural challenges. Bob Aiello shares DevOps best practices starting with its role early in the application lifecycle and bridging the gap with testing, security, and operations.

ME Acceptance Test-Driven Development: Mastering Agile Testing SOLD OUT

Nate Oster, CodeSquads, LLC

Mon, 06/02/2014 - 8:30am

On agile teams, testers can struggle to keep pace with 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.

MO Essential Test-Driven Development

Rob Myers, Agile Institute

Mon, 06/02/2014 - 1:00pm

Test-driven development (TDD) is a powerful technique for combining software design, unit testing, and coding in a continuous process to increase reliability and produce better code design. Using the TDD approach, developers write programs in very short development cycles. The developer first writes a failing automated test case that defines a new function or improvement, then produces code to pass that test, and finally refactors the new code to acceptable standards. The developer repeats this process many times until the behavior is complete and fully tested.

MP Agile Test Automation: Do It Early and Often SOLD OUT

Janet Gregory, DragonFire, Inc.

Mon, 06/02/2014 - 1:00pm

Agile teams deliver “potentially” shippable software at the end of every iteration—typically, one to four weeks but possibly as often as daily. This goal can't be achieved without comprehensive automated tests, a place where many teams struggle. The challenge of automating functional regression tests even frightens many experienced and competent testers. But it doesn’t have to be this way.

TE A Test Leader’s Guide to Agile

Bob Galen, Velocity Partners

Tue, 06/03/2014 - 8:30am

Much of the work of moving traditional test teams toward agile methods is focused on the individual tester. Often, the roles of test director, test manager, test team leader, and test-centric project manager are marginalized―but not in this session where we’ll focus on agile testing from the test leader’s perspective.

Keynotes

K2 For Maximum Awesome

Joe Justice, Scrum, Inc

Wed, 06/04/2014 - 10:15am

An agile hardware and engineering company of 500 collaborators in twenty countries, Team WIKISPEED uses test-first development practices, is run by Scrum teams, and produces road legal cars, micro-houses, and social-good projects. Joe Justice shares how their 100-MPG road car was created in just three months through object-oriented design, iterative development, and agile project management.

K3 An Agile Throwdown: Munich Takes on the Columbus Agile Benchmark Study

Michael Mah, QSM Associates, Inc.

Thu, 06/05/2014 - 8:30am

Agile has not only gone mainstream, it’s gone global. Data on agile team performance, time-to-market, and quality have emerged in the past decade. In 2012, a group of Columbus, Ohio, companies—business, IT, and financial services firms—participated in the first ever “Columbus Agile vs. the World” study. They collected velocity, schedule, effort, staffing, and quality data which were compared against QSM’s Software Lifecycle Management (SLIM) database. Analysis revealed delivery was 31 percent faster with 75 percent fewer defects than industry norms. Enter Munich, Germany.

K4 Producing Product Developers

David Hussman, DevJam

Thu, 06/05/2014 - 3:45pm

Many teams and organizations have found agile methods help them produce more. Where critical thinking is alive, a more important question arises: Are we producing the right thing? Even though agile tools and processes have helped produce more, they often fail to help us produce the right product, change our focus to product over process, or improve product learning.

Concurrent Sessions

AT4 Risk-Based Testing in Agile Projects

Erik van Veenendaal, Improve Quality IT Services BV

Thu, 06/05/2014 - 10:15am

Many projects implicitly use some kind of risk-based approach for prioritizing testing activities. However, critical testing decisions should be based on a product risk assessment process using key business drivers as its foundation. For agile projects, this assessment should be both thorough and lightweight. Erik van Veenendaal discusses PRISMA (PRoduct RISk MAnagement), a highly practical method for performing systematic product risk assessments. Learn how to employ PRISMA techniques in agile projects using Risk Poker.

AT8 Key Success Factors for Agile Testing

Janet Gregory, DragonFire, Inc.

Thu, 06/05/2014 - 12:45pm

How is testing different for successful agile projects? How can agile development teams employ testers’ skills and experience for maximum project value? Janet Gregory describes key factors she has identified for agile teams to succeed and explains the whole-team approach of agile development that enables testers to do the most effective job. Then, Janet explores the “agile testing mindset” that contributes to a tester’s success. She describes the different kinds of information that testers on an agile team need to obtain, create, and provide for the team and product owner.

AT10 Test-Driven Development Illustrated

Carsten Czeczine, binaris informatik GmbH

Thorsten Werle, binaris informatik GmbH

Thu, 06/05/2014 - 2:15pm

Agile methods help development teams create good quality code and ensure this with early testing. Test-driven development (TDD) is the preferred approach to accomplish this. First, you write the tests; then, you write the code so the tests pass. Sound simple? It is—when done correctly. And this is often where the trouble starts. Thorsten Werle and Carsten Czeczine explain the basic steps of TDD. You’ll see how to write tests for non-existing code using the compiler as your first testing tool. You’ll learn that TDD does not start with unit testing but with an integration test.

AT12 Session-Based Exploratory Testing in Agile Projects

Bob Galen, Velocity Partners

Thu, 06/05/2014 - 2:15pm

One of the challenges associated with testing agile projects is selecting test techniques that “fit” the dynamic nature of agile practices. How much functional and non-functional testing should you do? What is the appropriate mix of unit, integration, regression, and system testing? How do you balance these decisions in an environment that fosters continuous change and shifting priorities? Bob Galen has discovered that session-based exploratory testing (SBET) thrives in agile projects and supports risk-based testing throughout development.