Posts Tagged ‘test case’

Difference between Sanity and Smoke Testing:

Smoke Testing:

  • When a build is received smoke testing is done to ensure that whether the build is ready or stable for further testing.
  • Smoke testing is a wide approach where all areas of software application are tested without getting into deeper.
  • Test Cases for smoke testing can be manual or automated.
  • A smoke test is basically designed to touch each and every part of an app in a cursory way.
  • Smoke testing is Shallow and wide.
  • Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details.
  • Smoke testing is like General Health Check Up

Sanity Testing:

  • After receiving a software build, with minor changes in code, or functionality, Sanity testing is performed to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected.
  • Sanity testing exercises only the particular component of the entire system.
  • A sanity test is usually unscripted and without test scripts or test cases.
  • Sanity Testing is narrow and deep
  • Sanity testing is to verify whether requirements are met or not, checking all features breadth-first
  • Sanity Testing is like specialized health check up

Test Plan:

It is a high level document in which how to perform testing is described. The Test Plan document is usually prepared by the Test Lead or Test Manager and the focus of the document is to describe what to test, how to test, when to test and who will do what test.

The plan typically contains a detailed understanding of what the eventual workflow will be.

Master test plan: A test plan that typically addresses multiple test levels.

Phase test plan: A test plan that typically addresses one test phase.

Test Plan Template contains following components:

1. Introduction

A brief summary of the product being tested. Outline all the functions at a high level.

  • Overview of This New System
  • Purpose of this Document
  • Objectives of System Test

2. Resource Requirements

  • Hardware– List of hardware requirements
  • Software–List of software requirements: primary and secondary OS
  • Test Tools—List of tools that will be used for testing.
  • Staffing

 3. Responsibilities

List of QA team members and their responsibilities

4.      Scope—

  • In Scope
  • Out Scope

 5. Training

List of training’s required

6. References

List the related documents, with links to them if available, including the following:

  • Project Plan
  • Configuration Management Plan

7.      Features To Be Tested / Test Approach

  • List the features of the software/product to be tested
  • Provide references to the Requirements and/or Design specifications of the features to be tested

8.      Features Not to Be Tested

  • List the features of the software/product which will not be tested.
  • Specify the reasons these features won’t be tested.

9.      Test Deliverables—

  • List of the test cases/matrices or their location
  • List of the features to be automated

10.  Approach

  • Mention the overall approach to testing.
  • Specify the testing levels [if it’s a Master Test Plan], the testing types, and the testing methods [Manual/Automated; White Box/Black Box/Gray Box

11.Dependencies

  • Personnel Dependencies
  • Software Dependencies
  • Hardware Dependencies
  • Test Data & Database

12.Test Environment—

  • Specify the properties of test environment: hardware, software, network etc.
  • List any testing or related tools.

13.APPROVALS

  • Specify the names and titles of all persons who must approve this plan.
  • Provide space for signatures and dates.

14.Risks and Risk management plans—

  • List the risks that have been identified.
  • Specify the mitigation plan and the contingency plan for each risk.

15.Test Criteria—

  • Entry Criteria
  • Exit Criteria
  • Suspension Criteria

16.Estimate

  • Size
  • Effort
  • Schedule

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.

Difference between Test case and Test scenario:

  • Test case consist of set of input values, execution precondition, excepted Results and executed post condition, developed to cover certain test Condition. While Test scenario is nothing but test procedure.
  • A Test Scenarios have one to many relation with Test case, Means A scenario have multiple test case. Every time we have write test cases for test scenario. So while starting testing first prepare test scenarios then create different-2 test cases for each scenario.
  • Test cases are derived (or written) from test scenario. The scenarios are derived from use cases.
  • Test Scenario represents a series of actions that are associated together. While test Case represents a single (low level) action by the user.
  • Scenario is thread of operations where as Test cases are set of input and output given to the System.

For example:

Checking the functionality of Login button is Test scenario and
Test Cases for this Test Scenario are:
1. Click the button without entering user name and password.
2. Click the button only entering User name.
3. Click the button while entering wrong user name and wrong password.
Etc…

In short,

Test Scenario is ‘What to be tested’ and Test Case is ‘How to be tested’.

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.