STARWEST 2018

PRESENTATIONS

Reduce Wait Time with Simulation + Test Data Management

Data has become the most significant roadblock that testers face today. In fact, up to 60% of a tester’s time is spent waiting for data. Chris Colosimo shows that many factors contribute to this wait time, including internal requirements from the test data management team to pull data in the proper form, wait times for sanitized or “test-safe” data, or, most importantly, building data sets that do not exist. Compounding these challenges is the inherit complexity of today’s data.

Chris Colosimo

Risk Based Testing – Are You Talking the Talk, Or Walking the Walk?

Risk-based testing is essential to focus our testing, but it is not always easy to apply to our projects. Risk management tends to focus more on project and process risks (i.e., Will we make the deadline? Do we follow our processes?) and less on the product risks that can act as a foundation for a risk-based approach to test.

Gitte Ottosen

Risk Based Testing: Communicating WHY You Can't Test Everything

The idea of testing everything is a popular one—in fact many stakeholders think that’s exactly what their quality teams do. It usually isn’t and can’t be; but how can teams communicate this? Join Jenny Bramble as she helps to pave the way using the language of risk-based testing. By defining risk in two simple parts, the team and project have a tangible and usable metric.

Jenny Bramble

Testing Imprecise Requirements

Articles on abc.net and elsewhere reported that Volvo has recently discovered a non-traditional requirement: Any self-driving vehicle approved for use outside Australian cities must recognize kangaroos on or near the roadway and take proper actions. The kangaroo’s bounce confused the large animal detector! In this session, industry expert David Gelperin shares a new perspective on the value of imprecise requirements and explores the nature of testing them.

David Gelperin

Testing In The Dark

Isn’t it amazing? Stakeholders drop software on our desks and expect us to test it—without any requirements, design, or product knowledge whatsoever. About the only clear thing is the absurd and unrealistic deadline. We are expected to bend over backward, spread magic pixie dust, and heroically test quality into a product we have never heard of before. But testing in the dark is not impossible, and as Rob Sabourin shows, it can even be a very valuable and fun experience.

Rob Sabourin
Testing Outside of the Box

The cognitive skills of testing are being threatened by two major forces: the assumption that automation can replace all other forms of testing, and the acceptance of lower quality by consumers. You might be feeling like you’re living on an eroding island, but there is a way to adapt and even thrive using your testing skills. Your project still needs to have someone who will question assumptions, examine design, create experiments, analyze data, and report meaningful metrics.

Jon Bach

Testing Your Tests: Securing Confidence In Your Automation

The growth of automation testing in today’s software development organizations is changing the way we test applications. Software development practices have matured over the last thirty years to include all forms of testing in order to verify software quality. In the last ten years, there has been a huge spike in the adoption of automated tests, effectively replacing some manual testing practices and supplementing traditional testing activities.

Max Saperstone

The Art of Software Investigation

Although processes and tools play an important role in software testing, the most important testing tool is the mind. Like scientists, testers search for new knowledge and share discoveries—hopefully for the betterment of people’s lives. More than sixty years ago, William I.B. Beveridge reframed discussion of scientific research in his classic book The Art of Scientific Investigation. Rather than add to the many texts on the scientific method, he focused on the mind of the scientist.

Ben Simo

The Life of a Tester, from Once Upon a Time to Happily Ever After

[video:https://youtu.be/WGatcZxwmHc width:300 height:200 align:right]

Jennifer Bonine

The Logic of Verification

Software testing is sometimes described as “verification and validation”—or, according to Wikipedia, “the process of checking that a software system meets specifications and that it fulfills its intended purpose.” Yet, renowned tester and teacher Michael Bolton argues, if we examine the concept and logic of verification, we quickly recognize that there are serious limitations to what can and cannot be checked and verified. This is not to say that checking is a bad thing—on the contrary; checking can be very valuable.

Michael Bolton

Pages

AgileConnection is a TechWell community.

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