memory stack confusion (leftovers) when running tests in VBA project

can anybody here tell me how they run tests on their automation distributables? this question is related to the 2 I've asked recently. same project. I have a very small routine, and I'm writing a few different methods to test speed. I will use one of them, however, in order to preserve my sanity and brain power, I always run an app multiple times when it is partially finished so I can see how the coding environment handles all of the transaction requests I am writing within the code. how do you guys do this? because what I've noticed this time around is that if I run a test and break lines in any given area, some of memory that is not destroyed causes all sorts of confusion (which seems to not be patternized or predictable) when re-running the same test on the same app multiple times. what is the solution to this? obviously I don't want to write a bunch of temp code to destroy memory at various points in an app if I want to run in part way though a million times. that would be a very big waste of time.

how do you guys go about this?

So given what you, as a professional of excel applications, have said, what that leaves me with is essentially no answer to the problem is that correct? I mean there is a solution to the problem that I have found and that is to simply close the Excel application and every workbook that's opened when I'm testing obviously when I do that garbage collection has to occur because they sell quits and if any program quits then everything is destroyed by default

Do you know if that's the process people go through and running software applications in any other ide's? I don't know if you have used any other tools but I use many of them including visual studio, visual studio code, eclipse for Java PHP and JavaScript, aptana studio, dreamweaver, PHP storm, pycharm for python, etc....

But all of those development environments are much more sophisticated than office programs and I don't have time to learn everything I just wanted your input as to if it's easy to do this sort of reset process using sophisticated environments like I've just mentioned? Thanks

The reason I just said what I said is because restarting an office application to get rid of all memory junk that's temporarily stored in the system is a really bad way to force a developer to do that job. Any other web environment probably has a built-in method you don't have to restart

well yes, I think there's universal agreement on that one.