SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 4 of 4
  1. #1
    Junior Member
    Join Date
    Oct 2005
    Posts
    10
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Save different versions of scripts?

    Hello,
    I am testing one version of our Software at the moment, but next week, I will get a new release with some new / changed features.
    So I need to actualize some of my scripts in TP.
    What is the best way to save all existing scripts concerning to the current release?
    Perhaps I need to test the older version in the future, so I want to "reload" all scripts, moduls, globals for this release...

    Do you understand my question? Is there any way to do so?
    Taste

  2. #2
    Senior Member
    Join Date
    Sep 2004
    Location
    Toronto, Canada
    Posts
    555
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Save different versions of scripts?

    Duplicate your TP database, and give the new one a different name. Create a separate ODBC connection. When logging into TP, you can choose the database to log into. Log into the old one or the new one.

    The only problem with this is that if you update one part of the code that is the same in the other database (the functionality did not change), you need to go change it in the other as well via copy and paste.

    Aracknid
    TestPartner:
    Current AUT running test scripts on TP 6.3 build 183, SQL 2000 DB.
    Legacy AUT running on TP 5.6.0 Build 81 and TP 6.2 build 449 with SQL 2000 DB.

    Test Environment:
    TP/IE Clients on VMWare ESX 4.1 server, AUT Servers on VMWare ESX 3.5 server.

    Application Under Test (AUT):
    Client/Server based, IE 7/8 interface with SQL 2005/2008 DB.

    Automating with TP since August 2004.

  3. #3
    Senior Member
    Join Date
    Sep 2001
    Location
    Philly
    Posts
    1,231
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Save different versions of scripts?

    A tweak on aracknid's approach is to use the Projects in your TP db as a seperation for builds. You can have project for Version 1 and when you get version 2 copy all the assets to a new project called Version 2. Remember that anything in the Common Project is available to all projects.

    Note... "copying" an entire project to a new one is a 1-asset at-a time process today, but the 5.4 release (now in beta) allows you to import export assets to xml.
    ~Alias~

  4. #4
    Junior Member
    Join Date
    Oct 2005
    Posts
    10
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Save different versions of scripts?

    Thanks!
    That both sounds good, I'll have a try next week.
    Thanks for your help...
    Taste

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 10.34%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 10:21 AM.

Copyright BetaSoft Inc.