Forum Discussion
AlexKaras
11 years agoCommunity Hero
Hi Nathan,
As usual, full backup of test project is the best approach. :)
After you backed everything up, you may upgrade and I would advice to check if everything works as previously before making any significant changes in the test project.
If you decide to rollback, you have to use a created backup where you may replace script units with the ones from the upgarded project. This is the only thing that can be done without any risk (if you haven't implemented something that is specific for the version you are downgrading from). For all other test project items (which are xml-files), TestComplete makes changes during upgrade and you may or may not be able to (easily) roll these changes back. That is why I am suggesting to fully check if everything works as previously after upgrade and only then continue with project evolving.
As usual, full backup of test project is the best approach. :)
After you backed everything up, you may upgrade and I would advice to check if everything works as previously before making any significant changes in the test project.
If you decide to rollback, you have to use a created backup where you may replace script units with the ones from the upgarded project. This is the only thing that can be done without any risk (if you haven't implemented something that is specific for the version you are downgrading from). For all other test project items (which are xml-files), TestComplete makes changes during upgrade and you may or may not be able to (easily) roll these changes back. That is why I am suggesting to fully check if everything works as previously after upgrade and only then continue with project evolving.