Forum Discussion

ory_z's avatar
ory_z
Contributor
15 years ago

Working with Project Suite variables from scripts - limitations

Hi there,



According to the TestComplete documentation (to the best of my understanding) the following cannot be done from scripts:

1. Setting a variable's Default Value

2. Setting a variable's Description

3. Adding a variable and specifying whether it should be temporary or persistant

4. Setting a variable's Category



These limitations are causing us a few issues:

In our projects, we are trying to work with a common library + a project specific library. The common library makes use of some ProjectSuite variables (as good global variables), and therefore wherever we use the common library, we need to add all the ProjectSuite variables used by the common library to the new project. Easiest way to do this is implement a script that simply adds all the variables required (already done).



However due to the limitations mentioned above:

- We cannot add temporary Variables with default values (for example a flag that always initialises as False)

- We canot automatically set variable descriptions making  this a manual cut and paste job



Is there any workaround?



Thanks

13 Replies

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    14 years ago
    Perhaps you can write code to initialize a temporary variable.  For example, a Table type variable is a temporary type.  The following code will create the variable "foo" and initialize it to a certain set of values.  



    function blah()

    {

    if (!Project.Variables.VariableExists("foo"))

    {

        Project.Variables.AddVariable("foo", "Table")

    }

    Project.Variables.foo.AddColumn("Test1")

    Project.Variables.foo.AddColumn("Test2")

    Project.Variables.foo.RowCount = 5

    var Index

    for(Index=0;Index<5;Index++)

    {

    Project.Variables.foo.Item("Test1", Index) = "Row" + Index + "Test1"

    Project.Variables.foo.Item("Test2", Index) = "Row" + Index + "Test1"

    }

    }




    And then, if you want the variable to be temporary, use Project.Variables.RemoveVariable to remove it from the project at the end of the run.  

  • scottb's avatar
    scottb
    Contributor
    12 years ago
    I vote for this also.  



    I work with confidential information.  I need to avoid having info retained on disk after TC is closed.  Because the dynamically created String variables retain their information in the system, I must use only Table variables to store my working String data when I generate variables dynamically.  I generate a lot of variables dynamically to accomodate flexibility in my tests.  



    The inability to create String variables with temporary data adds complexity.  Complexity adds costs as well as the likelihood of script errors. 



    Please add a setting to create variables with temporary storage.
  • AlexanderM's avatar
    AlexanderM
    Icon for Staff rankStaff
    15 years ago
    Hi,



    We have the following suggestions in our database to implement:


    - ability to add temporary project variables from script;


    - ability to copy project suite and project variables among project suites and projects.



    Your request has increased their rating.



    Unfortunately, the variable category, description and default value cannot be modified from script. We have registered the suggestion to implement this ability.



    The workaround is to use the Variables page of the project and project suite editors.



    3. Adding a variable and specifying whether it should be temporary or persistant



    Note that if you add variables of the Object, Table and DB table types, they will be temporary.
  • rminnich's avatar
    rminnich
    Contributor
    14 years ago
    - ability to add temporary project variables from script;









    I would like to bump this rating as well.  I currently use project variables as static global variables accessible from any script in any unit that will not be persisted across executions.  It would make it easier to not have to pre-define the variable in my project file.




  • rminnich's avatar
    rminnich
    Contributor
    14 years ago
    That is close to what I'm currently doing except that I declare the variable as temproary in the project file and don't call the remove at the end.  Will using add/remove variable change the project file?  My concern is that it will complain when I run the scripts in an isolated lab (no access to the source control repository) using TestExecute.



    I've also considered using a dictionary to implement my own variable manager, but it seems like that is functionality TC should provide.

  • ory_z's avatar
    ory_z
    Contributor
    14 years ago
    Thanks for the suggestion Robert. 



    However if I could go through the trouble to create a new variable at the beginning of each run and destroy it at the end, I could also (and more easy IMO) reset a persistent variable at the beginning of each run (thus making it act like a temporary one). The idea is to have a variable that always begins in a certain (default) state without extra effort.



    For now I add the variables I need to the project through scripts and then move the ones I want to be temporary from the persistent list manually.
  • rminnich's avatar
    rminnich
    Contributor
    14 years ago
    If I want to add an arbitrary number of variables where the number varies across runs, I have to declare them all up front and I can't go over that amount.



    It's not a common scenario, but one I could see happening.



    I could implement a dictionary and store that as a global and then use that for my temporary global variables, but that seems like a hack.
  • ory_z's avatar
    ory_z
    Contributor
    14 years ago
    It is a bit of hack but might work. If you need a code example and are using JS have a look at the following thread:

    http://smartbear.com/forums/forum/post/?mode=singleThread&thread=80d933b1-8266-4c98-b4cc-64f29b196a08



    BTW, In regards to your Source Control, adding and removing variables would most definitely change their project files, but (depending on your SCM) you could either hijack the files temporarily for the run, work on an exported copy of the files, or even check out and in through scripts before and after making changes to the project file. 



    Still not a great solution though :-(
  • rminnich's avatar
    rminnich
    Contributor
    14 years ago
    -Ory,

    I've used the dictionary objects already in my current project for string lookups.  It is a very handy class.  I'm not sure how well it works with mutable objects, but I'll cross that bridge when I actually have to.



    As for the source control issue, I'm not sure it will be a problem since the source control provider won't be accessible to the PCs running the tests due to being located on a isolated network.



    This suggestion was a "quality of life" enhancement more than anything. 



    Thanks for the feedback.