Contents Now Platform Capabilities Previous Topic Next Topic Passing data from one automated test step to another Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Passing data from one automated test step to another Some automated test steps create data that you can use as an input to a subsequent step. You can pass data from one test step to another using input variables and output variables.The term input variables is another name for the field values associated with a step. These values are known as input variables because they provide the input the step needs to accomplish its task. For example, the Open Form step has three input variables: Table, Record, and View.Figure 1. Example test step showing input variables Some types of step also have output variables. These are the values that later steps in the same test can use as input. For example, the Record Insert step has an output variable called Record which contains the sys_id of the newly-created record. Note: Input data can also be passed to an automated test case from an external source such as a .csv file.The test step form does not indicate if a test step has output variables or not. However, you can easily tell if any output variables are available to provide a value to any given input variable. If you can map the value of one step's output variable to the current step's input variable, the system displays the mapping icon () to the right of that input field. When you click the variable mapping icon, the system displays a tree giving you access to any available output variables from previous steps. Figure 2. Example test step showing output variables For step-by-step instructions on how to assign the value of an output variable to another step's input variable, see Pass values from one automated test step to another. For a list of test step configs that return one or more output variables and the definitions of those output variables, see List of test steps with output variables.For an example of a test that passes variables using input and output variables, see Automated Test Framework use case: reference a value from a previous step. On this page Send Feedback Previous Topic Next Topic
Passing data from one automated test step to another Some automated test steps create data that you can use as an input to a subsequent step. You can pass data from one test step to another using input variables and output variables.The term input variables is another name for the field values associated with a step. These values are known as input variables because they provide the input the step needs to accomplish its task. For example, the Open Form step has three input variables: Table, Record, and View.Figure 1. Example test step showing input variables Some types of step also have output variables. These are the values that later steps in the same test can use as input. For example, the Record Insert step has an output variable called Record which contains the sys_id of the newly-created record. Note: Input data can also be passed to an automated test case from an external source such as a .csv file.The test step form does not indicate if a test step has output variables or not. However, you can easily tell if any output variables are available to provide a value to any given input variable. If you can map the value of one step's output variable to the current step's input variable, the system displays the mapping icon () to the right of that input field. When you click the variable mapping icon, the system displays a tree giving you access to any available output variables from previous steps. Figure 2. Example test step showing output variables For step-by-step instructions on how to assign the value of an output variable to another step's input variable, see Pass values from one automated test step to another. For a list of test step configs that return one or more output variables and the definitions of those output variables, see List of test steps with output variables.For an example of a test that passes variables using input and output variables, see Automated Test Framework use case: reference a value from a previous step.
Passing data from one automated test step to another Some automated test steps create data that you can use as an input to a subsequent step. You can pass data from one test step to another using input variables and output variables.The term input variables is another name for the field values associated with a step. These values are known as input variables because they provide the input the step needs to accomplish its task. For example, the Open Form step has three input variables: Table, Record, and View.Figure 1. Example test step showing input variables Some types of step also have output variables. These are the values that later steps in the same test can use as input. For example, the Record Insert step has an output variable called Record which contains the sys_id of the newly-created record. Note: Input data can also be passed to an automated test case from an external source such as a .csv file.The test step form does not indicate if a test step has output variables or not. However, you can easily tell if any output variables are available to provide a value to any given input variable. If you can map the value of one step's output variable to the current step's input variable, the system displays the mapping icon () to the right of that input field. When you click the variable mapping icon, the system displays a tree giving you access to any available output variables from previous steps. Figure 2. Example test step showing output variables For step-by-step instructions on how to assign the value of an output variable to another step's input variable, see Pass values from one automated test step to another. For a list of test step configs that return one or more output variables and the definitions of those output variables, see List of test steps with output variables.For an example of a test that passes variables using input and output variables, see Automated Test Framework use case: reference a value from a previous step.
