Timeline for Are memory leak identification and code profiling the developer's or tester's responsibility?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2013 at 18:28 | comment | added | Sam Woods | I agree, this is typically the job of the developer, however it sometimes is directed by me due to some performance/stress testing that I have been doing and noticed memory spikes or memory leaks. | |
| May 28, 2013 at 14:21 | comment | added | Phil Kirkham | Off topic but the oft-stated maxim might not actually be true - read The Leprechauns of S/w engineering... | |
| May 28, 2013 at 14:01 | history | migrated | from stackoverflow.com (revisions) | ||
| May 28, 2013 at 10:08 | vote | accept | CommunityBot | ||
| May 28, 2013 at 9:43 | comment | added | JHaider | We have a web application(already developed) and we are facing memory leaks issues at client side. we are discussing on how to best implement memory profiler to identify memory leaks at this stage. so at this stage should the QA take it up and identify the issues, and for the long term(later releases) developer will have to look into this during development and QA should only cross verify via Memroy profiler? | |
| May 28, 2013 at 8:56 | history | answered | Brian Agnew | CC BY-SA 3.0 |