Exploratory testing is, more than strictly speaking a \u201cpractice,\u201d a style or approach to testing software which is often contrasted to \u201cscripted testing,\u201d and characterized by the following aspects among others:<\/p>\n
Agile teams tend to shift and redraw the role boundaries between \u201cdeveloper\u201d and \u201ctester,\u201d mostly as a result of the heavy use by developers of automated\u00a0unit<\/a>\u00a0and\u00a0functional<\/a>\u00a0tests \u2013 in one sense an extreme form of scripted testing. These activities are not sufficient to ensure quality, and Agile teams can find valuable assets in team members who have well-developed testing skills (whether or not their job description includes the term \u201ctester\u201d). These skills will be deployed more effectively in the exploratory style on an Agile team, as this style is more consistent with an Agile approach than the \u201cscripted testing\u201d style.<\/p>\n The term \u201cexploratory testing\u201d has been popularized by a community of testers who claim affiliation with a \u201cschool of testing thought\u201d known as the \u201cContext-Driven\u201d school, which they distinguish from other schools favoring different approaches to testing: the Analytical, Factory, Quality Assurance, Context-Driven or Agile.<\/p>\n The Agile movement has indubitably contributed to renewed interest from the developer community in the activities of testing, which were previously not seen as requiring a high level of skill. However, and somewhat paradoxically, it has also led to lessened respect for the value of skilled testers, as a result of shifting some test-related responsibilities to the developer role. In spite of this mixed influence, exploratory testing is still slowly gaining acceptance as part of a broader \u201cAgile testing\u201d skill set.<\/p>\n","protected":false},"excerpt":{"rendered":" Exploratory testing is, more than strictly speaking a “practice,” a style or approach to testing software which is often contrasted to “scripted testing.”<\/p>\n","protected":false},"author":6000331,"featured_media":8067461,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","categories":[906],"tags":[],"class_list":["post-5003177","aa_glossary","type-aa_glossary","status-publish","has-post-thumbnail","hentry","category-technology"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003177","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary"}],"about":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/types\/aa_glossary"}],"author":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/users\/6000331"}],"replies":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/comments?post=5003177"}],"version-history":[{"count":0,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/aa_glossary\/5003177\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media\/8067461"}],"wp:attachment":[{"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/media?parent=5003177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/categories?post=5003177"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilealliance.org\/wp-json\/wp\/v2\/tags?post=5003177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Also Known As<\/h2>\n
Origins<\/h2>\n
\n