tag:blogger.com,1999:blog-414482498098790205.post655499107883571456..comments2012-02-08T06:49:09.083-07:00Ben Simohttp://www.blogger.com/profile/11448600123169359955noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-414482498098790205.post-62563242292280537042007-07-25T13:21:00.000-06:002007-07-25T13:21:00.000-06:00@Pradeep: You were missed. I heard your name a few times during the conference. Keep smacking that pinata. :)<BR/><BR/>@Rahul: I'm not a great note taker. I used to think that I had to record every bit of information to have good notes. I have since learned that jotting down a few highlights that I find interesting helps me recall the rest of the presentation.<BR/><BR/>Now that I think about it, I recall that Harry Robinson referred to Jerry Weinberg's second law in the tester expo. I don't remember him mentioning it in his keynote. So here's something from Harry's keynote:<BR/><BR/>Harry did a great job of demonstrating the difficulty of creating and managing test cases -- especially for automation -- prior to test execution. Harry showed that after creating just a few test cases for testing the <A HREF="http://www.google.com/talk/" REL="nofollow">Google Talk</A> functionality for creating and ending chat rooms it was easy to lose track of what was and was not covered by the test cases and that the test cases designed so far covered very little. Harry then showed how model-based automation could be used to generate and execute test cases based on a few simple rules. <BR/><BR/>Harry also showed a great use for bitmap comparisons in GUI test automation. I've never been a fan of bitmap comparison features in tools because I have found them to be more trouble than they are worth. Now I know of a good use for fuzzed bitmap comparisons. (And it is not comparing bitmaps to an expected result that is defined before test execution.)<BR/><BR/>Harry's demonstration reinforced my reasoning for describing behavior for automation instead of scripting test steps. He also gave me some new ideas for describing and selling model-based automation to those that are accustomed to scripted tests.Ben Simohttp://www.blogger.com/profile/11448600123169359955noreply@blogger.comtag:blogger.com,1999:blog-414482498098790205.post-11551257718875236902007-07-25T06:52:00.000-06:002007-07-25T06:52:00.000-06:00This comment has been removed by a blog administrator.Robertahttp://www.blogger.com/profile/08143273087113855796noreply@blogger.comtag:blogger.com,1999:blog-414482498098790205.post-1751422577368453182007-07-22T23:42:00.000-06:002007-07-22T23:42:00.000-06:00Hi Ben,<BR/><BR/>I used to wonder what some guys keep noting down, during the course of such conferences. I don't have this habit so far, but after reading this post, I strongly feel that I should start culturing the habit of making notes.<BR/><BR/>I am sure that these were one of the best points of presentations at CAST. Thanks for sharing the same.<BR/><BR/>Regards,<BR/><A HREF="http://testingperspective.blogspot.com/" REL="nofollow">Rahul Verma</A>Rahul Vermahttp://www.blogger.com/profile/15369178470521588425noreply@blogger.comtag:blogger.com,1999:blog-414482498098790205.post-20183771355684559152007-07-19T13:43:00.000-06:002007-07-19T13:43:00.000-06:00<I>What did you take away from CAST?</I><BR/><BR/>Before reading this post:<BR/>"I didn't take anything from CAST because I couldn't attend it."<BR/><BR/>After reading this post:<BR/>"There is valuable information and ideas I took from CAST although I couldn't make it there"<BR/><BR/>Pinata Heuristic usage: I keep pushing hard enough each year to make it to CAST. Hopefully the candy comes out next year.<BR/><BR/>Thank you!Pradeep Soundararajanhttp://www.blogger.com/profile/17849721523107325938noreply@blogger.com