Knowledgebase

Testing Mobile Applications Print

  • softwaretestingqa, software, performance, permissions, guide, howto, solution, zillionkinghost
  • 0

Verification on phones.

WHAT DIFFERS FROM OTHER PLATFORMS

Interruption is constant Connectivity varies Devices vary enormously Permissions can be refused and revoked Updates reach users slowly

WHAT TO TEST SPECIFICALLY

Rotation during a task Backgrounding and returning after a long period Termination and relaunch Incoming calls and notifications Permission granted, refused, and revoked later No network, and slow network Low storage and low battery Largest system font size Upgrade from the currently released version

WHY UPGRADE TESTING MATTERS MOST

It affects existing users, who have data, and failure on launch is unrecoverable for them.

WHAT DEVICE COVERAGE SHOULD PRIORITISE

Devices your users actually have.

WHAT TO ALWAYS INCLUDE

A modest device, which reveals what better ones conceal.

WHAT EMULATORS CANNOT VERIFY

Performance Battery consumption Camera and sensors Real network behaviour

WHAT DEVICE FARMS PROVIDE

Breadth across models remotely.

WHAT THEY DO NOT REPLACE

Holding a device and using it.

WHAT TO TEST BEFORE EVERY RELEASE

The release build, on physical devices.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot