Monday February 18, 2019
Exploratory testing is a process where testers can be creative in exploring the software without knowing much about the working of the system. let’s dig deep
What is Exploratory Testing?
It is a testing approach where you explore the system and venture into those aspects and functionalities which may or may not directly affect the system’s outputs, in order to find underlying errors.
It is all about exploring the system, discovering hidden errors, investigating their cause, and rectifying them. There are no pre-defined test cases formed in exploratory testing and therefore the testers explore the system aimlessly in hopes to find unforeseen bugs.
The purpose of performing exploratory tests is to learn more about the system and its functionality and using your existing knowledge about the system to find errors.
Testers need to be very creative and innovative in order to perform exploratory testing as the aim is to test the system for unexpected errors using unexpected techniques.
Even though there are no pre-defined test cases, testers may note down or document their ideas and things they want to test before performing the test.
Description of exploratory testing techniques?
There are different ways the process can be done. Based on that it can be divided into 3 main types as below:
How is functional exploratory testing different from structured exploratory testing?
1. Flow of the test
In structured testing, the flow of the test is directed by test cases that are prepared ahead of time.
Test cases are not determined in advance in exploratory testing and the flow is directed from exploring the system.
2. The objective of testing
The main objective of structured testing is to find foreseen errors whereas in exploratory testing the aim is to learn about the system and gain knowledge about its functionality.
Structured testing is predictive in nature as the flow of the test is predicted in advance.
Exploratory testing is spontaneous and investigative in nature. Tests are performed on a proper investigation is conducted.
4. The end results
The end results of structured tests are known and anticipated. However, the end results in exploratory tests are unknown and unexpected.
Wish to know about the types of software testing? Read here
When to use exploratory testing?
The process is mostly standalone and can not be used to confirm the quality of any software product, it is always used to supplement the other testings. Some of the situations where exploratory testing will be very fruitful and helpful are:
Exploratory Testing Process
This is the first step of exploratory testing and one which is very crucial. Learning about the system is important because you will be able to better analyze all the minor and major functionalities of the system and check it for bugs.
Your knowledge about the system will help you explore the system and create test designs and plans accordingly.
Unless you do not have knowledge about the system you will not be able to explore it in detail.
2. Test Design
Tests designs are created spontaneously during exploratory testing and there is no need for documentation of test cases, scripts and the conditions of the test.
3. Test Execution
Test execution is performed along with test designing. As soon as you plan and design your test you execute it without waiting for formal documentation. Only the key components of the test are recorded like the bugs that are detected or ideas for the next test.
When some bugs are detected on exploring the system, proper analysis and feedback are made in order to rectify the errors.
The previous test result feedback helps testers to prepare for future tests and apply logical reasoning to guide the future of the software testing life cycle.
Advantages of Exploratory Testing
Disadvantages of Exploratory Testing
There are some disadvantages related to exploratory testing which make it a little harder to implement.
Challenges in exploratory testing
There are some challenges in exploratory testing because it is not structured. Let us check out some of the major challenges:
Steps in exploratory testing
Exploratory testing does not follow a particular structure; however, there are a few steps that are common to each exploratory test. The preparation of exploratory tests is a 5 step process:
1. Learning and classifying errors
The first stage of exploratory testing is gathering the results of the previous exploratory test in order to learn the errors found in the past projects. Testers need to analyze these errors and understand the root causes of the bugs so that they can develop a test plan or strategy to test their system.
2. Test Charter tool
Test charter is a tool that is used to run exploratory tests. The stakeholders define the scope of the test and risks that need to be found using the test charter. Thus the charter should tell testers the following things:
3. Time Box
Time Boxing is the practice of setting a fixed amount of time known as a timebox during which a tester or a team of testers work together to find bugs. The time box session should not be interrupted and the testers should only focus on testing the system.
The testers working in pairs or groups can come up with the most creative exploration techniques and device efficient solutions to the errors found.
4. Analyzing the results
Once the testing process is completed, the results of the test are reviewed. The defects found are evaluated and testers learn the causes of the defects in order to come up with the best solutions.
The results are compiled and compared with the charter. This helps testers identify whether they have tested the system according to the stakeholder’s needs and demands.
Things to keep in mind for exploratory testing
1. Understand the main aim of testing
Exploratory testing is all about learning about the system and understanding its core functionality by exploring unexpected system paths. During this process, certain unforeseen bugs are detected.
2. Planning the test is very important
Although test cases are not pre-defined during exploratory testing, it does not mean that exploratory tests are completely unplanned. Testers study the system and previous test results in order to figure out and plan their test. This helps them save a lot of time as they know what they are looking for.
3. This is skill-based testing
Testing skills are an essential part of exploratory testing. Testers completely rely on their skills in order to explore the system and test it for defects. Therefore exploratory testers should be highly skilled and have good knowledge of all software testing techniques.
4. Keeping a record of the test can be very beneficial
Even though exploratory tests are not documented, recording the findings, results, and defects found or any other outcomes of an exploratory test can be very beneficial.
5. Exploratory testing should be a team activity
It is always better to perform exploratory tests in pairs or in a team. This helps testers to come up with better test plans, exploration techniques, and solutions to the defects found.
Top 10 Ideas for exploratory testing
Example for Exploratory testing
The below image is an indication of how test cases are created for checking out the functionality of a web app.
Exploratory testing documentation
Eg: *NEW* /LIVE/ “Browser: Login with Gmailfirefox” (23-july-2021 09:44:20)
Client id = 357
Login page displayed => OK
Previous account name displayed => OK
Login => OK
Logout Button available => OK
You can use web-based tools such as XMind7 to document the process. The conventional mind mapping technique would not work in this case. Create all the test cases as nodes and can be saved into a template. Data such as environment, date, execution browser, time, the theme of the site, input data, environment, output data
Exploratory testing vs ad-hoc testing
Testing is carried out without much knowledge about the software but in a formal way
Complete freedom in testing the software
Documentation is mandatory
Not that important
Charter directed testing
No particular plan
Maximum test cases are executed
No need for test cases
Form of positive testing
Form of negative testing
Helps in learning the application
Helps in developing innovative ideas in testing
Does not need much time to commence
Needs preparation time
It overcomes all the shortcomings of structured testing. It helps testers detect errors that go unnoticed during scripted tests as they do not directly affect the outcome or working of the system.
This is the reason exploratory testing has become a very popular testing approach, especially for complicated systems. Exploratory testing has many advantages over scripted testing and helps testers focus on gaining knowledge about the system.