Export to

• Google Calendar
• iCalendar file
• hCalendar markup
  <div class="vevent h-event"> <h1 class="summary p-name">XPDX October: Unit Test Your Database</h1> <div class='date'><time class="dtstart dt-start" title="2009-10-21T18:30:00" datetime="2009-10-21T18:30:00">Wednesday, October 21, 2009 from 6:30</time>–<time class="dtend dt-end" title="2009-10-21T22:30:00" datetime="2009-10-21T22:30:00">10:30pm</time></div> <div class="location vcard p-location h-card"> <a class="url" href='http://calagator.org/venues/202390009'><span class='fn org p-name'>PSU Business Accelerator</span></a> <div class="adr p-adr h-adr"> <div class="street-address p-street-address">2828 SW Corbett Ave</div> <span class="locality p-locality">Portland</span> , <span class="region p-region">OR</span> <span class="postal-code p-postal-code">97201</span> <div class="country-name p-country-name">US</div> (<a href='https://maps.google.com/maps?q=2828%20SW%20Corbett%20Ave,%20Portland%20OR%2097201%20US'>map</a>) </div> </div> <div class="description p-description"> <p>David Wheeler will be giving his "Unit Test Your Database" talk. It was well-received at Open Source Bridge; now he's giving it to an audience of Agile practitioners.</p> <p>We’re all used to unit testing our applications by now. The Extreme and Agile programming movements have done a great deal to promote unit testing, to the extent that many of us are now dependent on tests to assure that our applications work reliably. But how often do we test the database underlying our applications? Given that the database, as the repository for all of the knowledge and data for an application, just might be the single most important part of that application, the time for standardized database unit testing has come.</p> <p>This talk promotes the practice of writing and running unit tests that directly test the schema, storage, and functionality of application databases. Following a review of the available PostgreSQL unit testing frameworks, we’ll review examples of testing tables, views, columns, constraints, indexes, triggers, and functions. The idea is to promote complete test coverage every aspect of a database, independent of application unit tests, to ensure reliably canonical data integrity.</p> <p>Pizza and networking at 6:30pm, 7pm talk, beer afterwards.</p> </div> <h3>Links</h3> <ul> <li><a class="url u-url" href="http://tech.groups.yahoo.com/group/xpportland/">Website</a></li> </ul> </div>