<div>
  <p>
    Jenkins TestLink Plug-in retrieves automated test cases data from TestLink. 
	This data is then set as environment variables. Thus your iterative  
	Build Steps can make use of this information to execute your automated 
	tests.
  </p>
  <p>For instance, you could run ant passing a Test Class as parameter: <pre>/opt/java/apache-ant-1.8.0/bin/ant -DtestClass=$TESTLINK_TESTCASE_TEST_CLASS</pre>
  <p>
  	List of environment variables that Jenkins TestLink Plug-in defines:
  </p>
  <p>
  	<ul>
  		<li>TESTLINK_TESTCASE_ID</li>
  		<li>TESTLINK_TESTCASE_NAME</li>
  		<li>TESTLINK_TESTCASE_TESTSUITEID</li>
  		<li>TESTLINK_TESTCASE_TESTPROJECTID</li>
  		<li>TESTLINK_TESTCASE_AUTHOR</li>
  		<li>TESTLINK_TESTCASE_SUMMARY</li>
  		<li>TESTLINK_BUILD_NAME</li>
  		<li>TESTLINK_TESTPLAN_NAME</li>
  		<li>TESTLINK_TESTPROJECT_NAME</li>
  		<li>TESTLINK_TESTCASE_$CUSTOM_FIELD_NAME</li>
  	</ul>
  </p>
  <p>
  	For each Custom Field found, TestLink Jenkins Plug-in defines an environment 
  	variable with its name and value, as shown above (%CUSTOM_FIELD_NAME%).
  	If the custom field name contains spaces the plug-in will convert them into 
  	_'s.
  </p>
  <p>
    For each Test Step of the Test Case, Jenkins TestLink Plug-in defines two environment 
    variables. TESTLINK_TESTCASE_STEP_$INDEX_ACTION and 
    TESTLINK_TESTCASE_STEP_$INDEX_EXPECTED. e.g.: for the first test step found 
    in a test case, you can expect to have the environment variable 
    TESTLINK_TESTCASE_STEP_1_ACTION with the action of the step, and 
    TESTLINK_TESTCASE_STEP_1_EXPECTED with the expected result.
  </p>
</div>