Using with Coded UI test

Apr 21, 2015 at 7:44 AM
I tryed using this cool library together with Coded UI tests.
But it seems that Coded UI tests injects some "memory leaks" because of automation..

Are there any tricks for getting that to work?
May 16, 2015 at 12:41 PM
It depends on how you test. If the leak is constant you can retrieve the memory stats and subtract from that the coded UI memory overhead per iteration. If after n iterations a positive difference shows up you have found a real memory leak. In any case you need to completely understand how your leak builds up. Perhaps you can even solve it.