<?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 01:00:42 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Till Klampaeckel's Blog: Selenium vs. Saucelenium]]></title>
      <guid>http://www.phpdeveloper.org/news/15097</guid>
      <link>http://www.phpdeveloper.org/news/15097</link>
      <description><![CDATA[<p>
In <a href="http://till.klampaeckel.de/blog/archives/111-Selenium-Saucelenium-installation-and-dbus-xorg-woes.html">this new post</a> to his blog <i>Till Klampaeckel</i> talks about two tools for front-end interface testing - Selenium and <a href="http://github.com/saucelabs/saucelenium">Saucelenium</a> - and how he used the latter in his application testing.
</p>
<blockquote>
Selenium and Saucelenium have the same root - in fact Saucelenium is a Selenium fork. While the Selenium project seems to focus on 2.x currently, stable 1.x  development seems to really happen at Saucelabs. That is if you call a commit from January 22nd of this year active development.
</blockquote>
<p>
He talks about the installation process (guided by the README from <a href="http://github.com/till/saucelenium">his fork</a>) and the tool he had to install to get it to work for him - xserver-xorg. He includes a sample test to give you an idea of what can be done with the testing tool. It loads the page imitating Chrome and looks for certain text on two different pages as well as check one of the links.
</p>]]></description>
      <pubDate>Wed, 08 Sep 2010 13:48:03 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Lukas Smith's Blog: RC testing and the README.UPDATE]]></title>
      <guid>http://www.phpdeveloper.org/news/6112</guid>
      <link>http://www.phpdeveloper.org/news/6112</link>
      <description><![CDATA[<p>
According to <a href="http://pooteeweet.org/blog/472">this new post</a> on <i>Lukas Smith</i>'s blog today, the PHP project has started a new effort aimed at helping out developers upgrading their PHP installations - a new README file with details on each upgraded version and its install.
</p>
<blockquote>
In order to make the transistion for users upgrading to new minor (middle number increment) and major (leading number increment) version of PHP easier, the PHP project has recently begun adding a README with upgrade information with new releases. This guide steps through any issues that users are likely to be faced when upgrading their PHP installations.
</blockquote>
<p>
<i>Lukas</i> also <a href="http://pooteeweet.org/blog/472">reminds developers</a> that testing these releases is the only real way to find the bugs that are there and catch them before the final release for that version. Bug issues can be reported to <a href="http://bugs.php.net/">the tracker</a> and, if you'd like to see an example of this new README file for PHP 5.2, check out <a href="http://cvs.php.net/viewcvs.cgi/php-src/README.UPDATE_5_2?view=markup&pathrev=PHP_5_2">this example</a>.
</p>]]></description>
      <pubDate>Wed, 23 Aug 2006 06:38:56 -0500</pubDate>
    </item>
  </channel>
</rss>
