Exploratory Testing: Difference between revisions
(Created page with "=== '''Exploratory Testing for Web Sites – Basic Guide''' === '''What is Exploratory Testing?''' Exploratory testing is a hands-on testing approach where testers actively explore the website without using predefined test cases. The goal is to find unexpected issues by thinking like a user. Testers design and run tests at the same time, based on what they learn during testing. '''How to Prepare?''' Before testing, understand the product’s purpose, main user flows,...") |
No edit summary |
||
Line 1: | Line 1: | ||
<< Return to [[Testing Techniques]] | |||
=== '''Exploratory Testing for Web Sites – Basic Guide''' === | === '''Exploratory Testing for Web Sites – Basic Guide''' === | ||
'''What is Exploratory Testing?''' | '''What is Exploratory Testing?''' |
Latest revision as of 08:49, 5 June 2025
<< Return to Testing Techniques
Exploratory Testing for Web Sites – Basic Guide
What is Exploratory Testing?
Exploratory testing is a hands-on testing approach where testers actively explore the website without using predefined test cases. The goal is to find unexpected issues by thinking like a user. Testers design and run tests at the same time, based on what they learn during testing.
How to Prepare?
Before testing, understand the product’s purpose, main user flows, and recent changes. Review available documentation, wireframes, or product descriptions if any. Set a clear test charter — a short goal for your session (e.g. “Explore user registration process with invalid inputs”).
How to Run the Session?
Start using the site like a real user. Focus on functionality, usability, and responsiveness. Take notes while testing — what you did, what happened, and what seems wrong. If you find a bug, try to reproduce it and collect basic details (steps, expected vs actual result, screenshot/video if needed). Time-box your session (usually 30–90 minutes).
What to Look For?
- Broken links or missing elements
- Unexpected behavior in forms, buttons, navigation
- Layout problems on different screen sizes
- Unclear error messages or missing validations
Examples:
- You test the “Contact Us” form using special characters and receive a server error — this is a functional and security issue.
- You try to register with an email that is already used and the system accepts it without any warning — this is a validation issue.