Mukesh Chauhan

• Oct 21st, 2005

 

Memory leakage can be identified by doing volume testing.  

Mukesh Chauhan

• Oct 21st, 2005

 

This can be done by doing volume testing i.e. Application tries to retrieve large amount of data that require large temporary buffer area. If the data exceed the buffer area the situation of memory leakage will occur and query will fail without returning any result as sorting didn?t got finished as buffer exceeds the limit.

By Mukesh Chauhan - Bangalore

mchauhan

 Profile Answers by mchauhan 

• Oct 22nd, 2005

 

This can be done by doing volume testing i.e. Application tries to retrieve large amount of data that require large temporary buffer area. If the data exceed the buffer area the situation of memory leakage will occur and query will fail without returning any result as sorting didn?t got finished as buffer exceeds the limit.

By Mukesh Chauhan Bangalore

Rajeeva Reddy

• Oct 26th, 2005

 

how to indentify memory leakages after the build i...

Anandhaprabhu

• Dec 20th, 2005

 

actully we are supposed to do the memory leakages tests,while function testing or api testing.you have to see the memory size before test execution and after test execution by using memory related API functions or MFC functions.

then u can get the thing.

diksha

• Apr 25th, 2007

 

memory leakages are checked with endurance testing

akash singh

• Sep 15th, 2007

 

Soak testing is the best answer for that.


Soak testing is used to find out memeory leakage.

Anshoo_Arora

 Profile Answers by Anshoo_Arora 

• Oct 22nd, 2007

 

Memory Leak is best identified by conducting Soak Test.

A soak test runs for a prolonged duration of time. You will need to find number of Vusers between your results for Client's requirement and the the result you obtain for your Break-Even point of the application. Use this number of Vusers to run the test for a few hours, days, or weeks.

LoadRunner is the application you need to be looking at.