Comments on: Rapid vs. Hyper-Rapid Testing http://www.satisfice.com/blog/archives/9 The Consulting Software Tester Sat, 22 Nov 2008 07:55:04 +0000 http://wordpress.org/?v=2.3.3 By: Aaron Hodder http://www.satisfice.com/blog/archives/9#comment-114854 Aaron Hodder Thu, 20 Mar 2008 02:04:57 +0000 http://www.satisfice.com/blog/archives/9#comment-114854 Four years is a long time to leave a comment after a post, but I have to say that this is the most concise guide to exploratory testing I have ever seen. If I ever get stuck or run out of inspiration for what to do next, I search for this article, and find it kick starts the creative juices again. Thanks James <em> [James' Reply: Thanks, but be careful. This is not a description of exploratory testing. This is a description of an approach to testing that may or may not be exploratory, but usually is <strong>very</strong> exploratory. I now call this kind of testing "quick-testing" as in "I'm going to do some quick-tests now." We can imagine highly scripted quick-tests, too. When people confuse quick-testing with exploratory testing, they miss out on all the slow, careful, and deep forms of exploratory testing.]</em> Four years is a long time to leave a comment after a post, but I have to say that this is the most concise guide to exploratory testing I have ever seen. If I ever get stuck or run out of inspiration for what to do next, I search for this article, and find it kick starts the creative juices again.

Thanks James

[James’ Reply: Thanks, but be careful. This is not a description of exploratory testing. This is a description of an approach to testing that may or may not be exploratory, but usually is very exploratory. I now call this kind of testing “quick-testing” as in “I’m going to do some quick-tests now.” We can imagine highly scripted quick-tests, too. When people confuse quick-testing with exploratory testing, they miss out on all the slow, careful, and deep forms of exploratory testing.]

]]> By: Joaquin Bolaños Vargas http://www.satisfice.com/blog/archives/9#comment-13 Joaquin Bolaños Vargas Tue, 17 Feb 2004 17:08:49 +0000 http://www.satisfice.com/blog/archives/9#comment-13 Right now, sometimes our applications have errors in production time that we couldn't get because of for example the programmer forgot to replicated the new code into another module. However the black box testing didn't catch that error. So i have the doubt about when it is strictly necessary to do White Box Testing... Right now, sometimes our applications have errors in production time that we couldn’t get because of for example the programmer forgot to replicated the new code into another module. However the black box testing didn’t catch that error. So i have the doubt about when it is strictly necessary to do White Box Testing…

]]> By: Surya http://www.satisfice.com/blog/archives/9#comment-12 Surya Wed, 04 Feb 2004 21:44:30 +0000 http://www.satisfice.com/blog/archives/9#comment-12 Hi, I'm a developer trying to decide whether to be a full-time tester or not. Like u i am getting tired of this long cycle of production coding. Ur website/articles gave me a lot of insight into the world of testing. Thanks. Now I'm going to apply the above steps to these fields to check if I can crash this page! hehe Thanks a lot, Surya Hi, I’m a developer trying to decide whether to be a full-time tester or not. Like u i am getting tired of this long cycle of production coding. Ur website/articles gave me a lot of insight into the world of testing. Thanks.
Now I’m going to apply the above steps to these fields to check if I can crash this page!
hehe Thanks a lot,
Surya

]]>