<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>BDD on Architecture and Data Blog</title>
    <link>https://sadalage.com/tags/bdd/</link>
    <description>Recent content in BDD on Architecture and Data Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 16 Aug 2015 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sadalage.com/tags/bdd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Behavior Driven Database Development</title>
      <link>https://sadalage.com/post/behavior-driven-database-development/</link>
      <pubDate>Sun, 16 Aug 2015 00:00:00 +0000</pubDate>
      <guid>https://sadalage.com/post/behavior-driven-database-development/</guid>
      <description>&lt;p&gt;When Behavior Driven Development &lt;a href=&#34;http://dannorth.net/introducing-bdd&#34;&gt;BDD&lt;/a&gt; was introduced, some of the key principles were&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Requirements are behavior,&lt;/li&gt;&#xA;&lt;li&gt;Provides &amp;ldquo;ubiquitous language&amp;rdquo; for analysis,&lt;/li&gt;&#xA;&lt;li&gt;Acceptance criteria should be executable.&lt;/li&gt;&#xA;&lt;li&gt;Design constraints should be made into executable tests.&lt;/li&gt;&#xA;&lt;/ul&gt;</description>
    </item>
    <item>
      <title>Article about Behavior Driven Database Design is out</title>
      <link>https://sadalage.com/post/article_about_behavior_driven/</link>
      <pubDate>Mon, 22 Dec 2008 00:00:00 +0000</pubDate>
      <guid>https://sadalage.com/post/article_about_behavior_driven/</guid>
      <description>&lt;p&gt;Recently I have been thinking a lot about making specification and behavior expected about the database and the code that interfaces with the databases &lt;strong&gt;executable&lt;/strong&gt;. The Behavior Driven Design has a lot of parallels in the database world.&lt;/p&gt;&#xA;&lt;p&gt;Just finished writing a article about Behavior Driven Design applied to Databases or &lt;a href=&#34;http://www.methodsandtools.com/archive/archive.php?id=78&#34;&gt;Behavior Driven Database Design for Methods and Tools&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Database Testing revisited</title>
      <link>https://sadalage.com/post/database_testing_revisited/</link>
      <pubDate>Thu, 09 Nov 2006 00:00:00 +0000</pubDate>
      <guid>https://sadalage.com/post/database_testing_revisited/</guid>
      <description>&lt;p&gt;Some time ago I wrote about what it means to do database testing.. more I think about this and having had some strange situations recently I want to add more to the list of things we should be testing.&lt;/p&gt;&#xA;&lt;p&gt;&lt;em&gt;Persistence Layer&lt;/em&gt; We should persist the objects to the database using the applications persistence layer and retrieve the objects using the same mechanism and test that we get the same object back. If we have a lot of business logic in out persistence layer we may also want to retrieve the object using Direct SQL and test that the correct values got persisted.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
