Forum Discussion

kirk_bottomley's avatar
kirk_bottomley
Contributor
10 years ago

Assigning Variable Values to Remote Machines

Our test structure is one authoring machine writing tests using TestComplete, and TestExecute licenses on the machines that will run the tests. Each machine can install the software to any AppPath, a...
  • kirk_bottomley's avatar
    kirk_bottomley
    10 years ago

    I figured out a solution.

     

    You can't assign the value of a persistent variable to a persistent variable, it seems. But you can assign a temporary variable to one.

     

    So simply...

     

    function AssignVariables(VarName)
{
var MachineName = VarName + "_" + aqString.Replace(Sys.HostName, "-", "");
Project.Variables.VariableByName(VarName) = Project.Variables.VariableByName(MachineName);
}

    ...allows me to populate the Temporary Variables section with Variable_Machine-0123, call the routine as needed, and pass in the variable name to be assigned. Then I can just continue using the original variable in the rest of the tests and scripts.

     

    I know the better way would be to maintain a database or XML file with the machine names and their needed values, but until that is implemented, this will work.

    Thank you everyone who responded trying to help. Much appreciated.

ashokkumareds's avatar
ashokkumareds
Contributor
10 years ago

Hi,

I believe the culprit is the "If" statement.

It has 2 problems.

1. you have used "=" operator instead of "==". Is this by accident??

2. Use a aqString.Compare instead.

 

please post the updates. thank you,

 

 

  • chrisb's avatar
    chrisb
    Regular Contributor
    10 years ago

    Use triple equals to avoid type coercion. Also, you say it runs fine on one machine but not remote machines. Did you put a breakpoint in your script and check the values of the variables to compare and see what you are getting?

     

    What happens when the script fails on the remote machines, do you get the log message in your else statement?

     

    I am also wondering if your Sys.HostName is what you expect on the remote machines?

     

     

    function assignVariables(varName)
    {
    var machineName = aqString.Replace(Sys.HostName, "-", "");
    var concVar = varName + "_" + machineName;
    if (Project.Variables.VariableByName(varName)=== concVar){
        Log.Message(Project.Variables.VariableByName(varNa​me) + " now equals " + Project.Variables.VariableByName(varName + "_" + machineName) )
      }else
      { Log.Message(VarName + " not assigned.")
      }
    }

  • chrisb's avatar
    chrisb
    Regular Contributor
    10 years ago

    Use triple equals to avoid type coercion.

    • chrisb's avatar
      chrisb
      Regular Contributor
      10 years ago

      I am wondering if you have the project variable concVar saved to the variables object on your 'authoring' machine and it does not exist on the remote machine where you have the issue. Why not just compare varName against the conVar variable whose value you just create on the fly?...

       

      function assignVariables(varName)
      {
      var machineName = aqString.Replace(Sys.HostName, "-", "");
      var concVar = varName + "_" + machineName;
      if (Project.Variables.VariableByName(varName) === conVar)
        { Log.Message(Project.Variables.VariableByName(varNa​me) + " now equals " + Project.Variables.VariableByName(varName + "_" + machineName) )
        }else{
          Log.Message(varName + " not assigned.")
        }
      }

    • kirk_bottomley's avatar
      kirk_bottomley
      Contributor
      10 years ago

      "Use triple equals to avoid type coercion."

       

      Thank you for the feedback! I'm assigning variables in the function, though, not comparing them. I will probably add some comparisons when I write more logging. Thanks for the '= = =' suggestion for extra type comparisons. That might come in handy.

  • kirk_bottomley's avatar
    kirk_bottomley
    Contributor
    10 years ago

    "you have used "=" operator instead of "==". Is this by accident??"

     

    Not an accident, that's on purpose. Most operations return a 1 if they're successful, so writing it that way allows an error catch. It performs the operation as desired, and if true logs a success, but if false logs a failure.

     

    Thanks for the feedback!