Software Testing Blog

So maybe it wasn’t AT&T’s fault after all.

Apple recently revealed that there is a fundamental flaw in their method for calculating how many signal bars to display.  And we have the iPhone 4 (and its “learn to hold your phone the right way” fiasco) to thank for bringing this software snafu to light.

CNN Money shares the following details from Apple:

“Upon investigation, we were stunned to find that the formula we use to calculate how many bars of signal strength to display is totally wrong,” Apple wrote in a statement posted on its website. “Our formula, in many instances, mistakenly displays 2 more bars than it should for a given signal strength.”

That means, for example, that iPhones sometimes display four bars when they should be displaying two. Apple said users reporting a significant drop in bars when they hold their iPhone 4 are probably in an area of “very weak signal strength” but were unaware of that because the phone displayed four to five bars.

“Their big drop in bars is because their high bars were never real in the first place,” the company said.

Perhaps most surprising, Apple disclosed that the problem is not confined to the iPhone 4.  The faulty formula has been present in every iPhone model since the 2007 original.  Questions remain about whether the issue is strictly software-related, or if it also involved hardware problems.  However, Apple has said it will release a free software update in the next several weeks to fix the glitch. It will use a new formula recommended by AT&T.

News has been all over the web the past few days about the AT&T and iPad security breach.  If you haven’t heard the details, in short a group of hackers discovered a vulnerability in AT&T’s private web APIs where one could send the ICC-ID from an iPad SIM card and AT&T’s servers would send back the corresponding owner’s email address – no authentication required. Since the ICC-IDs for the iPad are somewhat predictable, it was trivial for the hackers to send in thousands of semi-random guesses and collect any email addresses that came back. Some of those addresses were for people with addresses from domains like faa.gov and us.army.mil.

The hackers claim they reported the flaw to AT&T before sending their discovery to the fine folks at Gawker. AT&T, on the other hand, was not pleased to see their security problems appear in a popular tech blog at all, and had this to say in an email to their iPad customers:

On June 7 we learned that unauthorized computer “hackers” maliciously exploited a function designed to make your iPad log-in process faster by pre-populating an AT&T authentication page with the email address you used to register your iPad for 3G service.

…

The hackers deliberately went to great efforts with a random program to extract possible ICC-IDs and capture customer email addresses.

So who’s to blame for a problem like this? Is it AT&T, or do the hackers themselves deserve some of the blame for the public way they handled their disclosure? Give us your thoughts below.

If you live in the United States and own and iPhone, chances are you’re aware that AT&T has some reliability issues.  As the sole mobile service provider for iPhones in the US, AT&T has seen their usage skyrocket and their reliability crumble in the past few years. Everyone has an opinion about why, but as of today AT&T has revealed what they see as one big problem: heavy bandwidth usage.

Starting this month, AT&T will now limit the amount of data an iPhone or iPad may consume in a given month.  The caps start at 200MB, but for an additional fee you can have all the way up to 2GB.  Existing users will continue to have an unlimited data plan for now, but new contracts will not have that option going forward.

AT&T says that 98% of their customers use less than 2GB of data per month, which means that most people won’t hit the top usage cap.  However, many people will still opt for the lower 200MB data cap because it will actually be cheaper than their current unlimited iPhone data plan.  That means software developers have an interesting new challenge on their hands – bandwidth optimization.

Read more…

Whenever you put a bunch of big brains with vast expertise about a still-evolving industry in the same room, you’re bound to get some interesting and impassioned debates.  Such was the case at Monday’s pre-conference sessions at CTIA Wireless in Las Vegas. There were a number of excellent speakers representing the perspectives of OEMs like Nokia and LG; carriers like Verizon and AT&T; and content providers like Travelocity and MTV.

I sat in on several of these sessions and heard a number of important topics being discussed that will have major implications for the future of mobile apps and mobile commerce.  These debates included:

• Android vs. iPhone vs. Blackberry vs. Symbian
• Free vs. Paid apps
• OEM app stores vs. Carrier app stores

But perhaps the most interesting, fierce and recurring debate that I heard at CTIA was around the topic of… Read more…

Over in Barcelona at the Mobile World Congress, 24 of the world’s leading wireless carriers and mobile OEMs announced their plans to create the Wholesale Applications Community (WAC) — a unified platform which developers can use to build a mobile app once and have it run seamlessly on any handset, OS or carrier.  Among the impressive roster of backers are mobile heavyweights like AT&T, Verizon, Orange, LG and Sony.  Sounds like a utopia for mobile developers, right?  It could be… if it works.

There are more than a few skeptics, including Jason Kincaid (@jasonkincaid) over at TechCrunch.  As Kincaid states (with a bit of help from Google’s Andy Rubin):

If it sounds too good to be true, that’s because it probably is. Andy Rubin, Google VP of Engineering (and the man in charge of Android) has already shared his skepticism, saying, “There is always a dream that you could write [a program] once and [have it] run anywhere and history has proven that that dream has not been fully realised and I am sceptical that it ever will be“. To put it another way, this is a pipe dream from carriers looking to loosen Apple’s stranglehold over mobile applications and there’s very little chance that it’s going to work.

The reasons Kincaid thinks the WAC won’t work out include:

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…

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?

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.