STARCANADA 2013 - Software Testing Conference

PRESENTATIONS

STARCANADA 2013: Maybe We Don’t Have to Test It

Testers have been taught they are responsible for all testing. Some even say “It’s not tested until I run the product myself.” Eric Jacobson thinks this old school way of thinking can hurt a tester’s reputation and—even worse—may threaten team success. Learning to recognize opportunities...
Eric Jacobson, Turner Broadcasting Inc.
STARCANADA 2013: Quantifying the Value of Static Analysis

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...
William Oliver, Lawrence Livermore National Laboratory
STARCANADA 2013: The Tester's Role in Agile Planning

If testers sit passively through agile planning, important testing activities will be missed or glossed over. Testing late in the sprint becomes a bottleneck, quickly diminishing the advantages of agile development. However, testers can actively advocate for customers’ concerns while...
Rob Sabourin, AmiBug.com
Testing After You’ve Finished Testing

Stakeholders always want to release when they think we’ve “finished testing”. They believe we have revealed “all of the important problems” and “verified all of the fixes,” and now it’s time to reap the rewards.
Jon Bach, eBay Inc.
Testing Challenges within Agile Teams

In her book Agile Testing: A Practical Guide for Testers and Agile Teams, Janet Gregory recommends using the automation pyramid as a model for test coverage. In the pyramid model, most automated tests are unit tests written and maintained by the programmers,and tests that execute...
Janet Gregory, DragonFire Inc.
The Role of Emotion in Testing

Software testing is a highly technical, logical, rational effort. There's no place for squishy emotional stuff here. Not among professional testers. Or is there? Because of commitment, risk, schedule, and money, emotions can run high in software development and testing. It is easy to...
Michael Bolton, DevelopSense Inc.
The Seven Deadly Sins of Software Testing

Many smart, otherwise-capable testers sabotage their own careers by committing one or more of the deadly sins of testing: irrelevance/redundancy, ignorance of relevant skills, obstructionism, adversarialism, nit-picking, blindness to project/organizational priorities, and last-moment-ism.
Rex Black, RBCS Inc.
Usability Testing: Personas, Scenarios, Use Cases, and Test Cases

To create better test cases, Koray Yitmen says you must know your users. And the path to better test case creation in usability testing starts with the segmentation and definition of users, a concept known as personas. Contrary to common market-wise segmentation that focuses on users'...
Koray Yitmen, UXservices
Using Mindmaps to Develop a Test Strategy

Your test strategy is the design behind your plan—the set of big-picture ideas that embodies the overarching direction of your test effort. It captures the stakeholders’ values that will inspire, influence, and ultimately drive your testing.
Fiona Charles, Quality Intelligence
Whiteboarding—for Testers, Developers, and Customers, Too

How can testers spend more time doing productive testing and waste less time preparing "useless" project documentation? Rob Sabourin employs whiteboarding techniques to enable faster, easier, and more powerful communication and collaboration—without all the paperwork. 
Rob Sabourin, AmiBug.com

Pages

CMCrossroads is a TechWell community.

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