Forum Discussion

kirk_bottomley's avatar
kirk_bottomley
Contributor
11 years ago
Solved

Different Variable Values For Different Workstations

I do apologize for asking this question again, but I still can't find out how to do this, and the lack of this one technique is holding up our ability to integrate TC in our process.  We hav...
  • TanyaYatskovska's avatar
    TanyaYatskovska
    11 years ago

    Hi Kirk,


     


    You need to work with the local value of a persistent variable. In this case, each slave machine will work with its own values. Read the "Project and Project Suite Editor - Variables Page" article to learn more about this.


     


    BTW, consider using the Network Suite variables in your test - they can help you create more flexible and massive distributing tests.

Kateryna's avatar
Kateryna
Contributor
11 years ago
Hi there!



If I understood you properly, I had the same issue. I  had problems with DBTabled because they use exact name of the workstation. I wrote a small script that changes that name (name in the connection string) into the name of the current computer (Delphi script):




procedure Test;


 var i, tbls, tablename, computername;


 begin


   tbls := aqObject.GetProperties(DBTables);


   computername:= Sys.HostName;


   for i := 0 to tbls.Count - 1 do


   begin


     tablename:= tbls.Item(i).Value; 


     tablename.ConnectionString := 'Provider=SQLOLEDB.1;'+'Integrated Security=SSPI;'+'Persist Security Info=False;'+'Initial Catalog=NL3_TestComplete;'+'Data Source='+computername;


   end;


 end;



I guess you can do something similar in your case. This script works during test execution.