tag:blogger.com,1999:blog-8951904624959546499.post6156466254522912863..comments2024-02-22T05:36:59.121-05:00Comments on Test This Blog - Eric Jacobson's Software Testing Blog: How to Test While You DaydreamEric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-8951904624959546499.post-87578616445235853602011-04-29T03:42:06.059-04:002011-04-29T03:42:06.059-04:00Sounds similar to the "Rubber Ducking"-e...Sounds similar to the "Rubber Ducking"-exercise I´ve written about here: http://agile-and-testing.chriss-baumann.de/2010/10/rubber-ducking/Christian Baumannhttp://agile-and-testing.chriss-baumann.de/noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-36662964968767154562011-04-08T15:43:51.186-04:002011-04-08T15:43:51.186-04:00'grok the code', well put :)
I think I wil...'grok the code', well put :)<br />I think I will suggest the British accent idea to the developers I work with.Unknownhttps://www.blogger.com/profile/06927096774207705192noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-47404348404228401232011-04-08T14:57:40.012-04:002011-04-08T14:57:40.012-04:00That would be something. I'll try that next ti...That would be something. I'll try that next time. :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-38250521816515113412011-04-08T14:54:58.781-04:002011-04-08T14:54:58.781-04:00Yes, I agree, Anonymous programmer. I'll try ...Yes, I agree, Anonymous programmer. I'll try to do more visualization of the scenarios. <br /><br />Perhaps if you make the code review more interesting, I would not drift off. For example, you could give the methods their own voice (maybe that British accent you do) and the objects could have a different voice (falsetto or something). You could make it like a little story. <br /><br />That would be something.Eric Jacobsonhttps://www.blogger.com/profile/08216361684596485033noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-31913374049921743352011-04-08T14:52:11.427-04:002011-04-08T14:52:11.427-04:00PS: I am not your programmer. You are *my* tester....PS: I am not your programmer. You are *my* tester. Beeotch!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-23389170999348907562011-04-08T14:45:56.575-04:002011-04-08T14:45:56.575-04:00I am flattered to finally get mentioned in your bl...I am flattered to finally get mentioned in your blog! I think more value can be added to this process by the tester not day-dreaming. That sounds obvious, of course. But, what I mean is that as the dev is explaining his or her code line by line, the tester might be able to visualize the sequence of what the code is doing and create a sequence diagram or something in their head or on paper. That will help the tester check that the implementation of the logic accords with their understanding of how the logic should be implemented. Honestly, that is mainly what I intend to happen when we do this--along with the "magic" that you point out.Anonymousnoreply@blogger.com