Archive for the ‘Manual Testing’ Category

Cookie:
Cookie is small bit of information stored in text file on user’s hard drive by web server. This information is later used by web browser to retrieve information from that machine. Generally cookie contains personalized user data or information that is used to communicate between different web pages.

Why Cookies are used?
Cookies are nothing but the user’s identity and used to track where the user navigated throughout the web site pages. The communication between web browser and web server is stateless.

For example if you are accessing domain http://www.example.com/1.html then web browser will simply query to example.com web server for the page 1.html. Next time if you type page as http://www.example.com/2.html then new request is send to example.com web server for sending 2.html page and web server don’t know anything about to whom the previous page 1.html served.

What if you want the previous history of this user communication with the web server? You need to maintain the user state and interaction between web browser and web server somewhere. This is where cookie comes into picture. Cookies serve the purpose of maintaining the user interactions with web server.

Cookie Detective Work

How can you tell if the Web system you are testing uses cookies? Simply read the website design documents, functional specs, etc. – if such documents are available. A more direct approach, especially useful in the likely absence of such documentation, is:

Find the folder on your PC where cookies are stored.

Delete all of the existing cookies. In Internet Explorer, the cache files are stored in the same folder as the cookies. Clearing the browser cache in IE can make finding the cookies easier, but isn’t strictly necessary.

Set your browser’s cookie options to “prompt me” In Internet Explorer, choose Tools | Internet Options, navigate to the Security tab, click Custom Level and select the “Prompt” radio button under “Allow cookies that are stored on your computer”. Also do the same under “Allow per –session cookies (not stored).”

Navigate through all of the major features and functions on the site to see where cookies are employed.

How do you know where cookies are used? Whenever the site attempts to record state information in a cookie on your PC, you will be prompted with a message. Internet Explorer’s prompt looks like this:

Every time this dialog appears, record the cookie details and what action(s) cause the cookie to be created or modified. Then, click Yes to accept the cookie. Personally, I find it easier to accept the cookie, open the cookie file and copy/paste the cookie details into a “cookie log” with my observations for later analysis. Save this data, including the cookie names and contents, creating a log of cookie activity correlated to your activities on the website. A word of warning: some sites are highly active with cookies, setting or modifying them on every page you visit. Creating the cookie log on these types of sites will be time consuming and drive you to a certain level of insanity. Getting as much info as possible in advance about cookie activity from the developers is usually your best bet.

How cookies work?
The HTTP protocol used to exchange information files on the web is used to maintain the cookies. There are two types of HTTP protocol. Stateless HTTP and Stateful HTTP protocol. Stateless HTTP protocol does not keep any record of previously accessed web page history. While State full HTTP protocol do keep some history of previous web browser and web server interactions and this protocol is used by cookies to maintain the user interactions.

Whenever user visits the site or page that is using cookie, small code inside that HTML page (Generally a call to some language script to write the cookie like cookies in JAVAScript, PHP, Perl) writes a text file on users machine called cookie.

Here is one example of the code that is used to write cookie and can be placed inside any HTML page:

Set-Cookie: NAME=VALUE; expires=DATE; path=PATH; domain=DOMAIN_NAME;

When user visits the same page or domain later time this cookie is read from disk and used to identify the second visit of the same user on that domain. Expiration time is set while writing the cookie. This time is decided by the application that is going to use the cookie.

Generally two types of cookies are written on user machine.

1) Session cookies: This cookie is active till the browser that invoked the cookie is open. When we close the browser this session cookie gets deleted. Some time session of say 20 minutes can be set to expire the cookie.
2) Persistent cookies: The cookies that are written permanently on user machine and lasts for months or years.

Where cookies are stored?
When any web page application writes cookie it get saved in a text file on user hard disk drive. The path where the cookies get stored depends on the browser. Different browsers store cookie in different paths. E.g. Internet explorer store cookies on path “C:\Documents and Settings\Default User\Cookies”
Here the “Default User” can be replaced by the current user you logged in as. Like “Administrator”, or user name like “Vijay” etc.
The cookie path can be easily found by navigating through the browser options. In Mozilla Firefox browser you can even see the cookies in browser options itself. Open the Mozila browser, click on Tools->Options->Privacy and then “Show cookies” button.

 

How cookies are stored?
Lets take example of cookie written by rediff.com on Mozilla Firefox browser:
On Mozilla Firefox browser when you open the page rediff.com or login to your rediffmail account, a cookie will get written on your Hard disk. To view this cookie simply click on “Show cookies” button mentioned on above path. Click on Rediff.com site under this cookie list. You can see different cookies written by rediff domain with different names.

Site: Rediff.com Cookie name: RMID
Name: RMID (Name of the cookie)
Content: 1d11c8ec44bf49e0… (Encrypted content)
Domain: .rediff.com

Path: / (Any path after the domain name)
Send For: Any type of connection
Expires: Thursday, December 31, 2020 11:59:59 PM

Since per-session cookies aren’t written to the hard drive, examining the cookie content can be done only through the actual Netscape prompt.

Cookies text file looks like this:

What’s Inside a Cookie?

.amazon.com is the domain this cookie is valid for.

TRUE is a flag indicating whether or not all machines in the domain can access the cookie.

/ is the path the cookie is valid for.

FALSE is a secure flag indicating whether or not a secure (encrypted) connection is needed to access the cookie.

994320128 is the UNIX expiration time of the cookie.

session-id is the name of the variable stored by this cookie.

102-7224116-8052958 is the value of this variable.

Applications where cookies can be used:

1) To implement shopping cart:
Cookies are used for maintaining online ordering system. Cookies remember what user wants to buy. What if user adds some products in their shopping cart and if due to some reason user don’t want to buy those products this time and closes the browser window? When next time same user visits the purchase page he can see all the products he added in shopping cart in his last visit.

2) Personalized sites:
When user visits certain pages they are asked which pages they don’t want to visit or display. User options are get stored in cookie and till the user is online, those pages are not shown to him.

3) User tracking:
To track number of unique visitors online at particular time.

4) Marketing:
Some companies use cookies to display advertisements on user machines. Cookies control these advertisements. When and which advertisement should be shown? What is the interest of the user? Which keywords he searches on the site? All these things can be maintained using cookies.

 5) User sessions:
Cookies can track user sessions to particular domain using user ID and password.

DisAdvantages of cookies:

1) Too many Cookies:
If you are writing too many cookies on every page navigation and if user has turned on option to warn before writing cookie, this could turn away user from your site.

2) Security issues:
Some times users personal information is stored in cookies and if someone hack the cookie then hacker can get access to your personal information. Even corrupted cookies can be read by different domains and lead to security issues.

3) Sensitive information:
Some sites may write and store your sensitive information in cookies, which should not be allowed due to privacy concerns.

How do I enable cookie support in my browser?

Cookies are enabled by default in most browsers, however if you think your browser has cookie support disabled then please follow these instructions:-

For Internet Explorer:
1. Left Click the ‘Tools’ menu.
2. Left Click ‘Internet Options’.
3. Left Click ‘Privacy’ tab.
4. Left Click the ‘Sites’ button.
5. Type http://www.weighin.net into the top box.
6. Left Click the ‘Allow’ button.
7. Left Click the ‘Ok’ button.
8. Left Click the ‘Ok’ button.

To enable cookies in Internet Explorer 7 or 8:

  1. Click Start > Control Panel. (With Windows XP Classic View, click the Windows Start button > Settings > Control Panel).
  2. Double-click the Internet Options icon.
  3. Select the Privacy tab.
  4. Click Advanced.
  5. Select “Override automatic cookie handling” under the “Cookies” section in the Advanced Privacy Settings window.
  6. Select the “Accept” or “Prompt” option under “First-party Cookies.”
  7. Select the “Accept” or “Prompt” option under “Third-party Cookies.” (If you select the “Prompt” option, you’ll be asked for approval every time a website attempts to send you a cookie.)
  8. In the Internet Options window, click OK to exit.

For Mozilla Firefox:

1. Left Click the ‘Tools’ menu.
2. Left Click ‘Options’.
3. Left Click ‘Privacy’ tab.
4. Left Click ‘Exceptions’ button.
5. Type http://www.weighin.net into the top box.
6. Left Click the ‘Allow’ button.
7. Left Click the ‘Close’ button.
8. Left Click the ‘Ok’ button.

To enable cookies in Chrome for Windows:

  1. Click the Tools menu.
  2. Select Options.
  3. Click the Under the Hood tab.
  4. Click Content settings in the “Privacy” section.
  5. Select Allow local data to be set to allow both first-party and third-party cookies. If you only want to accept first-party cookies, check the box next to “Block all third-party cookies without exception.”

Important Scenarios to test cookie testing for websites:

Test cases: 

1) As a Cookie privacy policy make sure from your design documents that no personal or sensitive data is stored in the cookie.

2) If you have no option than saving sensitive data in cookie make sure data stored in cookie is stored in encrypted format.

3) Make sure that there is no overuse of cookies on your site under test. Overuse of cookies will annoy users if browser is prompting for cookies more often and this could result in loss of site traffic and eventually loss of business.

4) Disable the cookies from your browser settings: If you are using cookies on your site, your sites major functionality will not work by disabling the cookies. Then try to access the web site under test. Navigate through the site. See if appropriate messages are displayed to user like “For smooth functioning of this site make sure that cookies are enabled on your browser”. There should not be any page crash due to disabling the cookies. (Please make sure that you close all browsers, delete all previously written cookies before performing this test)

5) Accepts/Reject some cookies: The best way to check web site functionality is, not to accept all cookies. If you are writing 10 cookies in your web application then randomly accept some cookies say accept 5 and reject 5 cookies. For executing this test case you can set browser options to prompt whenever cookie is being written to disk. On this prompt window you can either accept or reject cookie. Try to access major functionality of web site. See if pages are getting crashed or data is getting corrupted.

6) Delete cookie: Allow site to write the cookies and then close all browsers and manually delete all cookies for web site under test. Access the web pages and check the behavior of the pages.

7) Corrupt the cookies: Corrupting cookie is easy. You know where cookies are stored. Manually edit the cookie in notepad and change the parameters to some vague values. Like alter the cookie content, Name of the cookie or expiry date of the cookie and see the site functionality. In some cases corrupted cookies allow to read the data inside it for any other domain. This should not happen in case of your web site cookies. Note that the cookies written by one domain say rediff.com can’t be accessed by other domain say yahoo.com unless and until the cookies are corrupted and someone trying to hack the cookie data.

8 ) Checking the deletion of cookies from your web application page: Some times cookie written by domain say rediff.com may be deleted by same domain but by different page under that domain. This is the general case if you are testing some ‘action tracking’ web portal. Action tracking or purchase tracking pixel is placed on the action web page and when any action or purchase occurs by user the cookie written on disk get deleted to avoid multiple action logging from same cookie. Check if reaching to your action or purchase page deletes the cookie properly and no more invalid actions or purchase get logged from same user.

9) Cookie Testing on Multiple browsers: This is the important case to check if your web application page is writing the cookies properly on different browsers as intended and site works properly using these cookies. You can test your web application on Major used browsers like Internet explorer (Various versions), Mozilla Firefox, Netscape, Opera etc.

10) If your web application is using cookies to maintain the logging state of any user then log in to your web application using some username and password. In many cases you can see the logged in user ID parameter directly in browser address bar. Change this parameter to different value says if previous user ID is 100 then make it 101 and press enter. The proper access message should be displayed to user and user should not be able to see other users account.

Test Cases for Security Testing:                                                                                                                                               

1. Try to directly access bookmarked web page without login to the system.

2. Verify that system should restrict you to download the file without sign in on the system.

3. Verify that previous accessed pages should not accessible after log out i.e. Sign out and then press the Back button to access the page accessed before.

4. Check the valid and invalid passwords, password rules say cannot be less than 6 characters, user id and password cannot be the same etc.

5. Verified that important i.e. sensitive information such as passwords, ID numbers, credit card numbers, etc should not get displayed in the input box when typing. They should be encrypted and in asterix format.

6 .Check Is bookmarking disabled on secure pages? Bookmarking Should be disabled on secure pages.

7. Check Is Right Click, View, Source disabled? Source code should not be visible to user.

8. Is there an alternative way to access secure pages for browsers under version 3.0, since SSL is not compatible with those browsers?

9. Check does your server lock out an individual who has tried to access your site multiple times with invalid login/password information?

10. Verify the timeout condition, after timeout user should not able to navigate through the site.

11. Check Are you prevented from doing direct searches by editing content in the URL?

12. Verify that relevant information should be written to the log files and that information should be traceable.

13. In SSL verify that the encryption is done correctly and check the integrity of the information.

14. Verify that restricted page should not be accessible by user after session time out.

15. ID / password authentication, the same account on different machines cannot log on at the same time. So at a time only one user can login to the system with a user id.

16. ID / password authentication methods entered the wrong password several times and check if the account gets locked.

17. Add or modify important information (passwords, ID numbers, credit card number, etc.). Check if it gets reflected immediately or caching the old values.

18. Verify that Error Message does not contain malicious info so that hacker will use this information to hack web site.

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.

Test Cases For Games Apps:

 

Mobile Game Testing
Check for background music
and sound effects
ON/OFF sound & background music
Receive the call and check
Verify if sound effects are in sync with action
ON/OFF device sound(native sound) and check
Check for vibration effect if present
User Interface Check in Landscape/Portrait mode
Check for animation, movement of character, graphics, Zoom In/Out (all gestures) etc
There should not be any clipping (cutted background)
Test whether one object overlaps with another
Verify if loading indicator is displayed wherever required
Character should not move out of the screen/specified area
Test for enable and disable images/icons/buttons etc
Check for screen title
Check for message title, message description, label (should be appropriate)
Check scrolling
Font displayed (color, size etc)
Check other objects too (ex -if its a car race- you need to look at road, people, other objects like buildings etc)
Performance Check the loading time of a game
Make sure that any action is not taking considerable time, game flow should be fast
Score score calculation
Verify leaderboards General/All time/Weekly/local etc
Check the score registration functionality
Check the format (whether, comma is required in score etc ideally if customer is a foriegner coma should be in millions not in thousands )
Check for level completion syncs with the score
Time Out Check for time out
Do the actions when time-out yet to happen
Multitasking Switch b/w different apps and play game , check for sound, score, UI, time-out etc
Pause Check if game is paused when call received or multitasking or sleep mode
Save Settings Turnoff and ON device, check if settings are saved
Log out /On , check same
User should not loose his game in above conditions
User profile Put a all types of images in Player profile and check
Put special character, numbers,space in username and check
Password should be in masked
Chat feature Check the profile images
max limit of chat description
Enter empty string, special character and check
For a opponent , there should be a notification that he has received a message
Functionality Check game area, game logic
play till last level
get the cheat codes from development team and check all the levels
Check for the features that will be unlocked level-wise
Check for bonus score
Check the score hike when level gets increased
Check for multi-tap action (example in a car race we hold accelerator and left/right turn button simultaneously)
Menu options
Different game modes/location
Help & About Screen Should be in easily understandable format
free from spelling mistakes
URL should be hyperlinked (depends)
Multiplayer game Session expiry check
login/log out
Registration (Sign Up)
Verify account (receive verification mail)
login with registered but not verified account (without clicking verification link)
Forgot password checks (many cases here)
Game flow
Check for WIN/lost/Draw
Check user statistics graph
Challenge/Decline challenge/receive challenge
Check for forfeit
Check when player 2’s turn is on Player 1 is not able to do actions (should not be able to forfeit also)
Check for pass turn
Check for time-out (for one player)
Check the score for both the players till game ends
Memory leak Check the game when device memory is low
Network (n/w) check N/w messages if n/w is not present
check if what happens when n/w not present and user plays a move (whether score submitted for that move etc)
Check for localization Should be Support of different languages
Check for time format Change the device time , format etc
Size User wont like if your game takes lot of device space, so keep one eye on game file size
Device , OS Check in supported screen sizes and os versions (basicaly depend upon Client requirement)
Depends on platform Sometime we need to check as per OS guidliness as well. For ex in Wp7 we need to check in 2 background (light/dark).
Check Share options Post score via mail/FB/Twitter
Check the posted/sent messages in FB/Twitter/Mail. Check links are hyperlinked and application icon is displayed in
the post (depends)
If twitter integration is a manual ( custom UI developed by developer), check what happens when u enter more than
140 chars (as twitter limit is 140)
Music playing during app
launche
If music player running and we start installing any game app, music player should pauses without prompting for the user permission.
Steps for checking this:
1. Play a music file.
2. Launch the application.
3. Verify that while the application loads, it does not pause, resume or stop the actively playing music.
Interuption If app(game) is in running mode, then Check the behaviour of interuption like like Bluetooth, Infra red and CALL/SMS/MMS.
Upgrade the game
/ Battery effect
Upgrade of Games to the latest version and while migration all data should persist [ score, user profile etc ]
What if Battery goes down/switched of the cell while playing, Wheter the score wil get saved?

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.
Test cases/Scenarios For Web Site Cookie Testing:

1) Verified that on Sensitive and Personal data is stored In cookies.

2)Verified that if any personal data is stored in cookies it should be stored in encrypted format.

3) Verified  that there is no overuse of cookies on your site under test. Overuse of cookies will annoy users if browser is prompting for cookies more often and this could result in loss of site traffic and eventually loss of business.

4) Verified that If you are using cookies on your site, your sites major functionality will not work by disabling the cookies.  There should not be any page crash due to disabling the cookies. (Please make sure that you close all browsers, delete all previously written cookies before performing this test)

5) Verified that on Disabling the cookies appropriate messages Should be displayed to user like “For smooth functioning of this site make sure that cookies are enabled on your browser” while navigate through Site.

6) Verified that there should not be any page crash due to disabling the cookies.

Note:Please make sure that you close all browsers, delete all previously written cookies before performing this test)

7) Verified that your web application page is writing the cookies properly on different browsers as intended and site works properly using these cookies. You can test your web application on Major used browsers like Internet explorer (Various versions), Mozilla Firefox, Netscape, Opera etc.

8) Verified that cookies written by one domain can not accessed by another browser.

9) Verified that Corrupted cookies can not be accessible by other domain.

Note: Corrupting cookie is easy. You know where cookies are stored. Manually edit the cookie in notepad and change the parameters to some vague values. Like alter the cookie content, Name of the cookie or expiry date of the cookie and see the site functionality. In some cases corrupted cookies allow to read the data inside it for any other domain. This should not happen in case of your web site cookies.

10)  Accepts/Reject some cookies: The best way to check web site functionality is, not to accept all cookies. If you are writing 10 cookies in your web application then randomly accept some cookies say accept 5 and reject 5 cookies. For executing this test case you can set browser options to prompt whenever cookie is being written to disk. On this prompt window you can either accept or reject cookie. Try to access major functionality of web site. See if pages are getting crashed or data is getting corrupted.

11) Delete cookie: Allow site to write the cookies and then close all browsers and manually delete all cookies for web site under test. Access the web pages and check the behavior of the pages.

12) Checking the deletion of cookies from your web application page: Some times cookie written by domain say rediff.com may be deleted by same domain but by different page under that domain. This is the general case if you are testing some ‘action tracking’ web portal. Action tracking or purchase tracking pixel is placed on the action web page and when any action or purchase occurs by user the cookie written on disk get deleted to avoid multiple action logging from same cookie. Check if reaching to your action or purchase page deletes the cookie properly and no more invalid actions or purchase get logged from same user.

13) If your web application is using cookies to maintain the logging state of any user then log in to your web application using some username and password. In many cases you can see the logged in user ID parameter directly in browser address bar. Change this parameter to different value says if previous user ID is 456 then make it 452 and press enter. The proper access message should be displayed to user and user should not be able to see other users account.

14) In case of online shopping portal testing ,Verified that when user reach to final order summary page,cookie of previous page  i.e. shopping cart page should be deleted properly.

15) Verified that credit card number should not be stored in cookies not even in encrypted form.