Replies

  • For checking Leaks we have tools provided by Mac which is instrument spotlight  for instrument in your finder which brings up both the Leaks and allocations.

     

     

  • As Iphone is based on Objective C and here we have many memory related issues. As in Objective C garbage collection doesn't happen automatically. All objects and variables initialized in memory need to be deallocated. So for checking Memory allocation and leaks we have tools provided on MAC. This come under instrumentation. If you open this you get Memory allocation and memory leaks both options. We can check memory related aspects using these tools.

    Thanks

    Arvind

  • shwetha can you share the the name of tool for checking memory leaks
  • Performance Tools for iphone app

     

    I've been using instrument tool for finding and fixing the memory leaks 

     

     

    with in Instrument - Leaks .....

  • Thanks :), I'l check it out and get back to you .
  • @ SK:


    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. I have checked this using resizing the images, so believe me it wouldn't be that difficult. :)


    Sk said:

    @ Anand Verma :


    Point number 3 is difficult to check.  I tried a lot to execute that scenario.  :-)

     


    Arvind Verma said:
    what I do for testing memory related issues:
    1. Fill up the phone memory with other files and data, 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 hv even 1 KB of extra space that the APP mite require to cache some data.
    3. Run the App in low memory: 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.

    I hope this will help. I also request others to post how they test low memory scenarios...
  • @ Anand Verma :


    Point number 3 is difficult to check.  I tried a lot to execute that scenario.  :-)

     


    Arvind Verma said:
    what I do for testing memory related issues:
    1. Fill up the phone memory with other files and data, 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 hv even 1 KB of extra space that the APP mite require to cache some data.
    3. Run the App in low memory: 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.

    I hope this will help. I also request others to post how they test low memory scenarios...
  • @Arvind...
    thanks for sharing the scenarios..

    but i think memory testing is something deeper, am not sure; the scenarios u suggested are fine, and i think these scenarios may be fine to some extent...


    Arvind Verma said:
    what I do for testing memory related issues:
    1. Fill up the phone memory with other files and data, 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 hv even 1 KB of extra space that the APP mite require to cache some data.
    3. Run the App in low memory: 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.

    I hope this will help. I also request others to post how they test low memory scenarios...
  • Are you testing android app?
  • what I do for testing memory related issues:
    1. Fill up the phone memory with other files and data, 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 hv even 1 KB of extra space that the APP mite require to cache some data.
    3. Run the App in low memory: 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.

    I hope this will help. I also request others to post how they test low memory scenarios...
This reply was deleted.
    results->result as $result) { ?>
  1. jobtitle;?>
    company;?>(formattedRelativeTime;?>)city;?>, state;?>
    Welcome to Mobile QA Zone, a Next Generation Software Testing Community.Invite your friends to join this community.Write to us to become a featured member.