Forum Discussion
You could rename it instead of deleting.
Or remove it instead of deleting, so its out of the project but still exists as a file.
Then just operate as normal.
If you don't get a runtime error then after a while you'll know that nothing references it and it can be deleted.
If you do get the runtime error, then you know you need to restore it because it's still used.
I never delete anything but test logs. And then I only delete the ones that I ran while developing my scripts. Not the 'for-the-record' test runs.
For scripts and tests, I just remove them and then after a while put them in an archive folder. Who knows when you'll need something back that you discarded three years ago?
90% of all papers that get filed are never looked at again for any reason. That other 10% could bite you in the end, though, if you didn't file them.
- guido_riedweg10 years agoNew Contributor
Hi Joe_2
thanks for your advice. Since all our tests are stored in our code repository, I am not afraid of deleting any unused tests. If we find out we need a test again in a couple of years, we're save to get it from there. But until then, I would like to keep my test base as clean as possible. That's why I want to delete unused keywordtests.
If I rename a keywordtest, TestComplete is (most of the time) smart enough to rename all usages of that test. So, the only way to find out if a test is needed would be to delete it and run all tests afterwards. I would like to avoid that additional test run, since it can be very time consuming. I would expect TestComplete to provide this information somehow, since it is needed to support an efficient renaming mechanism.
Best regards
Guido
Related Content
- 12 years ago
- 12 years ago
- 11 years ago
Recent Discussions
- 2 days ago
- 2 days ago
- 6 days ago