Are memory leak identification and code profiling the developer's or tester's responsibility?
I am new to memory leaks and memory profiling. Kindly can anyone help me out in finding the answers of the below mentioned questions When to check a memory leak, during coding phase or testing phase? Who is responsible for identification of memory leaks, Developer or Tester? What is the best time to identify a memory leak? Who is responsible to run a memory profiler like ANTS (Developer or tester) ?
Laycee last edited by
It's best to look for and identify all issues as early as possible. The QAs can pick this stuff up, but by then in a sense it's too late. You should (as a developer) look to identify and mitigate such issues as early as possible and design for them, rather than patch post-development. It's an oft-stated maxim that to fix each bug/issue in a successive stage of development costs 10x what it does in the earlier stage (different figures are quoted sometimes but the magnitude remains the same), and as such resolving or avoiding issues as early as possible is the most desirable (cost-effective) outcome.