Software Testing Blog

In my recent post with my thoughts on the iPad, I noted that while the iPad will run iPhone apps, they won’t look that great.  Instead, developers will need to create new iPad apps.

“That’s fine!” you exclaim, thinking that you’ll just uprez your widgets and artwork from your iPhone app to the new iPad screen size.  Problem solved, right?  Apparently Apple thought so too and tried creating iPad sized versions of their default iPhone apps.  And apparently that idea sucked.  From Daring Fireball:

It’s not that Apple couldn’t just create bigger versions of these apps and have them run on the iPad. It wasn’t a technical problem, it was a design problem. There were, internally to Apple (of course), versions of these apps (or at least some of them) with upscaled iPad-sized graphics, but otherwise the same UI and layout as the iPhone versions. Ends up that just blowing up iPhone apps to fill the iPad screen looks and feels weird, even if you use higher-resolution graphics so that nothing looks pixelated. So they were scrapped by you-know-who.

Think this is just an Apple problem?  No, it’s a mobile device problem!

Read more…

For most who read a software testing blog, web access is a given — it’s always on, always up, usually fast, and even available on-the-go (as long as you remember to bring your Nexus One, Curve, iPhone, etc).

But not too long ago, the web was still in early adopter mode.  It was available (maybe) after you fired up that block you called a desktop computer; and after you endured the sound of your dial-up connection; and only if you exhibited zen-like patience with pop-ups and page load times.

Why am I taking this trip down memory lane?  Well, it could be because I saw the extended trailer for Hot Tub Time Machine (destined to be a classic, but NSFW).  More likely, however, is the fact that yesterday I read a couple of interesting pieces from Mashable & the BBC — about the global adoption of the Internet in the past decade, and the provocative question of whether or not web access is an inalienable human right in this day and age.  Both are worth checking out, if for no other reason than to make us appreciate what we have.

Read more…

Today Apple announced their much anticipated tablet computer – the iPad.  With a 9.7 inch screen, the iPad is a supersized iPhone; and it’s already inspiring both love and hate from Apple fans worldwide.  Comments so far have ranged from “I want it now” to “I was expecting a lot more than an XL version of the iPhone with no phone capabilities.”

So what does the iPad mean for developers, testers, and Apple users?  Here are a few thoughts:

Layout now matters for iPhone developers.
Up until now, an iPhone app was one size fits all.  Every iPhone has the same resolution, meaning apps didn’t have to worry about scaling up or down.  Not anymore!  The iPad is a larger device, but it runs the same iPhone apps.  While it can automatically scale up an app designed for the iPhone, the results are kind of ugly.  The bigger screen real estate opens a lot of interesting possibilities, but for iPhone developers now is the time you need to start worrying about how your app will look on a larger screen that isn’t 480×320.

New interface means new challenges.
If it’s not enough that the iPad comes in a different size, now developers will also have a slew of new interface widgets to work with.  Whether or not those widgets will be available on the iPhone remains to be seen, but whatever the case developers will have their hands full making sure their apps look correct on each platform.

Testers needed!
Read more…

Nick Jones over at Gartner wrote a great piece about the current state of mobile apps.  It’s a must-read for mobile app developers and marketers.

His post is written about the iPhone, but it applies equally to Android, Blackberry or Symbian apps.  It also helps to explain why mobile apps have been the fastest growing segment of the uTest biz (phenomenal growth + still evolving market = a lot of testing to do).

Here are a few realizations from his recent trip to his local Apple store that seemed especially relevant for our readers (bullet points are his and the running commentary is mine) :

Read more…

Bug-iversary Alert! Tomorrow is the 20-year anniversary of the “crash” of the AT&T Long Distance Network. On January 15, 1990 faulty software was installed on the AT&T Electronic Switching System (Number 4 ESS): a one-line bug incapacitated the entire system, disabling switches throughout half the network.

Known as one of the most serious telecom bugs in history, more than 75 million calls were not connected during 9 hours, an estimated $60 million loss.

Dennis Burke of California Polytechnic said it best: “The Jan. 1990 incident showed how bugs in self-healing software can bring down healthy systems, and the difficulty of detecting obscure load- and time-dependent defects in software.”

Speaking of “load defects,” AT&T — after signing up to be exclusive U.S. provider of iPhone service — has recently come under fire for the quality of its network coverage. Businessweek’s top headlines read:

• An AT&T Mystery: Abrupt New York iPhone Shutdown
• AT&T Mulls Plans to Deal with iPhone Data Demand
• Can AT&T Meet iPhone Network Demands?

In light of this bug-iversary, I can’t help but wonder if more testing should have been done before AT&T took on the massive data demands of modern 3G smartphones? What do you think?

Pundits are predicting a breakout year for Android in 2010.  The upstart mobile OS (if you can call anything Google does an ‘upstart’) is earning rave reviews from mobile app developers, and is growing rapidly.  And while the Android Market and it’s 20,000 apps have a ways to go before catch up with iPhone and it’s 100,000 approved apps, the growth has been impressive.  As we’ve seen time and time again, he who wins the hearts & minds of the development community, wins the battle.

Also helping Android’s case are some great new smartphones from manufacturers like HTC, Motorola and Samsung.

Robin Waulters from TechCrunch wrote a great piece today detailing the milestone and making some predictions for 2010:

2010 is going to be a big year for the Android operating system, with many new handsets finding their way to stores around the world (including Google’s own phone) and an increasing number of developers building tools, games and the likes for the fast-growing platform.

One way of noticing that the OS is poised for a big breakthrough at the expense of Windows Mobile, Symbian and other operating systems designed to run on various mobile devices, is the number of applications already available for download in the platform’s own application store, Android Market.

Waulters cited recently published data from AndroidLib, which showed an wildly impressive growth line for the Android Market (see the chart after the jump):

Read more…

When our Guest Blogger series began a few months back, you might recall that it was Bernard Lelchuck who got things started. For those who are new to uTest, Bernard has been one of our top testers from the get-go, and you can read more about his background and uTest experience by checking out his Tester Spotlight. In his latest post, he explains how he got into the lucrative field of mobile app testing – and how all testers can (and should) do the same. Enjoy!

If you haven’t noticed, the use of mobile applications has skyrocketed over the past few years. And while most mobile companies are lagging behind Apple’s success, the market itself has nevertheless become a multi-billion dollar endeavor. As one might expect, this success has prompted competitors of all sorts to rush and open their own mobile application stores. They naturally seek greater market share, and who could blame them?

According to a recent report published on the Wireless Expertise website, “the global mobile app market – including games – will be worth $4.66 billion in 2009, rising to $16.60 billion, in 2013.”

This of course would help explain the sudden entrance of Microsoft, Google, Research in Motion (RIM) and Palm, along with mobile vendors like Verizon and AT&T into the mobile market. As I like to say, they are trying to catch the fast-riding “Mobile App Train.”

And what a ride it’s been! Since the 1^st gen iPhone was released in June of 2007, almost every leading mobile vendor has changed their products to look, feel and be as cool as the iPhone (with varying degrees of success).

Which brings me to mobile testing. But before I discuss the testing implications of this iPhone mimicking trend, I’d like to address how I got into mobile testing in the first place.  It’s my hope that this story will encourage other testers to consider furthering their careers by hopping on board the Mobile App Train.

Read more…

Mobile bugs are becoming a bigger and bigger problem, and iPhone users are the latest to be affected by buggy software.  Techcrunch reported yesterday that a bug in Safari causes it to consume bandwidth even when it’s closed.  The problem arises with the use of Motion JPEG (or M-JPEG), a video standard that is built off of the JPEG images standard.  When an iPhone user visits a page with an M-JPEG video, Safari will download continuously, even if the user pushes the Home button to end Safari and go back to the home screen.

What makes this problem really terrible is that many mobile users are charged for their bandwidth usage.  Even AT&T users, who are used to having unlimited data plans in the United States, can be charged for data consumption while traveling internationally.  That can mean big bills when they get back home.

Cellular service providers aren’t immune either.  Networks around the world are struggling to keep up with the data demands of the iPhone, and providers certainly don’t need to deal with unnecessary data consumption caused by broken software.  That means companies like AT&T are building out extra infrastructure to support buggy apps – something that costs you and me money in our phone bills.

For the security researchers who uncovered this bug, one hour of testing resulted in $3,000 worth of data charges. That is serious money, and anyone developing mobile apps should take heed.  Your broken app can cost enough money to buy 10 iPhones, and that’s a great way to get some bad press.  Further proof that mobile application testing needs to catch-up to the standards of web and desktop testing.

Mobile is the next great frontier for games, music, media and more.  In fact, Gartner says that  more than 139 million smartphones were sold last year.  And the phone makers aren’t slowing down:  Apple is planning to launch the iPhone into the Chinese market and a more affordable Android handset expected to hit the market by the end of ‘09.  But haven’t we all learned that big markets make big targets — for VC dollars, for advertisers, for media coverage… and for hackers.

Doug Gross wrote a very interesting article over at CNN Tech about the one trend that could threaten to derail the otherwise unstoppable mobile movement.

Security analysts say they’ve already seen all of the major online threats — Trojan horses, viruses, worms — spreading on smartphones, often through e-mail attachments sent to the phones.

And as mobile apps have evolved from games and tip to calculators to company email, financial transactions and other mission-critical activities, the risk of security exploits grows considerably for mobile users and their employers.

The good news, experts say, is that phones present problems for hackers and other bad guys that traditional computers don’t.

Most viruses and other malware are designed for Windows, because that’s the most popular operating system. Since smartphones use a variety of different platforms, someone writing malicious software needs to pick and choose.

Wow, getting code to work across mobile platforms is so hard that even the hackers are having trouble!

Read more…

Every startup team has great and spirited debates about its products (or services).  We debate what works, what doesn’t, what makes it unique, and most importantly, what users want. We draw inspiration when new products launch and change the world.  Think Salesforce.com back in the day, the family of iPhones or, more recently, Facebook and Twitter.

And similarly, we witness product missteps that make us wince, rant or just shake our heads.   One such case emerged today with DiggBar (Digg’s URL shortening service) under the bright lights of a TechCrunch article titled, DiggBar Commits Career Suicide, Starts Redirecting To Digg Homepage.  In the words of  TC’s Jason Kincaid:

Read more…