Testing

A Guide to Mobile Emulators

mokil — Wed, 14 Oct 2009 16:15:31 +0000

In a previous article, 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.

For the uninitiated, an emulator is a software program that aims to replicate the functions of a specific piece of hardware or software.

Post Markup Directly to mobiReady.com

ruadhan — Fri, 28 Aug 2009 11:33:37 +0000

If you missed our newsletter yesterday you are probably not aware of a small announcement we made in it. We've pushed out a few updates to mobiReady.com, our mobile-readiness page testing tool. The most significant change is that you can now post markup directly to the service, instead of posting a URL for the service to visit and test.

Testing Mobile Web Sites Using Firefox

mokil — Wed, 12 Aug 2009 11:34:27 +0000

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.

User-Agent Switcher for Safari 4

atrasatti — Tue, 30 Jun 2009 15:57:26 +0000

The User Agent Switcher plug-in for Firefox has been a GREAT add-on and we all love it. 1 year and 27 weeks ago Ronan wrote a really simple, but useful configuration file for it that is available here on mobiForge (if you use Firefox it's a MUST: User Agent Switcher config file).

Location, Location, Location

jonarne — Sun, 07 Jun 2009 20:19:27 +0000

Location based services (LBS) has been a buzz word and a hype since birth of mobile services. I'm not saying that it is a failure!

Fennec Delivers!

ruadhan — Thu, 21 May 2009 16:49:20 +0000

We've all been eagerly anticipating the entry of the Fennec (Firefox Mobile to the uninitiated) into the mobile browser space. A couple of days ago we were given our first taste of the future with Fennec when a new alpha version was released for Windows Mobile devices. So how does it stand up?

Well, initial testing seems to indicate that Fennec will certainly be a contender. The Fennec team have packed in support for a wide array of technologies.

AutoTrader.mobi is 1Mth page tested by mobiReady

ruadhan — Wed, 20 May 2009 12:19:29 +0000

We're happy to announce a great milestone today: autotrader.mobi was the 1 millionth page that was tested by our mobiReady testing tool!

We're super happy about this, and we're delighted to see some well known brands such as AutoTrader making use of our free testing tool. Check out their results here.

TADA Usage Snippets

daniel.hunt — Tue, 05 May 2009 10:00:00 +0000

Regular contributors to DeviceAtlas will hopefully already know what TA-DA is, but in case you need a refresher class, you can have a quick glance at a few of these pages if you want. Back? Good.

Getting started with the ready.mobi API

ruadhan — Thu, 19 Mar 2009 12:50:56 +0000

Ready.mobi 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.

Ready.mobi API update

ruadhan — Thu, 19 Mar 2009 12:50:38 +0000

We've just gone live with an new version of the ready.mobi API. (Full details and code samples here). So what's new in this version? The most notable feature in this version is the ability to post markup directly to the ready.mobi API without having to supply a publicly accessible URL to the service.

This is the result of some early feedback on the API that during the development cycle pages often did not have a public URL, and so they could not be tested with ready.mobi.