To simultaneously learn about, design, and execute tests.
- Méthodologies : Idéation, Résolution de problèmes
Exploratory Testing

Exploratory Testing
- Méthodologie Agile, Amélioration continue, Assurance qualité, Contrôle de qualité, Software Testing, Méthodes d'essai, Tests d'utilisabilité, Tests auprès des utilisateurs, Validation
Objectif :
Comment il est utilisé :
- 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.
Avantages
- Can find defects that scripted tests might miss; Encourages creativity and learning.
Inconvénients
- Highly dependent on the skill and experience of the tester; Not a systematic or repeatable method.
Catégories :
- Qualité, Gestion des risques
Idéal pour :
- 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.
Principales étapes de cette méthodologie
- 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.
Conseils de pro
- 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.
Lire et comparer plusieurs méthodologies, nous recommandons le
> Référentiel méthodologique étendu <
ainsi que plus de 400 autres méthodologies.
Vos commentaires sur cette méthodologie ou des informations supplémentaires sont les bienvenus sur le site web de la Commission européenne. section des commentaires ci-dessous ↓ , ainsi que toute idée ou lien en rapport avec l'ingénierie.
Articles Similaires
Calculateur de METS en calories
Méta-analyse
Cartographie des messages
Diagrammes du modèle mental
Forces de poussée et de traction maximales acceptables
Planification des besoins en matériaux (MRP)