Tutorials

Full-Day Tutorials

Tutorials take place after the conference on July 18, 2012

Managing and Integrating Exploratory Testing

James Lyndsay
There are many ways to manage exploration, some fruitful, others harmful. Some even apply to exploratory testing. This one-day experiential workshop directly addresses the question of how to manage exploratory testing well, and how to integrate it with existing test strategies. We will identify and interact with a diverse collection of approaches, using simulation, games, discussion and our imaginations. Along the way, we will talk about how to get the best out of time spent exploring, how to incorporate tools, how to grow skills, work with audit, and how to measure your progress.  This is your chance to exchange ET management approaches and perhaps to play with the ways you’ve always wanted to try. You’ll come away with a bunch of real life examples, and a broader understanding of the strategies and application of exploratory testing.

The (Thinking) Tester in the User Story Workshop.

Elisabeth Hendrickson
A user story is simply a placeholder for a conversation. The user story workshop is where that conversation happens. In these workshops, the team, including programmers, testers, and the product owner, elaborate the user story. They work together to reach a shared understanding of the scope of the story and to define “Done” in concrete terms using examples. They then distill the examples into tests (checks) that drive the development effort. Testers (more specifically, thinking testers) have a wealth of insight into where things tend to go wrong. By participating in user story workshops, testers have the opportunity to use their testing super powers to prevent problems, not just detect them.  In this tutorial you will experience a user story workshop and practice distilling examples into acceptance tests. You’ll discover how you can apply your testing skills at the very beginning of the cycle, before requirements are even defined. And you’ll learn a set of heuristics you can use to ensure the effectiveness of your user story workshops and the resulting acceptance tests.

Testing Mobile Apps & Mobile Websites

Karen Johnson
Thinking testers ask questions.  Testers ask about the product, the technical environment and they ask questions about the users. In testing on the mobile environment, testers ask questions about phone models, network carriers, operating system versions, native browsers and applications as well as asking questions about emulators and automated tools. The reality is that the mobile environment adds a different context to testing as well as the user audience has access to a dazzling array of phones and devices. A typical user session on a mobile device might not be at all similar to a user session on a desktop computer. How does a thinking tester adjust for testing in the mobile environment?This tutorial explores those questions, provides an open forum for discussion, and offers hands-on exercises.Students should bring a laptop computer and/or a mobile device to participate in hands-on testing.  It is recommended that you have Admin access to your laptop.

Critical Thinking Skills for Testers

Michael Bolton
  • Every test must have an expected, predicted result.
  • Effective testing requires complete, clear, consistent, and unambiguous specifications.
  • Bugs found earlier cost less to fix than bugs found later.
  • Testers are the quality gatekeepers for a product.
  • Repeated tests are fundamentally more valuable.
  • You can’t manage what you can’t measure.
  • Testing at boundary values is the best way to find bugs.
  • Test documentation is needed to deflect legal liability.
  • The more bugs testers find before release, the better the testing effort.
  • Exploratory testing is unstructured testing, and is therefore unreliable.
  • Adopting best practices will guarantee that we do a good job of testing.

If you’re a tester or a test manager, you’ve probably heard statements like these touted as universal, unquestionable truths about testing.  At best, these bits of mythology and folklore are heuristics—fallible methods for solving a problem or making a decision.  At worst, they’re potentially dangerous simplifications or outright fallacies that can threaten a tester’s credibility, a product’s value, or an organization’s business.

In this workshop, we’ll question the myths of software testing; examine common cognitive biases, and the critical thinking tools that can help to manage them; learn modeling and general systems approaches to manage complexity and observational challenges; and work through exercises that model difficult testing problems—and suggest approaches to solving them.

Participants are encouraged to bring a Windows-based laptop computer to the workshop.

The First Hit is Free: Using Automation to drive a modern development process

Adam Goucher
Testers and those in other Quality-related fields are often rebuffed in their attempts at process change, as they can seem like change for the sake of change. Even with the rise in awareness of things like Continuous Delivery, DevOps and the Lean Startup, moving an entrenched process to these often gets tied up in politics.There are entire books on understanding human and organizational behaviors in order to affect change. This tutorial is about how to use [functional] automation to move your processes towards one similar to Continuous Delivery. It ends up that the tricks and techniques to make this successful are the same as those necessary in the organization at large, so we prove them here and move them out closer and closer to productionNot only will we participants learn about the ‘big picture’ of Continuous Delivery, but we will move a change (or multiple changes!) through a Deployment Pipeline.Please bring a laptop.
 

Comments are closed.