XPDX February: Acceptance Test Driven Development >> NOW AT 6:30 AND FEATURING PIZZA <<

Export to

• Google Calendar
• iCalendar file
• hCalendar markup
  &lt;div class=&quot;vevent&quot;&gt; &lt;h1 class=&quot;summary&quot;&gt;XPDX February: Acceptance Test Driven Development &amp;gt;&amp;gt; NOW AT 6:30 AND FEATURING PIZZA &amp;lt;&amp;lt;&lt;/h1&gt; &lt;div class='date'&gt;&lt;abbr class=&quot;dtstart&quot; title=&quot;2009-02-18T18:30:00&quot;&gt;Wednesday, February 18, 2009 from 6:30&lt;/abbr&gt;&amp;ndash;&lt;abbr class=&quot;dtend&quot; title=&quot;2009-02-18T20:00:00&quot;&gt;8pm&lt;/abbr&gt;&lt;/div&gt; &lt;div class=&quot;location vcard&quot;&gt; &lt;a class=&quot;url&quot; href='http://calagator.org/venues/202389907'&gt;&lt;span class='fn org'&gt;CubeSpace [ *sniff* out of business 12 June 2009]&lt;/span&gt;&lt;/a&gt; &lt;div class=&quot;adr&quot;&gt; &lt;div class=&quot;street-address&quot;&gt;622 SE Grand Ave.&lt;/div&gt; &lt;span class=&quot;locality&quot;&gt;Portland&lt;/span&gt; , &lt;span class=&quot;region&quot;&gt;Oregon&lt;/span&gt; &lt;span class=&quot;postal-code&quot;&gt;97214&lt;/span&gt; &lt;div class='country-name'&gt;USA&lt;/div&gt; (&lt;a href='http://maps.google.com/maps?q=622+SE+Grand+Ave.%2C+Portland+Oregon+97214+USA'&gt;map&lt;/a&gt;) &lt;/div&gt; &lt;/div&gt; &lt;div class=&quot;description&quot;&gt; &lt;p&gt;Elisabeth Hendrickson will be coming to facilitate our February meeting. Here's her description:&lt;/p&gt; &lt;p&gt;&gt;&gt;&gt; UPDATE: SolutionsIQ are sponsoring pizza for twenty - arriving at 6:30 &amp;lt;&amp;lt;&amp;lt;&lt;/p&gt; &lt;p&gt;&quot;It will essentially be a shorter preview of the Agile2009 demo I proposed at &lt;a href=&quot;http://agile2009.agilealliance.org/node/641&quot;&gt;http://agile2009.agilealliance.org/node/641&lt;/a&gt;&lt;/p&gt; &lt;p&gt;Here's the blurb:&lt;/p&gt; &lt;p&gt;Agile teams practicing Acceptance Test Driven Development (ATDD) define acceptance tests collaboratively while discussing each story. This practice helps uncover assumptions and confirm that everyone has a shared understanding of what “done” looks like. During implementation, the technical team automates the natural-language Acceptance Tests by writing code to wire them up to the emerging software. In this way, ATDD tests become executable requirements. This session is a demonstration of the full ATDD workflow from initial discussions through final demo, and everything in between.&quot;&lt;/p&gt; &lt;/div&gt; &lt;h3&gt;Links&lt;/h3&gt; &lt;ul&gt; &lt;li&gt;&lt;a href=&quot;http://xpdx.org&quot; class=&quot;url&quot;&gt;Website&lt;/a&gt;&lt;/li&gt; &lt;/ul&gt; &lt;/div&gt;