Exploratory Testing Documentation & Reporting - Codoid
Select Page
Codoid Blog

Exploratory Testing Documentation & Reporting

Demonstrating Exploratory Testing using its document is a great value add for your team and project.

Exploratory Testing Documentation & Reporting

Reporting and documenting your exploratory testing can be a huge value add for your project. In scripted testing, you’re able to demonstrate with test results based on overall status and step-wise status. When talking about Exploratory testing however, there is a slightly different approach.

We’re all aware of the difference between Exploratory testing and scripted testing. Exploratory testing is more of a creative, free process in which you’re able to be flexible in your methodologies. This can actually work to the benefit of the product.

Let’s take a look at how to conduct Documentation and Reporting for Exploratory Testing.

Charters

Before Exploratory testing can begin, identifying the “What and Why” is crucial. What are you going to be testing, and why is it important? Exploratory testing allows for freedom while testing, but there should be a sharp focus on a particular area.

What we like to do at CODOID, is prepare a Charter before the Exploratory testing begins. This charter sets a focus and roadmap for your testing and ensures testers stay on track.

Notes

Keeping notes is vitally important to help members of your team understand how testing was conducted, and what you’re learned. Notes can then be used later for auditing.

Defect List

When discovering Defects, ensure they’re well documented on a dedicated list. To add some substance to the documentation, a full description of the Defect as well as screenshots or screencasts (i.e., steps to replicate Defect) ensure the proper context is provided. This allows your team to quickly and easily understand the issue.

Debriefing

A debriefing note is a fantastic way to explain to your team what you’ve done in that particular testing session. This allows your team to understand your approach, reflect, and receive inputs to improve the overall coverage and planning of the testing itself. Not all stakeholders in the project will have time to go through all of the artefacts. A debriefing note is a quick way to paint the overall picture for them.

Test Planning using MindMapping

It’s almost never a good idea to create a testing plan for Exploratory testing. However, planning shouldn’t be ignored entirely. You never know what will come out of Exploratory testing. Instead of creating a full test plan, begin planning when focusing on a particular feature or functionality. As a software testing company, CODOID creates test plans using MindMap tools. The diagram below demonstrates all of our focus areas when testing CODOID’s Contact Us page.

Exploratory Testing Documentation

In Conclusion

We believe documentation is crucial in Exploratory testing. Not only does it help the tester, it helps their team and other stakeholders by quickly providing important information about the areas tested and defects found while limited superfluous information.

Written By

Submit a Comment

Your email address will not be published. Required fields are marked *


Reporting and documenting your exploratory testing can be a huge value add for your project. In scripted testing, you’re able to demonstrate with test results based on overall status and step-wise status. When talking about Exploratory testing however, there is a slightly different approach.

We’re all aware of the difference between Exploratory testing and scripted testing. Exploratory testing is more of a creative, free process in which you’re able to be flexible in your methodologies. This can actually work to the benefit of the product.

Let’s take a look at how to conduct Documentation and Reporting for Exploratory Testing.

Charters

Before Exploratory testing can begin, identifying the “What and Why” is crucial. What are you going to be testing, and why is it important? Exploratory testing allows for freedom while testing, but there should be a sharp focus on a particular area.

What we like to do at CODOID, is prepare a Charter before the Exploratory testing begins. This charter sets a focus and roadmap for your testing and ensures testers stay on track.

Notes

Keeping notes is vitally important to help members of your team understand how testing was conducted, and what you’re learned. Notes can then be used later for auditing.

Defect List

When discovering Defects, ensure they’re well documented on a dedicated list. To add some substance to the documentation, a full description of the Defect as well as screenshots or screencasts (i.e., steps to replicate Defect) ensure the proper context is provided. This allows your team to quickly and easily understand the issue.

Debriefing

A debriefing note is a fantastic way to explain to your team what you’ve done in that particular testing session. This allows your team to understand your approach, reflect, and receive inputs to improve the overall coverage and planning of the testing itself. Not all stakeholders in the project will have time to go through all of the artefacts. A debriefing note is a quick way to paint the overall picture for them.

Test Planning using MindMapping

It’s almost never a good idea to create a testing plan for Exploratory testing. However, planning shouldn’t be ignored entirely. You never know what will come out of Exploratory testing. Instead of creating a full test plan, begin planning when focusing on a particular feature or functionality. As a software testing company, CODOID creates test plans using MindMap tools. The diagram below demonstrates all of our focus areas when testing CODOID’s Contact Us page.

Exploratory Testing Documentation

In Conclusion

We believe documentation is crucial in Exploratory testing. Not only does it help the tester, it helps their team and other stakeholders by quickly providing important information about the areas tested and defects found while limited superfluous information.