Ask a Question

What are our options to have versioning on tests?

Occasional Contributor

What are our options to have versioning on tests?

What are our options to have versioning on tests?


We create keyword tests in Test complete for application V1 and modify tests for application V2.
When we are looking at test report, how do we know if we executed latest (modified tests for v2) keyword tests?
I am trying to find if there is any test versioning feature available in TestComplete. If there is none, what are options to set versioning for each test?

Community Hero

Our process has been to copy the original project as a whole for each set of changes.  We never tried to keep them all together since objects and therefore name mapping might have changed significantly.


For example, if we started with IceCream test and then have versions, we would end up with several projects in the suite:








[Community Hero]
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
Esteemed Contributor

Automated tests, even keyword tests, are "code".  To version them, I would use a version control/source control tool like GIT or Mercurial or something.  This would allow you tag or branch different versions of your code so you can always retrieve a previous version if necessary.


Now, as to know which version you're running...  

Add a single Log entry to the very beginning of your automation so that, every time you run it, it logs the version of the automation.  That entry you would simply change when you reversion your automation.  So, if you're running V1, the log records V1.  If you're running V2, the log records V2.  That way you don't have to worry about renaming projects, etc.  Just update the source for that log entry.

Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available

Depending on what you think of. We have everything in GIT for source control.


For creating multible instances of a test we have seperated test conditions, test sequence and data from eachother. Creating more reusable test sequences and data. We control what we execute by creating a test definition, which keeps the conditions, test sequence and data for the execution. After that we apply some magic trick with a script and run our test instances.


Scaling with this approach is very fast. And managing data is easier than managing many scripts.





Personal notebook/Blog:
Showing results for 
Search instead for 
Did you mean: