STAREAST 2011 - Software Testing Conference

PRESENTATIONS

STAREAST 2011: Performance Engineering: More Than Just Load Testing

Performance testing that is only done at the last minute–just prior to launch–is the wrong approach for complex systems which have many opportunities for performance bottlenecks. Rex Black discusses a different approach-performance engineering-that is far more comprehensive and valuable than merely performing load testing during the system test.
Rex (Red) Black, J9 Technologies
STAREAST 2011: Service-driven Test Management

Over the years, the test manager's role has evolved from "struggling to get involved early" to today's more common "indispensable partner in project success." In the past, it was easy to complain that the testing effort could not be carried out as planned due to insufficient specs, too few people, late and incomplete delivery, poor test environments, etc. Martin Pol explores why–and how–test managers must provide a high level of performance within their projects and organization.
Martin Pol, Polteq Test Services B.V.
STAREAST 2011: Seven Key Factors for Agile Testing Success

What do testers need to do differently to be successful on an agile project? How can agile development teams employ testers' skills and experience for maximum value to the project? Janet Gregory describes the seven key factors she has identified for testers to succeed on agile teams. She explains the whole-team approach of agile development that enables testers to do their job more effectively. Then, Janet explores the "agile testing mindset" that contributes to a tester's success.
Janet Gregory, DragonFire, Inc.
Stop Writing Test Cases! It's All About Models and Exploration

With rapid application development environments and sometimes daily product releases, test cases can be an unnecessary burden on testers. Test cases are expensive to write, often fail to adequately describe interrelationships, and are ineffective for whole-team collaboration. Brett Leonard explains how you can employ software models to replace test cases as your main vehicle for test design, execution, and reporting.
Brett Leonard, Construction Software Technologies (iSqft.com)
Streamline Test Planning with Business Process Models

Test-QA professionals and business-systems analysts have always lived in two separate worlds, with test planning and design segregated from the task of creating business process models. However, a business process modeling (BPM) diagram–which visually shows the break down of activities into individual tasks–for the test project can help Test-QA managers see how to organize multiple tasks and create an end-to-end test project flow.
Filip Szymanski, Hewlett Packard
Test Execution and Results Analysis: Time for a "Legal" Separation

Generally, testers mix test execution and test analysis. Typically, each test case execution also does its bit of analysis focusing on the feature under test, comparing actual to expected results. Jacques Durand explains that by declaring and enforcing a "legal" separation between execution and analysis tasks, testers' perspectives automatically change. Rather than focusing only on actual vs.
Jacques Durand, Fujitsu Software Corporation
Testing for Web Accessibility

Because 10% to 20% of the general population has disabilities that can impact their ability to use software, systems should be developed to accommodate their needs. Even though web accessibility requirements are included in many development projects, they are often not fully understood and verified during testing. Join David Leistner as he examines the Web Accessibility Initiative and Section 508 of the Rehabilitation Act. First, David explains what web accessibility is, its importance, and who it affects.
David Leistner, National Archives and Records Administration
The 2011 Survival Guide: Lessons for Test Professionals

When we are in dangerous situations, we need a well-thought-out survival guide to help save ourselves and others. These lifesaving principles and skills provide the basic necessities for life and help us think straight, navigate safely, signal for help, and avoid unpleasant consequences of interactions with our environment. Julie Gardiner shares her 2011 Survival Guide for testers and test managers living in today's challenging business and technical environments.
Julie Gardiner, Grove Consultants
The Agile Build Pipeline: A Tester's Lessons Learned

When Insurance Australia Group wanted to launch a new online car insurance service, complex technical issues called for early integration and strong testing capabilities. The project was distributed across multiple partners, each working on different horizontal components and employing different development approaches. In this environment, it was critical to continuously integrate the software and test-test-test.
Kristan Vingrys, Thoughtworks
The Cassandra Syndrome: The Tester's Dilemma

In Homer's Iliad, we read of Cassandra, who had the gift of prophecy and the curse of having no one listen to her. Many testers have felt like Cassandra, but why? When engaged in what many perceive as "negative" activities–predicting problems, discovering defects, and reporting incidents–testers often are seen as negative people who don't make a "positive" contribution to the project. While most team members focus on making software work, testers focus on what doesn't work.
Rick Hower, Digital Media Group, Inc.

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.