"The aim of the test plan (and any test artifacts generated) is not to specify a set of actions to be followed in a rote manner, but instead a rough guide that encourages creative exploration."--- How do you measure this Creative Exploration.
Hi Erik, We use a bunch of internal tools to track the ET we're doing. These include bug tracking, code coverage tools, test case management -- yes, we do store interesting cases we come upon in the course of ET. In Google Talk, we rely on a broad set of quality metrics rather than just a couple to indicate release-readiness. Joel
Hi Joel, At my work use Session-Based Exploratory Testing. But we follow the Bach´s definition of session(www.satisfice.com). Why use a day session? You made a report for each session?
For our team, it worked better to have a broader definition of a session, and to have a daily milestone. The beauty of this form of testing is the ability to define the work into whatever chunks make sense for your implementation. We don't formally report each session, but we collate all of the daily reports into the work packet for the day. It would be interesting to hear how your company does using the pure method of Session-based ET. Joel
Hey Sachin, We actually make a point of not explicitly measuring the creative exploration, but rather use tools like metrics reporting, coverage analysis and auditing to ensure the right level of testing in the right areas is done. I find the testers find better bugs this way, and the developers are encouraged to do better unit testing as a result. Joel
Exploratory testing is one of the best techniques to find bugs in any given product.I do lot of exploratory testing and found around 100 crashes(high severity artifacts) and around 300 bugs from last 3 years.
In exploratory testing we can design many real time use cases.It can be used on any product which has immediate impact on customers.
Are you using a tool to track all this ET?
ReplyDelete"The aim of the test plan (and any test artifacts generated) is not to specify a set of actions to be followed in a rote manner, but instead a rough guide that encourages creative exploration."--- How do you measure this Creative Exploration.
ReplyDeleteSachin
Hi Erik,
ReplyDeleteWe use a bunch of internal tools to track the ET we're doing. These include bug tracking, code coverage tools, test case management -- yes, we do store interesting cases we come upon in the course of ET. In Google Talk, we rely on a broad set of quality metrics rather than just a couple to indicate release-readiness.
Joel
Hi Joel,
ReplyDeleteAt my work use Session-Based Exploratory Testing. But we follow the Bach´s definition of session(www.satisfice.com). Why use a day session? You made a report for each session?
Hi nacho,
ReplyDeleteFor our team, it worked better to have a broader definition of a session, and to have a daily milestone. The beauty of this form of testing is the ability to define the work into whatever chunks make sense for your implementation. We don't formally report each session, but we collate all of the daily reports into the work packet for the day. It would be interesting to hear how your company does using the pure method of Session-based ET.
Joel
Hey Sachin,
ReplyDeleteWe actually make a point of not explicitly measuring the creative exploration, but rather use tools like metrics reporting, coverage analysis and auditing to ensure the right level of testing in the right areas is done. I find the testers find better bugs this way, and the developers are encouraged to do better unit testing as a result.
Joel
Hi:
ReplyDeleteExploratory testing is one of the best techniques to find bugs in any given product.I do lot of exploratory testing and found around 100 crashes(high severity artifacts) and around 300 bugs from last 3 years.
In exploratory testing we can design many real time use cases.It can be used on any product which has immediate impact on customers.
Thanks and Regards,
sarath
How do you do regression test of captured ET test cases? Automatic (Selenium) or manual?
ReplyDelete