This plug-in integrates Jenkins and TestLink and generates reports on automated test execution. With this plug-in you can manage your tests in TestLink, schedule and control in Jenkins, and execute using your favorite test execution tool (TestPartner, Selenium, TestNG, Perl modules, PHPUnit, among others).
This plug-in is not part of TestLink project, issues regarding Jenkins and TestLink integration must be reported in Jenkins JIRA. It has been reported by users that it is also possible to use ReportNG, as this tool has an option to output TestNG XML too.
The TestLink plug-in integrates Jenkins with TestLink. TestLink plug-in uses testlink-java-api to access TestLink XML-RPC API. With the information that you provide in the build step configuration the plug-in retrieves automated tests from TestLink. With the plug-in, you are able to execute build steps that call testing tools. It reads TestNG, JUnit and TAP test report formats, used to update TestLink test cases' executions.
TestLink configuration section
Test Execution section
And Result Seeking Strategy section
TestLink Plug-in retrieves automated test cases data from TestLink. This data is then set as environment variables. This way your build steps can make use of this information to execute your automated tests.
For instance, you could run ant passing a Test Class as parameter, more or less something like this, /opt/java/apache-ant-1.8.0/bin/ant -DtestClass=$TESTLINK_TESTCASE_TEST_CLASS. In this case, Test Case is the name of a custom field in TestLink.
List of environment variables available during TestLink Plug-in execution of single build steps (JENKINS-17622):
List of environment variables available during TestLink Plug-in execution of iterative build steps:
For each Custom Field found, TestLink Plug-in defines an environment variable for 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. i.e., Test Class can be accessed as %TESTLINK_TESTCASE_TEST_CLASS% in Windows or $TESTLINK_TESTCASE_TEST_CLASS in *nix-like systems.
You can choose among different result seeking strategies in your job configuration. The plug-in supports three result formats, TestNG, JUnit and TAP.
TestNG class name: The plug-in matches the TestNG class name (e.g.: org.tap4j.TestParser) and the key custom field value.
TestNG method name: The plug-in matches the TestNG method name (e.g.: org.tap4j.TestParser#testTokenizer) and the key custom field value.
TestNG suite name: The plug-in matches the TestNG suite name (e.g.: functional tests) and the key custom field value.
JUnit case class name: The plug-in matches the JUnit case class name (e.g.: org.tap4j.TestParser) and the key custom field value.
JUnit case name: The plug-in matches the JUnit case class name (e.g.: testTokenizer) and the key custom field value.
JUnit method name: The plug-in matches the JUnit case class name (e.g.: org.tap4j.TestParser#testTokenizer) and the key custom field value.
JUnit suite name: The plug-in matches the JUnit suite name (e.g.:functional tests) and the key custom field value.
TAP file name: The plug-in matches the TAP file name (e.g.: testFtpProtocol.tap) and the key custom field value.
TAP file name multiple test points: Adds one test execution in TestLink for each TAP Test Result with its execution status
Want to see this plug-in in your language? Send us an e-mail and we will get in touch with the text that needs to be translated.
The plug-in 1.0 and 1.1 versions were pilot projects that should be ignored. They have issues in distributed environments and depend on Maven. Please, consider updating your plug-in to the 2.0 version.
For commercial support, please get contact us via @tupilabs
JENKINS-10904 - Include test step information as env vars. We had to update testlink-java-api, as the bug was in there. However, the TestLink data stored in builds will be lost. So if you need any of the data, back it up before updating the plug-in.
Added test summary. This way the user can see more details in TestLink reports.
Fixing bugs in JUnit and TestNG strategies
Minor improvements for issues found during update of Jenkins TestLink Plug-in Tutorial
JENKINS-11264 - Test execution notes being added twice and incorrectly formatted
YourKit is kindly supporting open source projects with its full-featured Java Profiler.
Skip to end of metadata Go to start of metadata