<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:10pt;font-family:Bitstream Vera Sans">
<p>Hello,</p>
<p></p>
<p>For those of you interested, you can find my presentation at:</p>
<ul type="disc"><li>http://www.instantiated.ca/tdd-kiss.swf</li></ul>
<p>The git repository with the Address example can be found at:</p>
<ul type="disc"><li>http://www.instantiated.ca/tdd-git.tgz</li></ul>
<p></p>
<p>As I indicated in my talk, feed back would be appreciated.</p>
<p></p>
<p>Thanks,</p>
<p>Henry</p>
<p></p>
<p>On Wednesday, April 25 2007 11:24 am, Michael Graham wrote:</p>
<p>> The next TPM meeting will be tomorrow (Thursday Apr 26 2007) in the</p>
<p>> usual location (2 bloor St. west).</p>
<p>></p>
<p>> There's also a special all-day Hackathon happening this Sunday (Apr 28</p>
<p>> 2007) downtown (Richmond and Peter streets). Details for the Hackathon</p>
<p>> are here:</p>
<p>></p>
<p>> http://rakudo.org/hackathon-toronto/</p>
<p>></p>
<p>> If you're thinking of attending the Hackathon, please sign up on the</p>
<p>> wiki, so we have an idea of what sort of numbers to expect.</p>
<p>></p>
<p>></p>
<p>> Thursday Meeting Details:</p>
<p>></p>
<p>> (These details are also on the TPM web site: http://to.pm.org/)</p>
<p>></p>
<p>> This month we have two speakers on testing-related subjects!</p>
<p>></p>
<p>> Date: Thursday 27 Apr 2007</p>
<p>></p>
<p>> Time: 6:45pm</p>
<p>></p>
<p>> Where: 2 Bloor Street West (NW corner of Yonge/Bloor, skyscraper</p>
<p><span style="color:#008000">> with the CIBC logo on top) Classroom 11, 8th floor</span></p>
<p><span style="color:#008000">></span></p>
<p><span style="color:#008000">> ===================================================================</span></p>
<p><span style="color:#008000">></span></p>
<p><span style="color:#008000">> Talk Details:</span></p>
<p><span style="color:#008000">></span></p>
<p><span style="color:#008000">> Speaker #1: Jim Keenan</span></p>
<p><span style="color:#008000">> Title: Component-Focused Testing: The Case of the Parrot Build</span></p>
<p><span style="color:#008000">> Tools</span></p>
<p><span style="color:#008000">></span></p>
<p><span style="color:#008000">> Duration: 40 minutes</span></p>
<p><span style="color:#008000">></span></p>
<p><span style="color:#008000">> Description:</span></p>
<p><span style="color:#008000">></span></p>
<p><span style="color:#008000">> Installation of an open-source software package such as Perl or a</span></p>
<p><span style="color:#008000">> CPAN module generally follows a 4-step process: configure, build,</span></p>
<p><span style="color:#008000">> test, install. Although 'make test' is usually thought of as the</span></p>
<p><span style="color:#008000">> place where all the testing happens, the successful completion of</span></p>
<p><span style="color:#008000">> each of the other stages implicitly constitutes the passing of a</span></p>
<p>> functional test. But does there exist a place for a type of test</p>
<p>> which is not included in the 'test' target but instead is run either</p>
<p>> before the 'configure' stage or between the 'configure' and 'build'</p>
<p>> stages?</p>
<p>></p>
<p>> In this talk, Jim argues that there is a role for such tests and he</p>
<p>> describes how he has implemented a number of test suites, run post-</p>
<p>> configure but pre-build, for those of Parrot's build tools written</p>
<p>> in Perl 5. Such tests encourage provide more rapid feedback on the</p>
<p>> results of refactoring than 'make test' can. Indeed, they encourage</p>
<p>> Phalanx-style refactoring which makes the build tools more</p>
<p>> maintainable over the long run.</p>
<p>></p>
<p>> -------------------------------------------------------------------</p>
<p>></p>
<p>> Speaker #2: Henry Baragar</p>
<p>> Title: Test Driven Design: Or How I Learned to Love the KISS</p>
<p>> Principle</p>
<p>></p>
<p>> Duration: 40 minutes</p>
<p>></p>
<p>> Description:</p>
<p>></p>
<p>> Test Driven Development is a practice that can be used to improve</p>
<p>> software quality by writing tests before writing code. Applied</p>
<p>> properly, this practice can be extended to the design activities as</p>
<p>> well as code construction. In other words, it is practical to</p>
<p>> organically grow an application from an acorn to a mighty oak</p>
<p>> without doing any up front design work.</p>
<p>></p>
<p>> To demonstrate Test Driven Design, Henry will walk through the</p>
<p>> evolution of a real world example. He will discuss the techniques,</p>
<p>> examine some interesting and unexpected observations, and present</p>
<p>> statistics from personal use. Finally, the example will be</p>
<p>> developed using Jifty so that you may gain some exposure and insight</p>
<p>> into this interesting and cutting edge application framework.</p>
<p>></p>
<p>> ===================================================================</p>
<p>></p>
<p>> Note:</p>
<p>></p>
<p>> The elevators in the building are "locked down" after 5:30pm</p>
<p>> to people without building access cards. Leading up to the</p>
<p>> meeting someone will come down to the main floor lobby every</p>
<p>> few minutes to ferry people upstairs.</p>
<p>></p>
<p>> After 19:00, you can reach the access-card-carrying guy via</p>
<p>> a cell phone number that we'll leave with security in the</p>
<p>> front lobby. The room and floor numbers will be left with</p>
<p>> security too.</p>
<p></p>
</body></html>