Parameter-Token Replacement Upon Execution

Any string input for a property of a test may contain placeholders in the following form: ${parametername}. parametername must match the name of a parameter defined or inherited for the test. At execution time, the placeholder is replaced by the value entered for the parameter with the denoted name. This makes recurring strings in properties more customizable and facilitates the editing of common definitions.

When Silk Central finds a parameter with the notation ${parametername}, it first checks if the parameter is included in the defined parameters, and if not, it checks if the parameter is defined as an environmental variable on the execution server. Environment variable values are used as defined at the startup time of the execution server. The Silk Central variable name only matches the name of the environment variable if the case is exactly the same, or if all characters are either lowercase or uppercase. Example: Silk Central matches the environment variable SilkHome against ${SilkHome}, ${silkhome} and ${SILKHOME}, but not against ${silkHome}.

For example, if the value of a JUnit classpath property is junit.jar;${MyWorkingDir}/myclasses and the parameter MyWorkingDir has the value C:/Temp/MyWorking, the resultant effective property value is junit.jar;C:/Temp/MyWorking/myclasses.

Note: The value of a parameter may also contain other parameter placeholders, which allows nesting based on the same principle.