Depends what you'd be testing. This is where you ask a LOT of clarifying questions on what it is they want you to detect a memory leak. Like: "what aspect of the program should I focus on?" "does it do alot of memalloc's object allocation, and the like" "what happens with the mem leak?" Ultimately you could write a test program that runs the target app for a LONG time, or run it in a forever loop, etc, and look for it to eventually crash.