Your best option would be to use some sort of source control that has your master set to an instance of the project with no logs in it (in fact I would use the source control ignore to ignore anything log related), then after a test run, just do a revert / cleanup.
We use git, and this is what our .gitignore looks like:
*.bak
*.tcCfgExtender
*.tcLS*
Visualizer/
Log/
*.tcax.tlb
We also save all of the logs during run time outside of the project folder and in a shared log folder. Doing all of these ensure that during test execution (not development) you have a clean environment.
