Browse Definitions :
Definition

exploratory testing

Contributor(s): Ivy Wigmore

Exploratory testing is an approach to software assessment that integrates learning about the program that's being developed with plans for future testing. Exploratory testing is sometimes referred to as ad hoc testing.

Once coding is complete, exploratory testing helps developers learn more about a program's functionality and discover whether requirements have been missed or misunderstood. Missed requirements may turn into new user stories, or they may be bugs that need to be fixed right away.

Testers manage the scope of exploratory testing by using a concept called charters. Charters are statements of what aspects of the system are to be tested. Unlike scripts, exploratory testing charters leave the actual steps of the testing up to the skilled and disciplined tester. For example, while a script might say "Type John Smith into the User field and 1234 into the Password field," a charter might simply say "test the login functionality."

Designing charters for exploratory testing is one of the most difficult aspects of exploratory testing. It is hard to know how much testing is enough, what aspects of the system need more coverage or how long a tester should spend examining any particular aspect of the system.

This was last updated in August 2018

Continue Reading About exploratory testing

Join the conversation

2 comments

Send me notifications when other members comment.

Please create a username to comment.

One aspect that should be mentioned is that commonly test engineers running Exploratory Testing (ET) should be highly skilled testers. ET should not be mixed with Ad'Hoc testing, but should be understood as structure approach and is not 'free for all'.

To employ ET successfully you also need TestObjectives clearly identified for each journey/timebox.

Searching for #TestObjectives gives multiple sites to bootstrap testing within ET context.
Cancel
how to test UI parts (like buttons are placed correctly and color is related requirement) in c# using xamarin technology
Cancel

SearchCompliance

  • risk assessment

    Risk assessment is the identification of hazards that could negatively impact an organization's ability to conduct business.

  • PCI DSS (Payment Card Industry Data Security Standard)

    The Payment Card Industry Data Security Standard (PCI DSS) is a widely accepted set of policies and procedures intended to ...

  • risk management

    Risk management is the process of identifying, assessing and controlling threats to an organization's capital and earnings.

SearchSecurity

SearchHealthIT

SearchDisasterRecovery

  • call tree

    A call tree is a layered hierarchical communication model that is used to notify specific individuals of an event and coordinate ...

  • Disaster Recovery as a Service (DRaaS)

    Disaster recovery as a service (DRaaS) is the replication and hosting of physical or virtual servers by a third party to provide ...

  • cloud disaster recovery (cloud DR)

    Cloud disaster recovery (cloud DR) is a combination of strategies and services intended to back up data, applications and other ...

SearchStorage

  • RAM (Random Access Memory)

    RAM (Random Access Memory) is the hardware in a computing device where the operating system (OS), application programs and data ...

  • business impact analysis (BIA)

    Business impact analysis (BIA) is a systematic process to determine and evaluate the potential effects of an interruption to ...

  • M.2 SSD

    An M.2 SSD is a solid-state drive that is used in internally mounted storage expansion cards of a small form factor.

Close