ET Workshop v Opening©2002 Amland Consulting0-1 Exploratory Testing v Workshop in Risk-Based Agile Testing Parts of this class have been excerpted from: Rapid Software Testing, by James Bach, Black Box Software Testing, by Cem Kaner, How to build and lead an effective test team, by Lloyd Roden, Ståle Amland, Amland Consulting, Hulda Garborgsv. 2, 4020 STAVANGER, NORWAY Phone: , Fax: WEB:

ET Workshop v Opening©2002 Amland Consulting0-2 Introductory Note Parts of this class have been excerpted from: Rapid Software Testing, by James Bach, Black Box Software Testing, by Cem Kaner, How to build and lead an effective test team, by Lloyd Roden, Grove Consultants, Who am I? Name: Ståle Amland WEB: Phone: The reference text will be located about here.....

ET Workshop v Opening©2002 Amland Consulting0-3 License agreement James Bach: Rapid Software Testing (Course notes), I grant permission to make digital or hard copies of this work for personal or classroom use, provided that (a) Copies are not made or distributed for profit or commercial advantage, (b) Copies bear this notice and full citation on the front page, and if you distribute the work in portions, the notice and citation must appear on the first page of each portion. Abstracting with credit is permitted. The proper citation for this work is "Rapid Software Testing (Course notes), (c) Each page that you use from this work must bear the notice "Copyright (c) James Bach, or if you modify the page, "Modified slide, originally from James Bach", and (d) If a substantial portion of a course that you teach is derived from these notes, advertisements of that course should include the statement, "Partially based on materials provided by James Bach." To copy otherwise, to republish or post on servers, or to distribute to lists requires prior specific permission and a fee. Request permission to republish from James Bach,

ET Workshop v Opening©2002 Amland Consulting0-4 License agreement Cem Kaner: Black Box Software Testing (Course notes, Commercial version, Spring 2002) I grant permission to make digital or hard copies of this work for personal or classroom use, provided that (a) Copies are not made or distributed for profit or commercial advantage, (b) Copies bear this notice and full citation on the front page, and if you distribute the work in portions, the notice and citation must appear on the first page of each portion. Abstracting with credit is permitted. The proper citation for this work is "Black Box Software Testing (Course notes, Commercial version, Spring 2002) (c) Each page that you use from this work must bear the notice "Copyright (c) Cem Kaner, or if you modify the page, "Modified slide, originally from Cem Kaner", and (d) If a substantial portion of a course that you teach is derived from these notes, advertisements of that course should include the statement, "Partially based on materials provided by Cem Kaner." To copy otherwise, to republish or post on servers, or to distribute to lists requires prior specific permission and a fee. Request permission to republish from Cem Kaner,

ET Workshop v Opening©2002 Amland Consulting0-5 Software Testing: “There is artistry. There is craft. There is science. It is all three – as with all technologies. If you understand the science and have mastered the craft, then it is meaningful to investigate, espouse, and perfect the art.” Boris Beizer.

ET Workshop v Opening©2002 Amland Consulting0-6 Software Testing: “Testing is the process of executing a program with the intent of finding errors.” “Testing is an extremely creative and intellectually challenging task.” Glenford Myers in “The Art of Software Testing”

ET Workshop v Opening©2002 Amland Consulting0-7 Presentation Outline Introduction Test Management and Techniques ET Planning, Exec. and Documentation ET Styles ET Management Introduction: Exploratory Testing and Risk, Why and when to use Exploratory Testing. Test Management, Test Techniques and Test Process ET Planning, Documentation and Execution. How to do Exploratory Testing Exploratory Test Styles How to use Exploratory Testing, continued Exploratory Test Management How to Manage Exploratory Testing and Teams

ET Workshop v Opening©2002 Amland Consulting0-8 Slides Structure 1. Introduction 1.1 Testing – thinking like a tester Exercise: Triangle 1.2 Exploratory Testing 2.0 Test Management and Techniques 2.1 Testing Fundamentals 2.2 Test Execution and Techniques Exercise: Boundary and EC Exercise: Bug Advocacy 2.3 Heuristic Risk-Based Testing 2.4 Test Management and Techniques 3.0 Exploratory Test Planning, Execution and Documentation 3.1 Planning, Tasks and Documentation Exercise 1a, 1b and 1c - Charters 3.2 Exploratory Testing in Pairs 3.3 ET with eXtreme Programming Exercise 2 – testing StarOffice 4.0 Exploratory Testing Styles - Skills and Techniques Exercise 3 – testing MiniTest Exercise 4 – testing WEB 5.0 Exploratory Test Management 5.1 Exploratory Test Team Management 5.2 Risk-Based Test Management 5.3 Session Based Test Management Exercise

ET Workshop v Opening©2002 Amland Consulting0-9 Outline Schedule Start: Coffee breake: Lunch: Coffee break: End: 5 minutes break every 45 hour if time permits

ET Workshop v Opening©2002 Amland Consulting0-10 General Information Messages and information Smoking Toilets Safety and Security

ET Workshop v Opening©2002 Amland Consulting0-11 Introduction Test Management and Techniques ET Planning and Documentation ET Styles ET Management My Assumptions about You… You test software. You know how to test software. You are familiar with test processes and testing techniques. You test things under conditions of uncertainty and time pressure. You have control over how you think and what you think about. One of your goals is to find important bugs fast. You want to get very good at testing software. From Rapid Software Testing, copyright © James Bach

ET Workshop v Opening©2002 Amland Consulting0-12 Workshop Objectives This workshop is NOT about test techniques or how to test a product! This workshop is about Exploratory Testing only! After this class, you should know: 1. What is Exploratory Testing? 2. When to apply and when NOT to apply exploratory testing 3. What kind of skills do you need? And how to develop them? 4. How to pick correct testing technique and style to do effective exploratory testing 5. How to manage an exploratory test team