|
|
|
|
"Exploratory testing is an interactive process of concurrent product exploration, test design and test execution." "Exploratory testing involves simultaneously learning, planning, runningtests, and reporting / troubleshooting results."
Have you ever been on a project that did not have enough resources for testing? Have you ever been in a project without requirements or specifications? So have we! Exploratory testing is a technique for "doing something quickly!". Exploratory testing can go in parallel with structured, scripted testing. As you as a tester learn about the application and the application domain during the project, new "exploratory tests" should continuously be added to your existing documented (scripted) tests. However, when there is no time and no resources for testing, Exploratory testing techniques might be an option to do some testing before the application is released to the users. No matter how you want to use exploratory testing, there are some basic skills you as a tester should have to become a good exploratory tester. Those skills will make you even more valuable to your project and to your company. Other reference material: Danish Paper about Exploratory Testing - click here! Case Study Exploratory Testing - click here! This presentation is documented in the book "Software Quality and Software Testing in Internet Times", by Dirk Meyerhoff et.al. (editors), Springer-Verlag 2002, ISBN: 3-540-42632-9. For further questions regarding this paper or presentation, please e-mail jarle.vaga@chello.no. For more information and inquiries about Amland Consulting's testing services, please click here.
|
|
Send mail to webmaster@amland.no with
questions or comments about this web site.
|
Have
you ever been on a project that did not have enough time for test planning,
scripting and execution?