et workshop v. 1.20 - opening©2002 amland consulting0-1 exploratory testing v. 1.20 workshop in...

ET Workshop v. 1.20 - Opening

©2002 Amland Consulting 0-1

Exploratory Testing

v. 1.20

Workshop in Risk-Based Agile Testing

Parts of this class have been excerpted from: Rapid Software Testing, by James Bach, [email protected] Box Software Testing, by Cem Kaner, [email protected] to build and lead an effective test team, by Lloyd Roden,

[email protected]

Ståle Amland, Amland Consulting,Hulda Garborgsv. 2, 4020 STAVANGER, NORWAY

Phone:+47 905 28 930, Fax: +4751585524e-mail: [email protected] WEB: www.amland.no



Introductory NoteParts of this class have been excerpted from:

Rapid Software Testing, by James Bach, [email protected] Black Box Software Testing, by Cem Kaner, [email protected] to build and lead an effective test team, by Lloyd Roden, Grove Consultants, [email protected]

Who am I?Name: Ståle AmlandE-mail: [email protected]: www.amland.noPhone: +47 905 28 930

The reference text will be located about here .....



License agreement James Bach: Rapid Software Testing (Course notes),

www.testingeducation.org

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), www.testingeducation.org"", (c) Each page that you use from this work must bear the notice "Copyright (c) James Bach, [email protected]", 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, [email protected].



License agreement Cem Kaner: Black Box Software Testing (Course notes, Commercial version, Spring 2002)

www.testingeducation.org

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) www.testingeducation.org", (c) Each page that you use from this work must bear the notice "Copyright (c) Cem Kaner, [email protected]", 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, [email protected].



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.



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”



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 StylesHow to use Exploratory Testing, continued

Exploratory Test ManagementHow to Manage Exploratory Testing and Teams

1.

2.

3.

4.

5.



Slides Structure1. Introduction

1.1 Testing – thinking like a tester

Exercise: Triangle

1.2 Exploratory Testing

2.0 Test Management and Techniques

2.1 Testing Fundamentals2.2 Test Execution and Techniques

Exercise: Boundary and ECExercise: Bug Advocacy

2.3 Heuristic Risk-Based Testing2.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 Pairs3.3 ET with eXtreme Programming

Exercise 2 – testing StarOffice

4.0 Exploratory Testing Styles - Skills and TechniquesExercise 3 – testing MiniTestExercise 4 – testing WEB

5.0 Exploratory Test Management5.1 Exploratory Test Team Management5.2 Risk-Based Test Management5.3 Session Based Test Management

Exercise 5

1.

2.

3.

4.

5.



Outline ScheduleStart:Coffee breake:Lunch:Coffee break:End:

5 minutes break every 45 hour if time permits



General Information

Messages and informationSmokingToiletsSafety and Security



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 © 1996-2002 James Bach



Workshop ObjectivesThis 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 testing3. 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

et workshop v. 1.20 - opening©2002 amland consulting0-1 exploratory testing v. 1.20 workshop in...

Documents