Posts Tagged ‘APP’

  • Verified that the link takes you to the page it said it would.
  • Ensure to have no orphan pages (a page that has no links, on buttons, tabs
  • etc to it)
  • Ensure that all referenced links or email addresses must be hyperlinked.
  • Check all mailto links and whether it reaches properly
  • Ensure that all the data’s inside combo/list box must be arranged in chronological order.
  • Check the maximum field lengths to ensure that there should not any truncated characters.
  • Assure that leap years are validated correctly & do not cause errors/miscalculations.
  • Include value zero in all calculations.
  • Assure that upper and lower values in ranges are handled correctly. (Using BVA)
  • Each field should get highlighted when the cursor is in that field.
  • Default values on page load/reload (Also terms and conditions should be disabled)
  • Ensure that division by zero does not occur.
  • Navigation should work correctly with the input methods offered by the device.
  • An application for a touch device should use touch interaction to navigate all functions/screens of the application, e.g. tapping buttons, navigating lists etc.
  • Ensure that all interactive elements such as buttons must respond to touch interaction on first use. It must not be difficult to touch an interactive element, such as a button, link, image, etc.
  • Checks weather all requirements and checkpoints are covered.
  • Give multiple inputs (Text inputs) at a time and the app should work according to that.
  • Check the app weather it syncs with native functionalities.
  • Whether checks for optional and mandatory fields carried out like a mandatory field should not be left blank and an optional should allow the user to skip the field.
  • Closing of the application should result in “Are you sure?” message.(Depends upon app)
  • Verify if the application continuous from the same place after minimizing and restarting it.
  • Ensure that home page of an app should be loaded quickly within 8 seconds.
  • If the device is tilted from portrait mode to landscape mode and vice versa, the app should self adjust as per the device resolution (condition: if the application supports both landscape and portrait modes).
  • If the device is tilted from portrait mode to landscape mode, the screen should display an error message asking the user to switch the device back to landscape mode or the screen resolution should not change (condition: if the application supports only portrait mode)
  • If the device is tilted from landscape mode to portrait mode, the screen should display an error message asking the user to switch the device back to portrait mode or the screen resolution should not change (condition: if the application supports only landscape mode)
  • Verify the functionality for the Background music [If any]
    • When music running in the background of the App/game
    • App goes into idle mode
    • When app comes from the idle mode

Expected behavior: Background music should be running.

  • When the Application uses network capabilities, it must be able to handle network delays and any loss of connection.
    Launch the Application.
    Start the network access from the Application.
    Put the phone in a place where there connection will be lost.
    Observe the result.
    Expected behavior: The Application will work until time out and then give an error message to the user indicating there was an error with the connection.
  • When the Application uses network capabilities, it must be able to handle the device being in Airplane mode.
    Set the device to Airplane mode
    Start the Application.
    Observe the result.
    Expected behavior: The Application will give a meaningful error message to indicate that the device is in Airplane mode and the application cannot run successfully.
  • Verify for the Network Reachebility.
    Expected behavior: Popup should be detect when the network is unavailable and provide a (pop-up) message informing the user.
  • Verify the Materials or Advertisements.
    Expected behavior: Marketing materials or advertisements should not be there at the app (app will be rejected)
Advertisements

Test Cases for Android Apps (Test Cases Regarding External Influence):

Senario no.1

Ensure that the Application works correctly following a memory card insertion action when the Application is suspended and resumed.

Steps to Scenario:

1. Launch the Application.

2. Suspend Application

3. Insert the memory card into the phone, and mount the card.

4. Fill the card to its capacity

5. Unmount the memory card.

6. Resume and operate the Application

Expected Result:

The Application continues to operate as designed based on the Application specification and is not affected by the memory card insertion or mounting/unmounting.

Scenario no.2

Ensure that the Application works correctly during a memory card insertion and removal.

Steps to Scenario:

1. Launch the Application.

2. Insert and remove the memory card.

3. Verify that Application works correctly.

Expected Result:

1. The Application should work correctly following memory card insertion.

2. The Application should work correctly with memory card removed.

Scenario no.3

Ensure that the Application with memory card functional screens works correctly with memory card inserted and removed.

Steps to Scenario:

1. Launch the Application.

2. Navigate to screen where Application works with memory card.

3. Insert the memory card.

4. Verify that Application works correctly.

5. Remove the memory card.

Expected Result:

1. The Application should work correctly following memory card insertion.

2. The Application should work correctly following memory card removal.

Test Cases for Android Apps (Test Cases Regarding Storage):

a) Storage/Cache (verification points)

Go to the Device>Settings> App>

Here, all the Downloaded apps will be listed. It will show the location of app whether its Downloaded on internal memory, SD Card or currently in Running status.

Test Cases for category a):

1. Verify how much memory space (internal/SD Card) occupied by app.

(Occupied space shown just below the App name.)

2. Click on the app> it will redirect to the ‘App Info’ page

(I) we can verify here whether the App name and App version is as per the requirement

(ii) Under ‘Storage’ section:

a) Verify the ‘Total’ space occupied by the App, it should be as per the requirement

b) Verify ‘App’ storage, it should be as per the requirement

c) USB storage app: verify whether it occupies the space as expected

d) Data: verify whether the app uses the defined limit of data while running

e) SD Card: If app is installed in SD Card, very that app occupy as per the expected space

f) Cache: verify that cache space should be as expected (notice the behavior of app if cache space exceeded)

b ) App Storage

Test Cases for category b)

1.On installing the app into device, it should occupy the expected space

2.On moving app to SD Card, it should release the internal memory

3.On uninstalling the app from the device, it should released all the occupied memory (saved files that contain games level, application setting etc should be released)

4.If cache exceeded from expected memory, check the behaviour of app

5.If app provide the upgrade option (like Skype, Facebook etc) then check whether app provide the details of the size which it suggest for upgrading (if device memory will be less and we start upgrading then check whether app prompt the message regarding less memory or app crashes out)

Windows Phone Test Checklist-II

Test cases for Windows app:

16. Test Name:  Technical Support Information

Test Description:

  • Launch your application.
  • Verify that the application displays the application name, version information, technical support and contact information in a location that is easy to discover.

Expected Result:

  • Ensure that the application displays all the details regarding name, version information and technical support contact information about the application in a location that is easy to discover by the user.

17.  Test Name: Enabling/Disabling location services globally and within the app (Test case valid for an app that uses location based settings)

Test Description:

  • Navigate to settings page of the app under test
  •  Enable the loction based setting
  • Launch your application
  • Use the app so that it provides location based output
  • Click the Home button on the device to return to Home screen (your app becomes inactive)
  • Navigate to the setting page of the windows phone (global and particular to any app)
  • Disable the location based service
  • Verify that the app is still working correctly and cannot provide location based services

Expected Result:

  • Ensure that the application should be responsive even after closing the location services in the device.

18. Test Name:  Configurable Functionality(if any)

Test Description:

  • Launch your application.
  • Verify that the application UI or Settings menu enables the user to disable toast notifications(if any).

Expected Result:

  • Verify that there should be an option available to user in the menu to disable toast notifications.

19. Test Name:  Toast Notification Opt-In(if any)

Test Description:

  • Launch your application.
  • Verify that the application prompts the user upon first use of the BindToShellToast method.
  • This prompt must request explicit permission to receive toast notifications.

Expected Result:

  • Ensure that a message should be prompt  asking for an explicit permission from user to receive toast notifications.

20. Test Name:  Verify for Minimize Power Usage When Running Under a Locked Screen (Test case applicable to apps that use the windows idle detection service. If idle detection is enabled in provided in the app then the OS will be able to deactivate the app when it is idle. The only exception is when the app has a feature to play music and the feature is being utilized when the phone is locked)

Test Description:

  • Launch your application
  • Lock the device
  • Verify that any app’s user interface updates, active timers and other non-critical processing activities are halted by the OS

Expected Result:

  • Ensure that  any active timers, user interface updates or non-critical processing activities are halted by the application while running under locked screen.

 21. Test Name: Idle Behavior Under a Locked Screen (Test case applicable to apps that use the windows idle detection service. If idle detection is enabled in provided in the app then the OS will be able to deactivate the app when it is idle. The only exception is when the app has a feature to play music and the feature is being utilized when the phone is locked)

Test Description:

  • Launch your application which allows windows OS to detect if it is in idle state
  • Ensure that app is not playing music if it has such a feature in it, otherwise ignore this step
  • Lock the device
  • Verify that the application does not play music, and the device stays idle

Expected Result

  • Ensure that the device should stay idle when the application is paused under lock screen
  • Application should not play any music/sound under the lock screen

 22. Test Name:  Verify History List Updates if the application uses Music + Video Hub

Test Description:

  • Launch your application.
  • Play back a video or music media file within the application.
  • Navigate to the Music + Videos Hub
  • Verify that the History list contains information about the video or music media file that you played.

Expected Result:

  • Ensure that the History list in Music + Videos Hub contains information about the video or music media file that was played in the test application.

23. Test Name:  Verify Initial Launch Functionality of the test application

Test Description:

  • Play a music file.
  • Launch Test application.
  • Verify that while the application loads, it does not pause, resume or stop the actively playing music.

Expected Result:

  • Ensure that while the application loads, it does not pause, resume or stop the actively playing music.

24. Test Name:  Verify Configurable Functionality of the application

Test Description:

  • Launch your application.
  • Verify that the application allows a user to configure the background music or background music volume of the application.
  • Verify that changes made to these settings do not affect music playback on the device after the application closes.

Expected Result:

  • Ensure that there should an option available to user to configure the application’s  background music.
  • Ensure that changes made in the application’s settings do not affect music playback on the device after the application closes.

25.Test Name:  Verify if Application Plays a Video or Audio Segment

Test Description:

  • Play a music file from the  Music + Video Hub in the device.
  • While the music file plays, launch your application.
  • Play a non-interactive, full-motion video file or a non-interactive audio segment within the application.
  • When the file or audio segment completes, the background music of the device must resume from where it was paused.

Expected Result:

  • Ensure that After completing the video/audio segment in the test application the background music of the device must resume from where it was paused.

26.Test Name:  Verify Applications That Extend The Picture Viewer: Launch Behaviors

Test Description:

  • Tap the Pictures application in Windows phone.
  • Navigate to the Application Bar.
  • Tap Test Application name.
  • Verify that the application allows manipulation of the photo.
  • Navigate back to the Start screen and launch your application from the application list.
  • Verify that the application allows the user to choose a photo.

Expected Result:

  • Ensure that the application allows manipulation of the photo if the user is navigated through the picture application.
  • Ensure that the application allows the user to choose a photo if the user is navigated to the application from the start screen.

 27.Test Name: Verify Applications That Extend the Share Picker: Functionality

Test Description:

  • Launch the application.
  • Verify that the primary functionality of the application is to upload photos.

Expected Result:

  • Ensure that there should be an option available to user to upload or share photos.

 28.Test Name: Verify Universal Volume Control Commands with the test application

Test Description:

  • Launch your application.
  • Begin audio playback.
  • Close the application.
  • Verify that the audio continues to play in the background.
  • View the universal volume control.
  • If the playback service supports the pause command, pause the audio through the universal volume control, verify that
  • playback is paused, restart the audio through the universal volume control, and verify that playback restarts.
  • Stop the audio through the universal volume control.
  • Verify that the playback stops.

Expected Result:

  • Ensure that the application volume (music or sound etc.) can be adjusted by the universal controls
  • Ensure that if the volume is  muted or demuted from the universal control, the application’s volume should also be operated accordingly.
  • Ensure that if the playback is paused from the universal control, then the application’s playback should also be paused.
  • Ensure that if the playback is restarted from the universal control, application’s playback should also be restarted.

29.Test Name:Verify Universal Volume Control Strings

Test Description:

  • Launch your application.
  •  Begin audio playback.
  • Run the application in the background.
  • View the universal volume control.
  • Verify that the metadata for the audio playback appears and is relevant to the audio content.

Expected Result:

  • Ensure that the metadata for the audio playback appears in the universal control window and is relevant to the audio content which is playing.

30.Test Name: Verify if the application uses Audio Streaming Agent

Test Description:

  • Launch your application.
  • Close the application.
  • Verify that the Background Audio Streaming Agent is only being used to stream the intended audio content and relatedmetadata management.

Expected Result:

  • Ensure that the  audio streaming agent is used only for intended audio streaming and related meta data management.

Android App Test Cases (UI Related Scenarios):

  • Verified that Alignment should be proper.Expected result: Alignment should be proper.
  • Check each and every buttons, images Pixels as per wire frame/page schematic or screen blueprint.Expected result: Dimensions must be same as defied in wireframe.
  • Verify that Proper images size displayed in well manner with Orientation.
  • Verify that all Spell check are correct on Alert, error popup,Error messages etc.
  • Verified that Spinner (Size, Types) should be suitable as per screen.
  • Verify that application Logo should not be blurred and App title should not be misspelled (Means whole logo text should be displayed))
  • Verify that Font size should be consistent.
  • Verify that any kind of text should not be cutting off.
  • Verify that any kind of graphics should not be blurred, Check with different resolution Devices (Like BB have Different resolution for all devices, iPhone 3Gs or iPhone 4)
  • Verify that application must not perform inappropriate actions while thinking or rendering by making user input while the application or handset is busy processing or rendering.There must be no inappropriate reaction by the Application.
  • Verify that On Taping (Single Tap) Application Logo , Application Splash should display.
  • Verify that Application Splash Should not display More than 4 Second
  • Verify that there is visual feedback when response to any action takes more than 3 seconds.
  • Verify that each screen should be visible for the time necessary to comfortably read all its information by moving between screens of an application. Each screen must be visible for the time necessary to comfortably read all its information.
  • Verify that error messages in the Application must be clearly understandable.
  • Verify that error messages must clearly explain to a user the nature of the problem, and indicate what action needs to be taken (where appropriate).
  • Verify that any function selected in the Application should start within 5 seconds.
  • Verify that there must be some visual indication that the function is being performed like
     – prompting for user input;
    – displaying splash screens or progress bars;
    – displaying text such as “Please wait…”, etc
  • Verify that If the screen requires data entry on a specific field, should identify the required fields with a red asterisk and generate a friendly warning if the data is left blank
  • Verify that If the screen contains dates, numeric, currency or other specific data types, ensure that only valid data can be entered.
  • Verify that If the screen contains text boxes that allow data entry, ensure that the width of data entered does not exceed the width of the table field.
  • If the information in the screen is not self-explanatory to the casual user, should provide onscreen instructions to aid the user.
  • If the screen takes more than 5 seconds to display the results/page, it should contain a progress bar so that the user understands the processing is continuing.
     
  • The screen look, feel, and design should match the other screens in your application. (Application should match with the Wireframe or design document provided).
     
  • If the screens contain abbreviations (e.g. Nbr for number, Amt for amount, etc), the abbreviations should be consistent for all screens in the application.
     
  • If the screen allows changing of data without saving, it should prompt users to save if they move to another record or screen.
  • If a person deletes an item, it is a good idea to confirm the delete. User should be prompted with confirmation alert.
     
  • If the user interface uses combo boxes (drop down lists), be sure to include type ahead (if there are hundreds of items in a list, users should be able to skip to the first item that begins with that letter when they type in the first letter).
     
  • Ensure the test cases look for grammar or spelling errors.
     
  • If the application lists information in table format and the data in the table extend past one page, the scrolling should scroll the data but leave the table headers intact.
     
  • If fatal errors occur as users use your application, ensure that the application writes those errors to a log file, event viewer, or a database table for later review. Log the routine the error was in, the person logged on, and the date/time of the error.
     
  • Ensure that error messages are informative, grammatically correct, and not condescending.
     
  • If the application allows short cut keys for copy/paste etc, should test each and every short cuts
     
  • Do not show menu items that are not available for the context users are currently in.
  • Use a style guide to document what choices are available for dialog boxes. Application should not have Save/Cancel dialog on one screen and an OK/Cancel on another. This is inconsistent.
  • Ensure that the screen font family matches from screen to screen. Mismatching fonts within the same sentence and overuse of different fonts is not allowed.
     
  • Ensure that the screen font sizes match from screen to screen. A good user interface will have an accompanying style guide that explicitly defines the font type and size for headers, body text, footers, etc.
  • Ensure that screens do not use different color sets as to cause an inconsistent.style guide should define header colors, body background colors,screen background color, footer colors, etc.
  • Ensure that icons are consistent throughout your application by using a common icon set. For example, a BACK link that contains an icon next to it should not have a different icon on one screen versus another. Avoid free clip-art icons.
  • Ensure that narrative text appears at the same location on the screen on all screens.
  • Ensure that narrative text, error messages and other instructions are presented in laymen’s terms but are brief and to-the-point.
  • If your application has links on the screen (e.g. Save as Spreadsheet, Export, Print, Email, etc.), ensure that the links have consistent spacing between them and other links, that the links appear in the same order from screen to screen, and that the color of the links are consistent.
  • If your application has menu items, ensure that menu items that are not applicable for the specific screen are disabled and the order in which each menu item appears is consistent from screen to screen.
     
  • If your application has buttons (e.g. Submit, OK, Cancel, etc), ensure that the buttons appear in a consistent order from screen to screen (e.g. Submit then Cancel).
  • Tabbing will go onto the next field on the screen

Test cases for android app testing:

Memory Related Scenarios:

1. Fill up the Full phone memory with other files and data, and then try to install the APP on the phone.

Expected Result: The APP should not get installed on the phone and the user should be shown a native warning from the phone OS.

2. Fill up the memory with files and data and leave exactly the same amount of memory required for the installation of the APP.

Expected Result: APP should get installed on the phone, but as you launch the APP the phone should refuse as it doesn’t have even 1 KB of extra space that the APP might require to cache some data.

3. Leave only a small amount (5-7 KB) of space for the app to run. While you are in the app and continuously making server calls this memory will also get filled up.

Expected Result: The app should give a warning stating low memory.

Note: Checking point number 3: Ensure that there is no memory card in the phone. You can fill up the memory using Image files. You can also re size the images to so that 5-7 KB of memory is left out.

Some general Scenarios:

Application start/stop behavior-

1. Start the application by selecting the icon or following the steps outlined in the submission statement. Navigate to the Task Manager and check that the application appears there.

Expected Result: The app should be appearing in task manager.

2. Close the application from within the application UI and then return to the Task Manager. Navigate to the Task Manager and check that the application appears there.

Expected Result: The application must no longer be running and must no longer appear in the task manager.

3. An application which must run in the background does not need to appear in the Task Manager or present a UI.

Note: Developer justifies/Provide this behavior during submission.

Application credentials:

1. With the application running, check the name of the application displayed on the phone. The application must display the same name on the phone as stated during submission.

Expected Result:  The application must display the same name on the phone as stated during submission.

No disruption to text messages:

1. With the application installed and running, send a text message to the test device.

Expected Result:  The incoming text message must be notified to the user as per their alert settings.

2. Read the text message on the test device and choose to reply. Send the reply.

Expected Result: The reply must be received at the second device.

3. From the standby screen on the test device, navigate to the “new text message” option and create a new message. Send the message to the second device.

Expected Result: The message must be received at the second device.

Auto-start behavior:

1. With the application running, find the settings for the application — either within the application itself or from the settings option on the device.

Expected Result: There must be an option which allows the user to enable/disable auto-start functionality.

Note: Depends upon application.

2. Ensure that the setting for auto-start behavior is disabled, and restart the device.

Expected Result: The application must not start on device boot.