If a script unit file is not included in TestComplete as part of a project, TestComplete has no native built in awareness of it so there is no native function in TestComplete to "clean up". You COULD create a feature request for this... however, I am not a fan of this because of the concept of "shared" code units. There may be code units in a directory path for a TestComplete project that are not part of the current project but MAY be shared with another project. To "clean up" unused code units would, potentially, break this.
The best thing I can tell you to do is to go ahead and proceed with the commit to SVN but, before you do so, exclude any files that don't explicitly show up in the project... You would need to have the project open on screen at the same time. Once you've done that, close TestComplete, delete ALL script code files from the Script directory of your project, and then download the files again from SVN. When you restart TestComplete and re-open that project, you should have all your script files back and your project path won't have any "useless" stuff in it any more.
Champion Level 3What we do towards the end of a project is create a new TestComplete project and start out with just the core tests. We run those and add anything that's missing as we go. This gives us a clean project and we then add that one into svn and go forward with the smaller one. The old one stays in svn in case we want to refer back to something.
