...
Parameter | Description |
${testcaseIds} | The IDs of all the test cases selected for the execution. |
${uid} | The ID of the user who has been assigned to execute the test case. |
${rid} | The release ID. |
${cid} | The ID of the execution cycle. |
${cname} | The name of the execution cycle. |
${cpid} | The ID of the cycle phase of the execution cycle. |
${build} | The build information of the execution cycle. |
${env} | The environment information of the execution cycle. |
${nid} | The ID of the tree node to which the testcase belongs. |
${nname} | The name of the tree node to which the test case belongs. |
${testcaseNames} | The names of all the test cases selected for the execution. |
${projectName} | The project name. |
${projectId} | The ID of the project the test case belongs to. |
${releaseName} | The release name. |
${cyclePhaseName} | The name of the cycle phase of the execution cycle. |
${username} | The name of the user who is executing the test case(s). |
Execute a job
After creating a Script Automation job, you can use execute it to trigger automation for your test cases. To learn how to do that, see Executing Automated Test Cases.
...