BLOG

MOBILE APP TESTING BEST PRACTICES

MOBILE APP TESTING BEST PRACTICES

NSTALLING AND LAUNCHING

OTA INSTALL

The appliance ought to install over-the-air (OTA), with the icon for the appliance found from the device.

LONG LAUNCH TIME

all applications ought to apprise the user if there’s getting to be an extended launch time. If the appliance takes longer than 5 seconds to be prepared to be used, a progress bar or a message ought to be flaunted to tell the user what’s happening.

MEMORY AND FILE STORAGE THROUGHOUT RUN

For associate degree application that writes to the classification system, make sure that it properly handles out-of-house exceptions throughout execution, and offers a meaning warning to the user advising regarding lack of house once a file is making an attempt to be held on.

CONNECTIVITY

Users might need 2 kinds of property – e.g. wireless local area network and cellular – and therefore the device may well be switch between the two. The app should reply to this.

BLOCKED CONNECTIVITY

Make sure that it will handle the network affiliation being invalid/unusable (e.g. information affiliation / APN not properly started or invalid for the current carrier) or the device is switched into offline / flight mode.

The user ought to be notified with an associate degree applicable message if this occurs: ideally, the appliance ought to indicate that the device is in plane mode (or equivalent) stating that the appliance cannot run with success.

NETWORK DELAYS AND LOSS OF AFFILIATION

once the appliance uses network capabilities, it ought to be able to handle network delays and any loss of affiliation, giving a transparent error message to the user indicating there was a mistake with the affiliation.

MESSAGING & CALLS

SENDING OR RECEIVING SMS AND/OR MMS

For associate degree application that sends and/or receives SMS or MMS messages as a part of its operating, makes sure that it will send messages with success and that:
a) A notification of a brand new message is given wherever enabled on the receiving phone
b) The message is the correct format, and, wherever MMS is concerned, it contains the right payload.
It ought to be ready to use coincidental connections properly and also the user ought to be ready to manage the connections through the affiliation Manager.

HANDLING TELEPHONE CALLS & MESSAGES WHEN APPLICATION IS IN USE

The user should be ready to settle for associate degree incoming telephone whereas the applying is running. It ought to then be potential to resume from a similar purpose within the application at the top of the decision, or a logical re-starting purpose.
The applying mustn’t block the user from creating emergency calls on a cellular network.

EXTERNAL INFLUENCE

MEMORY CARD INSERTION

For an application on a device that supports removing an exchange memory cards whereas applications area unit running, the applying ought to handle this graciously and still operate as designed.

USER INTERFACE

BATTERY LIFE

Consider battery management, and permit the power-saving options of the device to be used, including sleep functions for the screen and the device itself.

DON’T HIJACK THE NATIVE EXPERTISE

Only hide the standing bar wherever the application’s user expertise is healthier while not it. The rear button must always navigate through previous screens. Use native icons systematically. Don’t override the menu button. Instead, place menu choices behind the menu button.

Respect user expectations for navigation. The rear button must always navigate back through previously-seen screens.

Always support electronic device navigation. Perceive your navigation flow once the entry purpose could be a notification or appliance.

Navigating between application parts ought to be simple and intuitive.

BROWSE TIME AND READABILITY

There ought to be a snug quantity of your time for content reading. Every screen ought to be visible for the time necessary to well browse all its data. Everything within the application ought to be a font size and kind that’s decipherable by the user.

BIT SCREEN USE

For applications employed in a slight screen device while not stylus, on-screen parts ought to be of a comfortable size and responsiveness to supply a decent user expertise.

SCREEN REPAINTING

The applying screens ought to be properly repainted, as well as cases once editing boxes and dialogue boxes area unit unemployed. Also, there ought to be no blinking of moving objects and background. If the applying objects overlap they have to still render properly.

CONSISTENCY

the applying UI ought to be consistent and perceivable throughout, e.g. displaying a standard series of actions, action sequences, terms, layouts, soft button definitions and sounds that area unit clear and perceivable

APPLICATION SPEED

The applying ought to add the device it had been targeted for, {and ought to and will and may} be usable on the device: the speed of the applying should be acceptable to the aim of the applying and should not alter the user expertise by being uncontrollable.

The speed of the applying ought to be adequate for the applying usage (i.e. the frame rate or response to user input ought to stay adequate, and not compromise the applying usage, or forestall the user from progressing normally).

ERROR MESSAGES

any error messages within the application ought to be clearly perceivable. Error messages ought to clearly show a user the character of the matter, and indicate what action has to be taken (where appropriate).

OPERATE PROGRESS

any operate selected within the Application ought to provide proof of activity at intervals 5 seconds. There ought to be some visual indication that the operation is being performed. The visual indication may be something that the user would perceive as a response, e.g.

— prompting for user input;

— displaying splash screens or progress bars;

— displaying text like “Please wait…”, etc.

ACTIONS WHEREAS PERFORMING ARTS CALCULATIONS OR IMAGE RENDERING PROCESSES

the user show and application activity ought to stay consistent and stable once calculations or image-rendering processes area unit being performed.

MULTIPLE SHOW FORMAT HANDLING

Wherever the device and application will show in multiple formats (e.g. portrait/landscape, internal/outside display), the weather of the applying ought to be properly formatted altogether show environments, with the applying displaying properly while not obvious errors altogether formats.
If the applying is meant to be used solely in landscape mode, then the applying ought to be forced so it can’t be revolved to portrait mode. Constant applies to applications supposed to be run in precisely portrait mode.

DIFFERING SCREEN SIZES

wherever the applying is meant to figure on multiple devices it should be able to show properly on differing screen sizes.

MULTIPLE FORMAT INPUT HANDLING

wherever the device and application will settle for input in multiple formats (e.g. external bit screen / external keyboard / internal bit screen / internal keyboard / QWERTY layout / 12-key lay

ACCELEROMETER/MOTION SENSOR RESPONSES

wherever each the device and therefore the application use measuring device/motion device support, the response of the applying to movement or amendment of alignment of the device mustn’t impair the use of the applying, nor be possible to confuse the user. The applying ought to the amendment between portrait and landscape modes while not confusing errors being flaunted to a user.

WRITING SYSTEM ERRORS

The applying ought to be freed from writing system or language errors unless they’re a part of a deliberate style idea.

TECHNICAL TEXT ERRORS

The text within the application ought to be clear and clear. The applying ought to be free from technical text show problems such as Text discontinue / Text overlapping, and everyone text in every target language ought to be displayed while not corruption, distortion or different show issues.
Problems to avoid are:
– Menu item text labels incorrectly aligned with pointer
– Button text label over-running the button space or truncated such it’s that means isn’t clear
– Text over-running or being truncated in different finite text show areas (e.g. speech bubbles, programme components etc.)
– Text not wrapping at the sting of the screen leading to words being discontinue
– Multiple items of text overlapping one another, or text overlapping programme components
– Text being cut horizontally.

LANGUAGE

Correct operation
Make sure that the applying works properly with all acceptable languages and permits the user to pick out languages if acceptable, with the right rendering.

SUPPORTED FORMATS

Verify that date, time, time zone, week start, numeric separators and currency, square measure formatted fittingly for the enforced language’s target country and supported throughout the applying.
Out and others), it ought to work properly with all supported input strategies.

INTERNATIONAL CHARACTERS AND UNITS OF MEASUREMENT

Make sure that the applying accepts and displays all acceptable international characters and units of measurements correctly, according to the local market needs.

PERFORMANCE

SUSPEND/RESUME

Wherever associate degree OS atmosphere supports ‘suspend/resume’, make sure that the applying suspends and resumes at some extent that doesn’t impair the user expertise.

RESOURCE SHARING – INFORMATION

Wherever there are multiple applications that build use of a typical information (for example, calendar synchronization and calendar viewing), the information ought to be properly shared between those applications.

MEDIA

APPLICATION MUTE POSSIBILITY

For applications with sound settings, there ought to be a Mute or Sound On/off setting, unless the applying doesn’t have Application mute facility deliberately it respects the settings of the telephone set volume buttons.

SETTINGS STATUSES COMPREHENSIBLE

Wherever the applying has settings choices, make sure that the settings statuses are simply comprehensible at any stage within the application’s journey.

SAVING SETTINGS

Wherever the applying has settings choices, make sure that the applying saves all settings on exit which restarting the applying can restore the saved settings.

SPECIFIC FUNCTIONS

For applications with sound, guarantee application sounds have specific functions and will not be over-utilized – e.g. a game finishing with a second of random noise ought to be avoided.

MENU

HELP AND ABOUT

An application with the user interface capable of displaying information to the user should contain standard Menu items Help & About (or equivalent information in a format easily found and understood by the user) to explain to the user how the Application works.
If it is clear that the application’s purpose requires network coverage to operate, then it would be sufficient for the Help to be provided through a browser connection rather than being contained in the application. In the opposite case, where most functions of the application can be used while the device is offline, then the application should have Help that can be accessed without needing a data connection.
Menu items like Help and about should be presented on the main menu or another easily found screen of the application.
About functions should contain the application name, application version number, and author information.
Help should include the aim of the application, usage of the keys (e.g. for games) and other instructions. If the text of the help is too long, it should be divided into smaller sections and/or organized differently.
Help must be accurate and consistent with the application functionality and the handset specifics.

VALID ACTIONS

All application items that can be selected and/or changed by the user should do what the application is intended to do.

FUNCTIONALITY

FUNCTIONALITY SANITY CHECK

All specific application functionality such as algorithms, calculations, measurements, scoring, etc. should be implemented correctly.

APPLICATION HIDDEN FEATURES

The applying should not introduce any hidden features: its functionality set should be in keeping with the assistance and it mustn’t damage the information on the device. However, the subsequent hidden functions square measure OK: Cheat codes and therefore the unlocking of associate application to upgrade from a demo version to a full version.

KEYS

SCROLLING IN MENUS

For associate application with user interaction, once the computer keyboard or alternative navigation device is employed to scroll vertically and (if applicable) horizontally within the Main menu item list, there ought to be no adverse result on the applying. Additionally, associate application ought to be able to lock itself in a very vertical or horizontal read if seen as vital from an application-use purpose of reading.

CHOICE KEY

For associate application with user interaction, pressing the first choice key or device equivalent within the main menu item list ought to choose the menu item with no unwanted effects on the applying.

TEXT FIELD SCROLLING

For associate application with user interaction, the scrolling functions of the computer keyboard or alternative navigation device in a very text dialogue (for example: regarding and Help) ought to scroll vertically and (if applicable) horizontally within the dialogue.

PAUSE

For associate application wherever time-sensitive immediate user intervention is required, the applying ought to support an interruption feature within the areas of the applying wherever this can be applicable (for example in-game).
The user ought to – wherever necessary – be able to simply pause and resume the applying.
All time-specific options of the applying ought to be disabled at the time of the pause.
There ought to be a transparent indication that the applying is in a much-paused state.
There ought to be a transparent indication of however the user will come from the paused state.

COINCIDING KEY PRESSES

For associate application with user interaction, make sure that it copes with coinciding key presses by not golf shot the applying into associate unusable or incomprehensible state by coinciding key presses. Any error messages generated ought to be meaningful.

MULTI-KEY PRESSES

For the associated application that supports multi-keypress actions (on a tool that conjointly supports this), they must perform as expected and may not leave the applying in an associate unusable state.

DEVICE SPECIFIC TESTS

DEVICE GAP AND SHUTTING

For associate application on a tool with open / shut practicality, make sure that it handles gap and shutting off the device properly whereas launching and returns to the identical state before the interruption.

STABILITY

APPLICATION STABILITY

The applying mustn’t crash or freeze at any time whereas running on the device.

APPLICATION BEHAVIOR WHEN FORCED OBTAINABLE SYSTEM

The applying ought to preserve enough state info to address strong-arm obtainable the system. It mustn’t lose any info that it implies would be preserved, nor become tough to use later on, as a result of a strong-arm closure by the system.

DATA HANDLING

SAVE GAME STATE

For associate application wherever the user might exit a half completed game or wherever a player high score worth is known, make sure that it will save its game state/high score table info into persistent memory.

KNOWLEDGE DELETION

Wherever associate application contains a perform to delete knowledge, it ought to indicate whether or not know are going to be for good deleted or provide simple reversal of the deletion.
The user should be needed to substantiate deletion of information or have an associate choice to undo the deletion, to cut back the risk of accidental loss of knowledge through user error.

SECURITY

ENCRYPTION

All sensitive info (personal knowledge, MasterCard & banking info etc.) should be encrypted throughout transmission over any network or communication link.

PASSWORDS

If an associate application uses passwords or alternative sensitive knowledge, the passwords or alternative sensitive knowledge mustn’t hold on within the device and not echoed once entered into the applying. Sensitive knowledge should protect by countersign. If attainable, all hold on countersign ought to be encrypted
With passwords, the required approach is that the applying shows that character the user designated then changes that to the associate asterisk (*).
If the user is expressly asked for permission, a countersign is often held onto the device memory.
It’s vital to attenuate the chance of access to sensitive info ought to the device be lost, by making certain that no authentication knowledge are often re-used by merely re-opening the applying.
Once sensitive knowledge has been entered, it mustn’t be displayed in plain text anyplace within the application. But it’s typically acceptable to possess no quite twenty-fifths of a sensitive worth displayed in plain text (e.g. four of the sixteen digits of a card number) wherever this assists the user to differentiate between multiple cards or accounts.

Leave a comment

Your e-mail address will not be published.

Enjoy this blog? Please spread the word :)