Downloaded 497 times
Uploaded bysriks7
PPTX, PDF11,118 views
Exploratory Testing
The document discusses the importance and techniques of exploratory testing in software development, highlighting the benefits of both manual and automated testing. It categorizes various exploratory testing methods, including freestyle, scenario-based, strategy-based, and feedback-based testing, emphasizing the need for testers to have clear goals and documented strategies. Additionally, it addresses the challenges and potential metrics for evaluating exploratory testing effectiveness.
Editor's Notes
- #6 Perhaps this is a case of feature conflict…it’s the ‘pub crawl across England starting in Newcastle” feature conflicting with the ‘don’t drive through Amsterdam when the wife is in the car” feature. Resulting in a 1600 mile unwanted detour.
- #7 Someone actually wrote this error message…
- #13 Bug bash, first round of bugs in any app, initial parts of development
- #14 Finds the most important set of bugs – those that users will hit in mainline scenarios. UAT is largely composed of such testing.
- #15 Some people are just better testers. Nose for defects. Tricks/tips that just assist them in finding a bug in the most tested s/w.
- #16 Different teams have different metrics that are important. Coverage could be one. Churn is a smart metric, but there are no tools yet that can distinguish how we can select tests that are impacted
- #30 Different teams have different metrics that are important. Coverage could be one. Churn is a smart metric, but there are no tools yet that can distinguish how we can select tests that are impacted