<?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>Sun, 19 May 2013 19:27:01 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[H&aring;vard Eide's Blog: ChaosMonkey]]></title>
      <guid>http://www.phpdeveloper.org/news/16873</guid>
      <link>http://www.phpdeveloper.org/news/16873</link>
      <description><![CDATA[<p>
<i>H&aring;vard Eide</i> has a new post sharing a tool he's created (based on some ideas presented in <a href="http://techblog.netflix.com/2010/12/5-lessons-weve-learned-using-aws.html">this netflix blog post</a>) for testing a web service. Specifically, his tool helps you test a web service developed with the <a href="http://www.slimframework.com/">Slim</a> framework.
</p>
<blockquote>
I just pushed a example on how to create a <a href="https://github.com/haavardeide/ChaosMonkey>ChaosMonkey</a> with the <a href="http://www.slimframework.com/">Slim framework</a> to github. The idea is that whenever you create a webservice with the Slim framework (which is really simple) you rarely test for failure, the ChaosMonkey class will help you to do just that. When initialized with the <a href="https://github.com/haavardeide/ChaosMonkey/blob/master/ChaosMonkey/Chaos/AbsoluteChaos.php">AbsoluteChaos</a> plugin it will randomly kill the webservice with exceptions, garbage to the output, or just run the service for you without failure at all.
</blockquote>
<p>
His plugin does a lot of things right now, but it's easy to extend with your own failure types - like his suggested "networkSleep" or something that could kill the connection to MySQL. He includes a <a href="http://eide.org/2011/09/18/chaosmonkey/">code snippet in the post</a> of how to hook Slim and ChaosMonkey together for some testing fun.
</p>]]></description>
      <pubDate>Mon, 19 Sep 2011 09:11:26 -0500</pubDate>
    </item>
  </channel>
</rss>
