Quality Assurance

Tutorials

TA SOLD OUT! Testing Mobile Applications

Jonathan Kohl, Kohl Concepts, Inc.

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

As applications for smartphones and tablets become incredibly popular, organizations face increasing pressure to quickly and successfully deliver testing for these devices. When faced with a mobile testing project, many testers find it tempting to apply the same methods and techniques used for desktop applications. Although some of these concepts transfer directly, testing mobile applications presents its own special challenges. If you follow the same practices and techniques as you have before, you will miss critical defects.

TB SOLD OUT! Critical Thinking for Software Testers

Michael Bolton, DevelopSense

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

Critical thinking is the kind of thinking that specifically looks for problems and mistakes. Regular people don't do a lot of it. However, if you want to be a great tester, you need to be a great critical thinker, too. Critically thinking testers save projects from dangerous assumptions and ultimately from disasters. The good news is that critical thinking is not just innate intelligence or a talent—it's a learnable and improvable skill you can master.

TE Essential Test Management

Rick Craig, Software Quality Engineering

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

The key to successful testing is effective and timely planning. Rick Craig introduces proven test planning methods and techniques, including the Master Test Plan and level-specific test plans for acceptance, system, integration, and unit testing. Rick explains how to customize an IEEE-829-style test plan and test summary report to fit your organization’s needs. Learn how to manage test activities, estimate test efforts, and achieve buy-in. Discover a practical risk analysis technique to prioritize your testing and become more effective with limited resources.

Concurrent Sessions

T10 Quantifying the Value of Static Analysis

William Oliver, Lawrence Livermore National Laboratory

Thu, 04/11/2013 - 2:00pm

During the past ten years, static analysis tools have become a vital part of software development for many organizations. However, the question arises, “Can we quantify the benefits of static analysis?” William Oliver presents the results of a Lawrence Livermore National Laboratory study that first measured the cost of finding software defects using formal testing on a system without static analysis; then, they integrated a static analysis tool into the process and, over a period of time, recalculated the cost of finding software defects.