Forum Discussion

TCU100's avatar
TCU100
Occasional Contributor
5 years ago
Solved

What are our options to have versioning on tests?

What are our options to have versioning on tests?   Scenario: We create keyword tests in Test complete for application V1 and modify tests for application V2. When we are looking at test report, ...
Keyword Tests
Test Results
  • tristaanogre's avatar
    tristaanogre
    5 years ago

    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.

Marsha_R's avatar
Marsha_R
Champion Level 3

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:

 

IceCream

IceCreamWithCaramel

IceCreamWithNuts

IceCreamWithFudge

 

 

tristaanogre's avatar
tristaanogre
Esteemed Contributor
5 years ago

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.