<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sat, 25 May 2013 05:05:23 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Tillate.com Blog: Unit test practice at tilllate.com]]></title>
      <guid>http://www.phpdeveloper.org/news/10164</guid>
      <link>http://www.phpdeveloper.org/news/10164</link>
      <description><![CDATA[<p>
<i>Silvan Muhlemann</i> has <a href="http://techblog.tilllate.com/2008/05/11/unit-test-practice-at-tilllatecom/">posted about</a> the unit testing that tillate.com does for their releases - the whole process from start to finish.
</p>
<blockquote>
For now over three years we are working with unit tests. I'd like to share some of those experiences. As we have two frameworks in place for our website, I can compare two different strategies for unit tests.
</blockquote>
<p>
He <a href="http://techblog.tilllate.com/2008/05/11/unit-test-practice-at-tilllatecom/">talks about</a> their choice of SimpleTest, their test monitoring, CruiseControl and their "if it doesn't pass, you can't release it" mentality to keep their site as bug free as possible.
</p>]]></description>
      <pubDate>Mon, 12 May 2008 15:46:25 -0500</pubDate>
    </item>
  </channel>
</rss>
