Forum Discussion
SmartBear_Suppo
Alumni
16 years agoHi,
Any properties set at a point higher in the hierarchy should be visible below it, so in a TestCase you can easily access properties in the TestStep, TestCase and TestSuite. These TestSuite properties, while accessible from a TestCase, do not overwrite any values. You need to actually use read the properties for this to be of any use. This can be done using Property Expansions. For instance, if you've created properties named "Endpoint", "Username" and "Password" (These are just variable names, and could be anything), you can set the Properties on the TestStep to "${#TestSuite#Endpoint}", "${#TestSuite#Username}", etc (without quotes). When run, these expansions will dynamically be replaced with the values set in the TestSuite.
Regards,
Dain
eviware.com
Any properties set at a point higher in the hierarchy should be visible below it, so in a TestCase you can easily access properties in the TestStep, TestCase and TestSuite. These TestSuite properties, while accessible from a TestCase, do not overwrite any values. You need to actually use read the properties for this to be of any use. This can be done using Property Expansions. For instance, if you've created properties named "Endpoint", "Username" and "Password" (These are just variable names, and could be anything), you can set the Properties on the TestStep to "${#TestSuite#Endpoint}", "${#TestSuite#Username}", etc (without quotes). When run, these expansions will dynamically be replaced with the values set in the TestSuite.
Regards,
Dain
eviware.com