Test cases for Windows app / Windows Phone Test Checklist-1

Posted: October 3, 2012 in Automation, Manual Testing, Test cases
Tags: , , , , ,

Windows Phone Test Checklist-I

Test cases for Windows app:

1. Test Name:  Verify Application Tile Images

Test Description:

  • View the Application list.
  •  Verify that the small mobile app tile image is representative of the application.
  •  From the Application list, tap and hold the small mobile app tile of your application and select ‘pin to start’.
  • Verify that the large mobile tile image on the Start screen is representative of the application.

Expected Result:

  • Ensure that the small app tile image should be representative of the application.
  • Ensure that the large app tile image on the start screen should be representative of the application.

2.  Test Name:  Application Closure

Test Description:

  •  Launch your application.
  • Navigate throughout the application, and then close the application through device’s “back” button.

Expected Result:

  • Verify that there shouldn’t be any unexpected behavior during the closing process.

3. Test Name:  Application Responsiveness

Test Description:

  •  Launch your application.
  •  Thoroughly test the application features and functionality.
  •  Verify that the application does not become unresponsive for more than three seconds.
  •  Verify that a progress indicator is displayed if the application performs an operation that causes the device to appear to be unresponsive for more than three seconds.
  • If a progress indicator is displayed, verify that the application provides the user with an option to cancel the operation being performed.

Expected Result:

  • Ensure that the application does not become unresponsive for more than three seconds.
  • Ensure that a progress indicator should be displayed if the application performs an operation that causes the device to appear to be unresponsive for more than three seconds.
  • Ensure that the application provides an option to the user to cancel the operation being performed.

4. Test Name:  Application Responsiveness After Being Closed

Test Description:

  •  Launch your application.
  • Close the application using the Back button, or by selecting the Exit function from the application menu.
  •  Launch your application again.
  • Verify that the application launches normally within 5 seconds, and is responsive within 20 seconds of launching.

Expected Result:

  • Ensure that the application launches normally within 5 seconds, and is responsive within 20 seconds of launching.

5. Test Name:  Application Responsiveness After Being Deactivated

Test Description:

  • Launch your application.
  •  De-activate the app. This can be achieved by pressing the “Start” button or by launching another app. (By deactivation we are not closing the app’s process but are merely putting the app in the background.)
  • Verify that the application launches normally within 5 seconds, and is responsive within 20 seconds of launching.
  • If your application includes pause functionality, pause the application.
  • Launch your application again.
  • Verify that the application launches normally within 5 seconds, and is responsive within 20 seconds of launching.

Expected Result:

  • Ensure that the application launches normally within 5 seconds, and is responsive within 20 seconds of launching.
  • Ensure that the application should be paused successfully in de-activating state.

 6. Test Name:  Back Button: Previous Pages

Test Description:

  •  Launch your application.
  •  Navigate through the application.
  •  Press the Back button.
  • Verify that the application closes the screen that is in focus and returns you to a previous page within the back stack.

Expected Result

  • Ensure that the application is redirected to the previous page of the application.

 7. Test Name:  Back Button: First Screen

Test Description:

  • Launch your application.
  • Press the Back button.
  • Verify that either the application closes without error, or allows the user to confirm closing the application with a menu or dialog.

Expected Result:

  • Ensure that the application Exits Successfully from the initial page or a Menu/Dialog box should be provided to the user for the confirmation of the exit.

8. Test Name:  Back Button: Context Menus and Dialogs

Test Description:

  • Launch your application.
  •  Navigate through the application.
  • Display a context menu or dialogs.
  • Tap the Back button.
  •  Verify that the context menu or dialog closes and returns you to the screen where the context menu or dialog was opened.

Expected Result:

  • Ensure that the context menu/dialog is closed & user is redirected back to the page where the context menu/dialog was opened.

9. Test Name:  Back Button: Games

Test Description:

  •  Launch your application.
  •  Begin playing the game.
  •  Tap the Back button.
  •  Verify that the game pauses.

Expected Result:

  • Ensure that games should be paused immediately with a menu/message on pressing back button

10.Test Name:  Trial Applications

Test Description:

  • Launch the trial version of your application.
  • Launch the full version of your application.
  • Compare the performance of the trial and full versions of your application.
  • Verify that the performance of the trial version of your application meets the performance requirements mentioned in test cases 1-9.

Expected Result:

  • Ensure that the performance of the trial version of your application meets the performance requirements mentioned in test cases 1-9

 11.Test Name:  Verify that Application doesn’t affect Phone Calls

Test Description:

  • Ensure that the phone has a valid cellular connection.
  • Launch your application.Receive an incoming phone call.
  • Verify that the quality of the phone call is not negatively impacted by sounds or vibrations in your application.
  • End the phone call.
  • Verify that the application returns to the foreground and resumes.
  • De-activate the application by tapping the Start button.
  • Verify that you can successfully place a phone call.

Expected Result:

  • Ensure that the quality of the phone call is not negatively impacted by sounds or vibrations of the test application.
  • Ensure that the application returns to the foreground and resumes after the phone call.
  • Ensure that User can successfully place a phone call when a test application is de-activated or in a pause state in a back ground.

 12.Test Name:  Verify that Application doesn’t affect SMS and MMS Messaging

Test Description:

  • Ensure that the phone has a valid cellular connection.
  • Ensure that the phone is not in Airplane mode by viewing the phone Settings page.
  • Launch your application. Deactivate the application by tapping the Start button.
  • Verify that a SMS or MMS message can be sent to another phone.
  • Verify that notifications regarding the SMS or MMS messages are displayed on the phone either from within the application, or within 5 seconds after the application is closed

Expected Result:

  • Ensure that a SMS or MMS message can be sent to another phone.
  • Verify that notifications regarding the SMS or MMS messages are displayed on the phone either from within the application, or within 5 seconds after the application is De-activated.

 13.Test Name: Verify Application Responsiveness With Incoming Phone Calls and Messages

Test Description:

  • Ensure that the phone has a valid cellular connection.
  • Ensure that the phone is not in Airplane mode by viewing the phone Settings page.
  • Receive an incoming phone call, SMS message or MMS message.
  • Verify that the application does not stop responding or close unexpectedly when the notification is received.
  • After verifying the above step, tap on the message notification or receive the incoming phone call.
  • If a message was received, verify that User can return to the application by pressing the Back button.

Expected Result:

  • Ensure that the application does not stop responding or close unexpectedly when the notification is received.
  • If a message was received, Ensure that User can return to the application by pressing the Back button.

14.Test Name: Language Validation

Test Description:

  • Review the product description of the application and verify that it is localized to the target language.
  • Launch your application.
  • Verify that the UI text of the application is localized to the target language.

Expected Result:

  • Ensure that the UI text of the application is localized to the target language.

15.Test Name: Verify Application with colors and Themes of the device

Test Description:

  • Navigate to the Settings page in the app list.
  • Tap theme and change Background to ‘Dark’.
  • Launch your application.
  • Verify that the text and visual elements of the application are visible and legible.
  • Navigate back to the theme page under Settings, and change Background to ‘Light’.
  • Launch your application.
  • Verify that the text and visual elements of the application are visible and legible.

Expected Result:

  • Ensure that the text and visual elements of the application are visible and legible in the dark background.
  • Ensure that the text and visual elements of the application are visible and legible in the Light background.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s