Exploratory Testing Explained

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5
Please Log in or register to rate

Exploratory Testing Explained


In exploratory testing, testers may interact with the application in whatever way they want and use the information the application provides to react, change course, and generally explore the application’s functionality without restraint. It may seem ad hoc to some, but in the hands of a skilled and experienced exploratory tester, this technique can prove powerful. Advocates argue that exploratory testing allows the full power of the human brain to be  brought to bear on finding bugs and verifying functionality without preconceived restrictions.

This workshop has been designed to assist testers understand better what is exploratory testing, how to plan it, run it, measure it, and improve in doing


Target Audience:
Testers, testing team leaders and test managers.

Good grasp of software testing terminology, methods, techniques and processes.

Course Topics

Module 1 – Introduction

  • Overview of different exploratory testing approaches
  • Tester’s skills and attitudes – how do testers think?

Module 2 – What is exploratory testing?

  • Concurrent test design and execution
  • Exploratory testing defined
  • How is exploratory testing different from scripted testing?
  • Why do exploratory testing?
  • Goals of exploratory testing

Module 3 – Using Exploratory Testing

  • Where to use it (type of project)
  • When to use it (test phase)
  • Exploration for new features, test cases for regression
  • Plan test cases in advance, and explore to break the code

Module 4 – Risk and Risk-Based Testing

  • The Role of Heuristics
  • How to use risks in your software to find bugs?

Module 5 – Skills and Techniques

  • Exploratory testing styles
  • What do exploratory testers know?
  • How else do exploratory testers differ?
  • Questioning strategies

Module 6 – How to run exploratory testing?

  • How much planning is  done with exploratory testing?
  • Sources for identifying sessions (Charters)
  • How to write a good charter?
  • Coverage and traceability in exploratory testing
  • Which documentation is  produced under ET?
  • Targeting and Blending
  • How can you create plans that focus your exploration while remaining flexible?

Module 7 – Exploratory Testing in Pairs

  • What is paired testing?
  • A paired testing session
  • Benefits of paired testing
  • Risks and suggestions

Module 8 – Lab

  • Running and analyzing exploratory testing using Microsoft Test Management (MTM)
© Copyright - Skilit - Site by Dweb