To simultaneously learn about, design, and execute tests.
- Metodologías: Clientes y marketing, Diseño de producto
Exploratory Testing

Exploratory Testing
- Metodología ágil, Mejora continua, Seguro de calidad, Control de calidad, Pruebas de software, Métodos de ensayo, Pruebas de usabilidad, Pruebas de usuario, Validación
Objetivo:
Cómo se utiliza:
- An unscripted approach to software testing where the tester explores the application to find defects. It relies on the tester's creativity, intuition, and experience to guide the testing process.
Ventajas
- Can find defects that scripted tests might miss; Encourages creativity and learning.
Contras
- Highly dependent on the skill and experience of the tester; Not a systematic or repeatable method.
Categorías:
- Calidad, Gestión de riesgos
Ideal para:
- Testing a new feature or application with limited documentation or time for formal test case design.
Exploratory Testing is particularly useful in industries such as software development, where project timelines are tight and fluid iterations are commonplace, such as in Agile methodologies. This approach is often adopted during the early stages of product development, where new features are being introduced, and formal testing processes may not yet be implemented. It can be initiated by development teams or quality assurance engineers who possess an intuitive understanding of the application’s functionality. Participants are typically experienced testers who leverage their domain knowledge to identify potential user interactions that scripted tests may overlook. For instance, in a mobile application context, testers might explore various device settings, network conditions, or user behavior patterns that could lead to unexpected application crashes or UI issues. This unscripted approach enables a more adaptive response to the software’s evolving nature and can also aid in creating informal knowledge-sharing sessions within teams, resulting in a more robust testing culture. Examples of successful applications of this method include major tech companies like Microsoft and Google, where exploratory testing is part of their quality assurance strategy, allowing quick feedback loops, adaptability in applications undergoing frequent changes, and a culture that values innovation through investigative exploration.
Pasos clave de esta metodología
- Identify areas of the application to explore based on feature changes or user stories.
- Use a variety of testing techniques such as error guessing and exploratory design.
- Interact with the application in ways that mimic real user behavior.
- Document findings during exploration without relying on formal templates.
- Adjust exploration based on immediate feedback from interactions.
- Communicate findings and impressions informally with the team throughout the process.
- Conduct follow-up tests on previously discovered defects to confirm resolution.
Consejos profesionales
- Engage in heuristic evaluation during exploratory testing to systematically identify usability issues, enhancing the overall user experience.
- Document exploratory sessions through screen recordings or notes, enabling future testers to analyze approaches and improve methodologies consistently.
- Prioritize feature testing based on user impact and potential failure scenarios, ensuring that high-risk areas receive adequate attention during exploration.
Leer y comparar varias metodologías, recomendamos el
> Amplio repositorio de metodologías <
junto con otras más de 400 metodologías.
Sus comentarios sobre esta metodología o información adicional son bienvenidos en la dirección sección de comentarios ↓ , así como cualquier idea o enlace relacionado con la ingeniería.
Publicaciones relacionadas
Simulación de Monte Carlo
Pruebas basadas en modelos
Comprobación de modelos
Investigación con métodos mixtos
A prueba de errores (Poka-Yoke)
Pruebas del perfil de la misión