<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://mobiforge.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>mobiForge Articles Feed - Section: Testing</title>
 <link>http://mobiforge.com/%24arg/article-listing/Testing</link>
 <description></description>
 <language>en</language>
<item>
 <title>A Guide to Mobile Emulators</title>
 <link>http://mobiforge.com/testing/story/a-guide-mobile-emulators</link>
 <description>&lt;p&gt;In a &lt;a href=&quot;http://mobiforge.com/testing/story/testing-mobile-web-sites-using-firefox&quot;&gt;previous article&lt;/a&gt;, I put forward a three-point plan for testing mobile Web sites. One of the points involved the use of emulators for first-pass device testing. This article concentrates on configuring emulators for mobile site testing (it also highlights emulators that can be used to test mobile applications too). It outlines the different types of emulator available, the best ones to use, and the various ways in which they can be used.&lt;/p&gt;
&lt;p&gt;For the uninitiated, an emulator is a software program that aims to replicate the functions of a specific piece of hardware or software.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/a-guide-mobile-emulators&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/a-guide-mobile-emulators#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/browsers">Browsers</category>
 <category domain="http://mobiforge.com/emulators">Emulators</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2320</wfw:commentRss>
 <pubDate>Wed, 14 Oct 2009 16:15:31 +0000</pubDate>
 <dc:creator>mokil</dc:creator>
 <guid isPermaLink="false">2320 at http://mobiforge.com</guid>
</item>
<item>
 <title>Testing Mobile Web Sites Using Firefox</title>
 <link>http://mobiforge.com/testing/story/testing-mobile-web-sites-using-firefox</link>
 <description>&lt;p&gt;Before you ever begin testing your mobile site to determine how it looks on handsets, you should make sure the functionality of the site is working as you expect. This is not always straightforward, as you want to approximate the mobile environment as closely as possible. Fortunately, Mozilla Firefox supports some great extensions that can make testing your mobile sites a piece of cake. This article explains how to set Firefox up to act as a first pass test environment for your site.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/testing-mobile-web-sites-using-firefox&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/testing-mobile-web-sites-using-firefox#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/browsers">Browsers</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/publishing">Publishing</category>
 <category domain="http://mobiforge.com/tools">Tools</category>
 <category domain="http://mobiforge.com/quality-assurance">Quality Assurance</category>
 <category domain="http://mobiforge.com/http">HTTP</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2201</wfw:commentRss>
 <pubDate>Wed, 12 Aug 2009 11:34:27 +0000</pubDate>
 <dc:creator>mokil</dc:creator>
 <guid isPermaLink="false">2201 at http://mobiforge.com</guid>
</item>
<item>
 <title>Getting started with the ready.mobi API</title>
 <link>http://mobiforge.com/testing/story/getting-started-with-ready-mobi-api</link>
 <description>&lt;p&gt;&lt;a href=&quot;http://ready.mobi&quot;&gt;Ready.mobi&lt;/a&gt; is a well known page testing tool offered by dotMobi. When you supply a page URL to ready.mobi, it evaluates how well the page is likely to display on mobile devices by testing against the Mobile Web Best Practices, and dotMobi compliance rules. &lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/getting-started-with-ready-mobi-api&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/getting-started-with-ready-mobi-api#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/accessibility">Accessibility</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/dotmobi-compliance-0">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/tools">Tools</category>
 <category domain="http://mobiforge.com/http">HTTP</category>
 <enclosure url="http://mobiforge.com/sites/mobiforge.com/files/sample_java.zip" length="1483" type="" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1956</wfw:commentRss>
 <pubDate>Thu, 19 Mar 2009 12:50:56 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">1956 at http://mobiforge.com</guid>
</item>
<item>
 <title>Handy shortcuts to using Ready.mobi</title>
 <link>http://mobiforge.com/testing/story/handy-shortcuts-using-ready-mobi</link>
 <description>&lt;p&gt;I love Firefox. In fact I sometimes wonder how anyone ever did any web development or design without Firefox and its many great extensions. Well I&amp;#39;ve got 3 handy add-ons/tips for you that will make designing for mobile that much easier by enabling you to launch ready.mobi in seconds.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/handy-shortcuts-using-ready-mobi&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/handy-shortcuts-using-ready-mobi#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/tools">Tools</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1939</wfw:commentRss>
 <pubDate>Fri, 06 Mar 2009 13:37:19 +0000</pubDate>
 <dc:creator>adrian.hopebailie</dc:creator>
 <guid isPermaLink="false">1939 at http://mobiforge.com</guid>
</item>
<item>
 <title>Audio/Video Playback &amp; Streaming Support on Mobile Devices</title>
 <link>http://mobiforge.com/developing/story/audiovideo-playback-streaming-support-mobile-devices</link>
 <description>&lt;p&gt;Audio and video are very important tools in the arsenal available to web-developers, marketing/sales types and content providers (to name but a few). Few are likely to remember the internet before YouTube, before on-demand playback of your favourite tv shows or even before Google for that matter, which means that the ability to embed movies and rich content in a webpage is almost certainly taken for granted in today&#039;s always-on world.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/audiovideo-playback-streaming-support-mobile-devices&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/audiovideo-playback-streaming-support-mobile-devices#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/tada">TADA</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <category domain="http://mobiforge.com/multimedia">Multimedia</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1861</wfw:commentRss>
 <pubDate>Mon, 19 Jan 2009 12:28:53 +0000</pubDate>
 <dc:creator>daniel.hunt</dc:creator>
 <guid isPermaLink="false">1861 at http://mobiforge.com</guid>
</item>
<item>
 <title>TADA  Advanced Tests - A Tutorial</title>
 <link>http://mobiforge.com/testing/story/tada-advanced-tests-a-tutorial</link>
 <description>Following on from my &lt;a href=&quot;http://mobiforge.com/testing/story/deviceatlas-tada&quot;&gt;previous tutorial&lt;/a&gt; and the &lt;a href=&quot;http://mobiforge.com/testing/blog/tada-alive-and-kicking-and-da-20-preview&quot;&gt;public release&lt;/a&gt; of TA-DA, I&#039;d like to present a new tutorial based on 2 of our more complicated tests: &lt;strong&gt;Usable Display Height&lt;/strong&gt; and &lt;strong&gt;Usable Display Width&lt;/strong&gt;.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/tada-advanced-tests-a-tutorial&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/tada-advanced-tests-a-tutorial#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/tada">TADA</category>
 <category domain="http://mobiforge.com/tutorial">Tutorial</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1249</wfw:commentRss>
 <pubDate>Tue, 02 Sep 2008 09:28:35 +0000</pubDate>
 <dc:creator>daniel.hunt</dc:creator>
 <guid isPermaLink="false">1249 at http://mobiforge.com</guid>
</item>
<item>
 <title>DeviceAtlas - TADA!</title>
 <link>http://mobiforge.com/testing/story/deviceatlas-tada</link>
 <description>The Test Application (or “test suite&quot;, as it is also known) for DeviceAtlas is a system that has been developed which provides you, the user, with the opportunity to input device specific data &lt;em&gt;directly&lt;/em&gt; into our system.&lt;br /&gt;
&lt;br /&gt;
This simple process is demonstrated below in a step-by-step introduction to “My First Test Session&quot; , so read on to find out more.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/deviceatlas-tada&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/deviceatlas-tada#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/tada">TADA</category>
 <category domain="http://mobiforge.com/tutorial">Tutorial</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1088</wfw:commentRss>
 <pubDate>Tue, 17 Jun 2008 15:31:00 +0000</pubDate>
 <dc:creator>daniel.hunt</dc:creator>
 <guid isPermaLink="false">1088 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Image Resizing</title>
 <link>http://mobiforge.com/testing/story/fixit-image-resizing</link>
 <description>&lt;p&gt;Images such as bitmaps have an intrinsic pixel size. Telling the browser in advance what the size is avoids it having to re-flow the page when it receives it. Resizing images at the server reduces the amount of data transferred and the amount of processing the client has to carry out to scale the image.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-image-resizing&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-image-resizing#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/802</wfw:commentRss>
 <pubDate>Thu, 07 Feb 2008 17:26:09 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">802 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Measures</title>
 <link>http://mobiforge.com/testing/story/fixit-measures</link>
 <description>&lt;p&gt;Avoiding pixel and absolute measures allows the browser to adapt content to fit the display, though there are exceptions to this rule (see below). This test checks for the use of absolulte and pixel measures where relative measures would be more appropriate&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-measures&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-measures#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/797</wfw:commentRss>
 <pubDate>Mon, 04 Feb 2008 17:03:47 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">797 at http://mobiforge.com</guid>
</item>
<item>
 <title>Fixit - Tables</title>
 <link>http://mobiforge.com/testing/story/fixit-tables</link>
 <description>&lt;p&gt;This test determines if your page uses tables. Tables do not work well on limited size screens and may result in the user having to scroll horizontally to read them. Putting navigational links into tables may result in the user having both to scroll horizontally and vertically to see possible navigational choices.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/fixit-tables&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/fixit-tables#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/dotmobi-compliance">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/788</wfw:commentRss>
 <pubDate>Fri, 01 Feb 2008 17:45:21 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">788 at http://mobiforge.com</guid>
</item>
</channel>
</rss>
