Test Cases for Android Apps, Memory related and some general scenarios for Android Testing



Test Cases for Android Apps, Memory related and some general scenarios for Android Testing

Following are the Test Cases for Android Apps :-

Scenarios for Memory → 1. Filled the full memory of phone with any data and files and after that try to for Apps installation on phone.

Expected Result will be: Now user should received the native warning from the OS of phone and App should not be able to install on Android

  1. Second Scenarios will be, Just filled the memory with the data and files and then leave exactly same space of required memory for apps installation.
Expected Result: In this scenarios apps will be installed on the Android phone, but as soon as we launch the apps then the phone will refuse it because it will not have only the 1kb of extra space so that app can ache some space of memory.

  1. This time leave the some space around 5 to 8 kb for apps to occupy. While you working with this app and same time you get any call from server then all memory will again filled up.
    Expected Result: Phone will show the warning realated to low memory backup.
    Note: For memory scenario no3, ensure there should not any memory card in that phone. We can filled up the memory with the help of images files. We should re-size the scenarios to secure the 5 to 7kb memory.

Some General Scenarios are Give as below:


Scenarios for the Behavior of Application Start or Stop:

  1. Application need to start with the selection of any icon or the steps outlined as per following submission statement. First required to Navigate the Task Manager and then test that apps appear there or not.
    Expected Result: In the Task Manager, Application should be visible.
  2. From the UI, close the application and then come back to task manager. Now just navigate the task manager and test the appearance of application there.
    Expected Result: Now application should not running and must not be appeared in the task bar.

  1. An Apps which is running the background doesn't required to appear in the task manger or in the present in UI.
    Note: Developers justifies / Provide such behavior during the submission.

Application Credentials related Test scenarios:

  1. During the running application, Confirm the name of apps shown on the phone. The app must show the same name exact it was showing on during the executing the app.
    Expected Result: The application should show the exact same name on the task bar as it was showing in the starting.

Test Scenarios for - No Disruption to text messages:
  1. During the installation and the execution of apps, need to send a text message on the test device.
    Expected Result: According to the alert setting of notified user, message must be notified for incoming text.
  2. Need to read the received text message on the phone and select the reply option.
    Expected Result: Second device should receive the reply.
  3. From screen standby from test device, navigate the 'new text message' option and then generate the new sms. Now send the sms on the new second device.
    Expected Result: Second device should received the Text SMS.

Auto Start Behavior:

  1. During the Running Application, find the setting for the apps – either during application execution itself or from the option of setting on the device.
    Expected Result: One option must be available which allow the user to active or deactivate the auto start functionality.
    Note: Depend upon application.
  2. Ensure that the auto start behavior is deactivate from setting and then restart the device again.
    Expected Result: The apps should not start on the device booting.





    Near Field Communication Support NFC Smart Poster Support













    Use of add-ins
    Cookies in QTP


    Mobile Testing with QTP How to install .ipa files for ipad iphone



    Touch Screen Simulating User Gestures



    MOBILE APPS    QTP TESTING QUESTIONS  MANUAL TESTING  ANDROID APPS


No comments:

Post a Comment

Popular Posts