Forum Discussion
tristaanogre
11 years agoEsteemed Contributor
I don't think that this is something that can be done. It's part of the functionality of TestComplete that, if you want to Undo a change, it uses the .bak file to know what changes can be undone. I do have some suggestions for your two scenaros.
1) bak files are supposed to be excluded from source control. They are not necessary in order to check in or check out code. They are used (as mentioned) only as backups in order to restore code using Undo
2) I attempted to reproduce this in TestComplete 10.10 and could not. I don't have your version of TestComplete to try it in so I can't necessarily say the problem is in TestComplete itself. However, if you're checking the BAK file in and out of your source control, it's possible that the bak file, when cloned, was cloned in a "read-only" state and so cannot be over-written. Again, BAK files should not be part of any source control so, if you remove them from your source control processes, this might go away as well.
1) bak files are supposed to be excluded from source control. They are not necessary in order to check in or check out code. They are used (as mentioned) only as backups in order to restore code using Undo
2) I attempted to reproduce this in TestComplete 10.10 and could not. I don't have your version of TestComplete to try it in so I can't necessarily say the problem is in TestComplete itself. However, if you're checking the BAK file in and out of your source control, it's possible that the bak file, when cloned, was cloned in a "read-only" state and so cannot be over-written. Again, BAK files should not be part of any source control so, if you remove them from your source control processes, this might go away as well.