Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
12 views2 pages

Exploratory Testing

Exploratory testing involves understanding an application, identifying and documenting scenarios, and testing based on that understanding, particularly when requirements are missing or unclear. It is often used in long-term projects, product-based companies, and startups where proper documentation may not be available. However, it can be time-consuming and may lead to missed defects or misunderstandings, which can be mitigated by interacting with experienced team members and leveraging product and domain knowledge.

Uploaded by

Chandana Sonu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
12 views2 pages

Exploratory Testing

Exploratory testing involves understanding an application, identifying and documenting scenarios, and testing based on that understanding, particularly when requirements are missing or unclear. It is often used in long-term projects, product-based companies, and startups where proper documentation may not be available. However, it can be time-consuming and may lead to missed defects or misunderstandings, which can be mitigated by interacting with experienced team members and leveraging product and domain knowledge.

Uploaded by

Chandana Sonu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Exploratory Testing

Understand the application, identify the scenarios, document the scenarios and
test the application by referring the document is called as Exploratory testing.
Or
Explore the application, understand how each and every feature works and test
the application based on your understanding is called as Exploratory testing.

When we go for exploratory testing?


When the requirement is missing we go for exploratory testing.
-In long term projects, when it’s a very big/huge/complex application, the
requirement for some modules might be missing.
-In product-based companies, since we don’t have customer, we won’t have
proper requirement document.
-In start-ups, if the company is very new, they might not maintain requirement
document properly.
-Sometimes even if the requirement (SRS) is present, we don’t have sufficient
time to read and understand the requirement.

How to do Exploratory testing?


1. Understand the application
a) Understand how each and every component works.
b) Understand how each and every module/feature works.
2. Identify the scenarios
3. Document the scenarios
4. Execute the scenarios referring the document.
5. When you find defects communicate of the developers.
Drawbacks of Exploratory testing:
1) Time Consuming
2) We might miss testing some features in turn we might miss the defects.
3) We might misunderstand defect as feature.
4) We might misunderstand feature as defect.
How to overcome the drawbacks of exploratory testing?
1. Interact with Sr. Dev, Sr. T.E, B.A or Customer.
2. Based on Product knowledge
3. Based on domain knowledge
4. By comparing the similar application.
5. Based on common sense.

You might also like