I need to create a set of local variables at the beginning of a Keyword test and then use them later while executing the Test. Is there any possibility to create local variables dynamically as like project variables which can be created dynamically. Project.variables.<variable_name> = "project_variable_value" in the similar fashion can we create any variable associated to any keyword test Keywordtests.<generic_keyword_test_name>.variables.<variable_name> = "local_variable_value"

I've considered using a Code Snippet to add a variable dynamically within a keyword test. Like Project variables and ProjectSuite variables, using code, you can add and/or delete variables on the fly (KeywordTests.MyKWT.Variables.AddVariable is a viable function). However, building a keyword test around it will be difficult because, until the variable is added, you can't utilize it in any keyword test operations. You would have to resort to Code Expressions anytime you want to use the dynamically declared variable using KeywordTests.MyKWT.Variables.VariableByName(). Also, note that the variable would persist at the end of the keyword test meaning you would have to make sure you dispose of it after you're finished with it or add logic to detect whether or not it exists before you add it. It just seems that this over-complicates things that can be achieved simply by declaring the variables at design time of the KWT. The way I think of Keyword tests is that each one is a function declaration, much like declaring a function in JavaScript&colon; function Test() { var myVar; myVar = 'My Test'; Log.Message(myVar); } Variables within functions are declared when the function is declared. Even in JavaScript, while a variable declaration can happen any time within the code, they are "hoisted" to the top and effectively declared up front (unless you're running in strict mode but I digress). Anything added dynamically are properties added to objects, elements added to arrays, rows added to tables, etc. As Marsha_R mentioned, it would be interesting to know why you want to do things this way. What problem are you attempting to solve or what effect are you attempting to achieve? We might be able to find an alternative. For that matter, if it's a matter of having common global variables to be used across all your keyword tests, it might just be best to declare them as Project or ProjectSuite variables up front or build them into read/write properties in script extension runtime objects.

I'm not sure why the variable name needs to change. All you are doing is validating the contents of two fields in your application under test. The names of those fields in the AUT are not directly related to the variable names in your test code. What I would do is write your validation to take as string pairs the name and value, something like "Field1|e". That would then be passed as a parameter to a code routine which would take the first string as the field name and the second string as the field content (use aqString.GetListItem to get the individual pieces). Then execute your validation code using a "Find" function to find the field and validate it's contents based upon the passed in strings. This routine could then be repeated for an field/value pair. If I was doing this ALL in script code, I would even make it an object like {Field1: e, Field2: c} and parse it out that way but I've had difficulty sending objects like that from Keyword Tests to script code so the string pair works best. This way, you don't have to worry about dynamically changing variable names but simply use a single parameter on a libraried code function to do the validation. There are probably a number of variations of doing this kind of thing but, generally, what you are looking to do doesn't require dynamically changing variables but a validation function that receives the field name and value as parameters and does the validation that way. No need to create/rename a variable every time you do your validation.

Yes, what tristaanogre said! I can understand not wanting a million variables to be declared, but you really can just use the same ones over. If combining everything into one pair is too confusing, then just have a few pairs, one for each different type, but making them permanent variables will take one complication out of your testing.

Hi, I know we have option to create Keyword test variables at runtime. refer here But I'm not sure how we can use keyword test name in dynamic way.

When we have more control over the Keyword Test variables we may reduce the usage of variables prior to running the test.

Forum Discussion

RajeshVV

Contributor

8 years ago

How to create local variables at runtime for any keyword test in TestComplete

I need to create a set of local variables at the beginning of a Keyword test and then use them later while executing the Test. Is there any possibility to create local variables dynamically as like project variables which can be created dynamically.

Project.variables.<variable_name> = "project_variable_value"

in the similar fashion can we create any variable associated to any keyword test

Keywordtests.<generic_keyword_test_name>.variables.<variable_name> = "local_variable_value"

shankar_r
Community Hero
8 years ago
Hi,

I know we have option to create Keyword test variables at runtime. refer here

But I'm not sure how we can use keyword test name in dynamic way.
- RajeshVV
  Contributor
  8 years ago
  When we have more control over the Keyword Test variables we may reduce the usage of variables prior to running the test.
  - shankar_r
    Community Hero
    8 years ago
    As a workaround you can do like below,
    
    Keywordtests.<generic_keyword_test_name>.variables.<variable_name> = "local_variable_value" To handle this, var str_keywordtestname = "KeywordTest1"; var objKeyword = eval("Keywordtests." + str_keywordtestname); Now you will have you keyword test object then you use this object to create dynamic variable. objKeyword.variable.VariableByName("MsgVar");
    
    I haven't worked in Keyword test but I'm guess this will have some help for you to handle dynamic

Forum Discussion

How to create local variables at runtime for any keyword test in TestComplete

Recent Discussions

TestExexute sometimes not recognizing object

Keys method sometimes adds period(.) in the middle of text

How to fully automate test complete UI test cases flow

Related Content

TestComplete 15.66: Does it require .NET 8.0 Desktop Runtime

Issue sending Environment variable to TestComplete via Azure pipeline using command-line Parameters

Runtime-398Error