Active TopicsActive Topics  Display List of Forum MembersMemberlist  CalendarCalendar  Search The ForumSearch  HelpHelp
  RegisterRegister  LoginLogin


 One Stop Testing ForumTypes Of Software Testing @ OneStopTestingManual Testing @ OneStopTesting

Message Icon Topic: Exploratory Testing Explained

Post Reply Post New Topic
Author Message
Sunil
Newbie
Newbie


Joined: 23Feb2007
Online Status: Offline
Posts: 1
Quote Sunil Replybullet Topic: Exploratory Testing Explained
    Posted: 23Feb2007 at 3:10pm
Exploratory software testing is a powerful approach, yet widely misunderstood. In some
situations, it can be orders of magnitude more productive than scripted testing. All testers
practice some form of exploratory testing, unless they simply don’t create tests at all. Yet few
of us study this approach, and it doesn't get much respect in our field. This attitude is
beginning to change as companies seek ever more agile and cost effective methods of
developing software.
Among the hardest things to explain is something that everyone already knows. We all know
how to listen, how to read, how to think, and how to tell anecdotes about the events in our
lives. As adults, we do these things everyday. Yet the level of any of these skills, possessed by

the average person, may not be adequate for certain special situations. Psychotherapists must
be expert listeners and lawyers expert readers; research scientists must scour their thinking for
errors and journalists report stories that transcend parlor anecdote.
So it is with exploratory testing (ET): simultaneous learning, test design and test execution.
This is a simple concept. But the fact that it can be described in a sentence can make it seem
like something not worth describing. Its highly situational structure can make it seem, to the
casual observer, that it has no structure at all. That’s why textbooks on software testing, with
few exceptions, either don’t discuss exploratory testing, or discuss it only to dismiss it as an
unworthy practice.
Exploratory testing is also known as ad hoc testing. Unfortunately, ad hoc is too often
synonymous with sloppy and careless work. So, in the early 1990s a group of test
methodologists (now calling themselves the Context-Driven School) began using the term
“exploratory”, instead. With this new terminology, first published by Cem Kaner in his book
Testing Computer Software, they sought to emphasize the dominant thought process involved
in unscripted testing, and to begin to develop the practice into a teachable discipline. Indeed,
exploratory testing can be as disciplined as any other intellectual activity. Microsoft practices
a formalized process of exploratory testing for the purposes of certifying third-party
applications for Windows compatibility (http://www.satisfice.com/tools/procedure.pdf) and
session-based test management (http://www.satisfice.com/sbtm) is a method specifically
designed to make exploratory testing auditable and measurable on a wider scale.

Our use of the term exploratory testing is not in any way euphemistic. We use the words in
their ordinary dictionary sense, just applied to testing. Our use of “Exploratory” particularly
echoes its usage in geography, as the explorers of the Royal Geographic Society, in the
eighteenth and nineteenth centuries, struggled with similar issues of methodology:



Post Resume: Click here to Upload your Resume & Apply for Jobs

IP IP Logged
Post Reply Post New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum



This page was generated in 3.094 seconds.
Vyom is an ISO 9001:2000 Certified Organization

© Vyom Technosoft Pvt. Ltd. All Rights Reserved.

Privacy Policy | Terms and Conditions
Job Interview Questions | Placement Papers | Free SMS | Freshers Jobs | MBA Forum | Learn SAP | Web Hosting