<?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>Fri, 21 Nov 2008 06:35:34 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Developer Tutorials Blog: Testing email routines in web applications]]></title>
      <guid>http://www.phpdeveloper.org/news/10625</guid>
      <link>http://www.phpdeveloper.org/news/10625</link>
      <description><![CDATA[<p>
On the Developer Tutorials blog, there's a <a href="http://www.developertutorials.com/blog/web/testing-email-routines-in-web-applications-348/">recent example</a> of how to validate a common task of many signup forms - if the email sent is actually received.
</p>
<blockquote>
For any web developer that's ever had to build a signup routine, email is the necessary evil that takes pride of place among hated activities. Sure, a simple call to the language's mail library will send a message through, but the moment the boss wants a HTML email, or users need attachments, everything starts to get tricky.
</blockquote>
<p>
They try to solve the <a href="http://www.php.net">mail</a> return issue (it tells if the message has gone to the queue, not been delivered) with a little testing and <a href="http://www.lastcraft.com/fakemail.php">Fakemail</a>. The software looks for emails based on the configuration given and pulls them out to a local directory. Your script can then look here and check the validity of the message before its sent. 
</p>
<p>
This even allows for integration with things like <a href="http://phing.info/">Phing</a>, <a href="http://simpletest.sourceforge.net/">SimpleTest</a> and <a href="http://selenium.openqa.org/">Selenium</a>.
</p>]]></description>
      <pubDate>Thu, 17 Jul 2008 08:49:16 -0500</pubDate>
    </item>
  </channel>
</rss>
