tag:blogger.com,1999:blog-5077189869336195827.post4262476894810804848..comments2023-09-25T04:46:47.467-04:00Comments on The expected result was 42. Now what was the test?: Measuring Exploratory TestingJohn Stevensonhttp://www.blogger.com/profile/05696297547425084869noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5077189869336195827.post-21932735829031087352014-01-30T09:01:35.465-05:002014-01-30T09:01:35.465-05:00Thank yo for your comment Michael.
I think your a...Thank yo for your comment Michael.<br /><br />I think your articles could have influenced me unconsciously whilst we were coming up with this concept. Thank you for adding the links so others can research further. <br /><br />PS - Regarding your approaches comment - we are using some tools, that should be able to show this very clearly.John Stevensonhttps://www.blogger.com/profile/05696297547425084869noreply@blogger.comtag:blogger.com,1999:blog-5077189869336195827.post-66806172544425652712014-01-30T01:38:01.259-05:002014-01-30T01:38:01.259-05:00Nice, John. I see links to
http://www.developse...Nice, John. I see links to <br /><br />http://www.developsense.com/blog/2009/11/why-is-testing-taking-so-long-part-1/ and http://www.developsense.com/blog/2009/11/what-does-testing-take-so-long-part-2/<br /><br />http://www.developsense.com/blog/2012/10/time-coverage-and-maps/<br /><br />http://www.developsense.com/blog/2012/10/where-does-all-that-time-go/<br /><br />Of course, you could measure testing done using other approaches as part of all this... and determine which approaches were finding bugs or revealing useful information.Michael Bolton http://www.developsense.comhttps://www.blogger.com/profile/09027725699187903416noreply@blogger.com