Archive for the ‘Test cases’ Category

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.

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.