English
资源说明：Jenkins testlink plugin
| Plugin Information |
|-----------------------------------------------------------------------------------------------|
| View TestLink [on the plugin site](https://plugins.jenkins.io/testlink) for more information. |
The current version of this plugin may not be safe to use. Please review
the following warnings before use:
- [Credentials stored in plain
text](https://jenkins.io/security/advisory/2019-08-07/#SECURITY-1428)
Older versions of this plugin may not be safe to use. Please review the
following warnings before using an older version:
- [Stored cross-site scripting
vulnerability](https://jenkins.io/security/advisory/2018-02-26/#SECURITY-731)
**This plugin is up for adoption.** Want to help improve this plugin?
[Click here to learn
more](https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin "Adopt a Plugin")!
This plug-in integrates Jenkins and [TestLink](http://testlink.org/) 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](http://issues.jenkins-ci.org/). 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.
When filing an issue, remember to include as much data as possible, but
avoid including sensitive data, as attachments can take a while to be
deleted from JIRA, as the process is manual and quite troublesome
## Jenkins TestLink Plug-in Tutorial
Check out this tutorial with step-by-step instructions on how to
integrate Jenkins and TestLink using TestLink Plug-in.
- [Jenkins TestLink Plug-in Tutorial
(HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/en/index.html)
- [Jenkins TestLink Plug-in Tutorial
(PDF)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/en/book.pdf)
- [Jenkins TestLink Plug-in Tutorial
(HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/de-de/index.html)
(German)
- [Jenkins TestLink Plug-in Tutorial
(HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/fr/index.html)
(French)
- [Jenkins TestLink Plug-in Tutorial
(HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/es/index.html)
(Spanish)
- [Jenkins TestLink Plug-in Tutorial
(HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/pt-br/index.html)
(Brazilian Portuguese)
#### [Who is using Jenkins TestLink Plug-in](https://wiki.jenkins.io/display/JENKINS/Who+is+using+TestLink+Plug-in)
[Let us know if you are using this
plug-in.](https://wiki.jenkins.io/display/JENKINS/Who+is+using+TestLink+Plug-in)
## Description
The TestLink plug-in integrates **Jenkins** with
[TestLink](http://testlink.org/). TestLink plug-in uses
[testlink-java-api](https://github.com/kinow/testlink-java-api "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.
The job configuration changed! Now there are three sections, what helps
you to configure your job, and add extra build steps, result seeking
strategies and general information about TestLink.
TestLink configuration section
Test Execution section
And Result Seeking Strategy section
You can use environment variables in Test project name, Test plan name
or Build name. For instance, build-project-$BUILD\_NUMBER would be
replaced by build-project- and the number of the Build executed in
Jenkins.
#### How does the plug-in execute my automated tests?
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](https://issues.jenkins-ci.org/browse/JENKINS-17622)):
- TESTLINK\_BUILD\_NAME
- TESTLINK\_TESTPLAN\_NAME
- TESTLINK\_TESTPROJECT\_NAME
- TESTLINK\_TESTCASE\_TOTAL
List of environment variables available during TestLink Plug-in
execution of iterative build steps:
- TESTLINK\_TESTCASE\_ID
- TESTLINK\_TESTCASE\_NAME
- TESTLINK\_TESTCASE\_TESTPROJECTID
- TESTLINK\_TESTCASE\_AUTHOR
- TESTLINK\_TESTCASE\_SUMMARY
- TESTLINK\_BUILD\_NAME
- TESTLINK\_TESTCASE\_TESTSUITEID
- TESTLINK\_TESTPLAN\_NAME
- TESTLINK\_TESTPROJECT\_NAME
- TESTLINK\_TESTCASE\_$CUSTOM\_FIELD\_NAME
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.
For each test case, the plug-in executes one call for each custom field.
In other words, if you have 1000 tests in a test plan, the plug-in will
execute a lot of calls to TestLink, downgrading the execution of your
job.
#### How does the plug-in know if a test passed or failed?
You can choose among different **result seeking strategies** in your job
configuration. The plug-in supports three **result formats**, *TestNG*,
*JUnit* and *TAP*.
#### TestNG result seeking strategies
**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 result seeking strategies
**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 result seeking strategies
**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
## Configuration
1. Download and install the latest version of TestLink
()
3. [Pull request \#20: Plan and build custom fields
support](https://github.com/jenkinsci/testlink-plugin/pull/20)
thanks @maiksaray!
### Release 3.11 (2015-11-14)
1. [TAP test plans support "n..m" with
n\>1](https://github.com/jenkinsci/testlink-plugin/pull/19)
2. [Added build number and error message in notes of JUnit Test
Result](https://github.com/jenkinsci/testlink-plugin/pull/18)
3. [Update
TestLinkSite.java](https://github.com/jenkinsci/testlink-plugin/pull/17)
### Release 3.10
1.
### Release 3.9
1.
2.
### Release 3.8
1. [JENKINS-20014: Jenkins Testlink plugin reports "Found 0 automated
test cases in
TestLink."](https://issues.jenkins-ci.org/browse/JENKINS-20014)
2. Reverted [JENKINS-17567: Allow the plug-in to filter test cases by
last execution
status](https://issues.jenkins-ci.org/browse/JENKINS-17567) due to a
backward incompatibility in TestLink 1.9.8 XML-RPC API
3. Updated [tap4j](http://tap4j.org/) to 4.0.4
### Release 3.7
1. Merged pull
request that
adds platforms to the job config
### Release 3.6
1. [JENKINS-17801: TAP-attachments produce file not found
error](https://issues.jenkins-ci.org/browse/JENKINS-17801)
2. [JENKINS-15790: Name of Test Case is
null](https://issues.jenkins-ci.org/browse/JENKINS-15790)
3. [JENKINS-19209: Testlink Plugin Not Run Test should mark build as
failed](https://issues.jenkins-ci.org/browse/JENKINS-19209)
4. [JENKINS-19390: Testlink Plugin did not manage to get 2nd execution
status](https://issues.jenkins-ci.org/browse/JENKINS-19390)
5. Updated testlink-java-api to 1.9.7-0
### Release 3.5
1. [JENKINS-17622: Cannot access TestLink environment variables within
Jenkins build](https://issues.jenkins-ci.org/browse/JENKINS-17622)
2. [JENKINS-16640: Mark in Jenkins build with "NOT RUN" Test Cases and
display in the UI (with colours,
etc)](https://issues.jenkins-ci.org/browse/JENKINS-16640)
### Release 3.4
1. [JENKINS-17567: Allow the plug-in to filter test cases by last
execution
status](https://issues.jenkins-ci.org/browse/JENKINS-17567)
2. [JENKINS-13821: When test uses DataProvider it mark in TestLink only
by last result](https://issues.jenkins-ci.org/browse/JENKINS-13821)
3. [JENKINS-17642: Trouble finding test results using TAP result
seeking
strategy](https://issues.jenkins-ci.org/browse/JENKINS-17642)
4. Quick profiling with Yourkit. Nothing worth of refactoring was
found. Thanks to Yourkit for providing an Open Source license to us.
### Release 3.3
1. **[Jenkins-17442: When connectin to TestLink find error
ClassCastException](https://issues.jenkins-ci.org/browse/JENKINS-17442) (due
to a bug in TL XML-RPC API, the plug-in wasn't working with TestLink
1.9.6)**
2. [Jenkins-16118: Testlink Plug-In: get Custom field information for
Testplans and
Testprojects](https://issues.jenkins-ci.org/browse/JENKINS-16118)
3. [Jenkins-17023: Jenkins Testlink plugin Found 0 test result is show
while test is
runned](https://issues.jenkins-ci.org/browse/JENKINS-17023)
4. [Jenkins-15588: TestLink is not getting
Updated](https://issues.jenkins-ci.org/browse/JENKINS-15588)
5. [Jenkins-17147: The configuration for testng method name and data
provider is not
saved](https://issues.jenkins-ci.org/browse/JENKINS-17147)
### Release 3.2
1. **Updated Jenkins version to 1.466**
2. The plug-in now should work correctly with other plug-ins that
require a BuildStepDescriptor, as Conditional Build Step
3. [JENKINS-15486: Documentation is needed for Project GTest Sample
Tap&Testlink for C++
testing](https://issues.jenkins-ci.org/browse/JENKINS-15486)
4. [JENKINS-15343: Unable to use Conditional BuildStep Plugin with
Testlink Plugin](https://issues.jenkins-ci.org/browse/JENKINS-15343)
### Release 3.1.5
[JENKINS-10904](https://issues.jenkins-ci.org/browse/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.
### Release 3.1.2
Added test summary. This way the user can see more details in TestLink
reports.
### Release 3.1.1
Fixing bugs in JUnit and TestNG strategies
### Release 3.1
1. **Created Result Seeking Strategy extension point**
2. Fixed all blocker issues
3. Added more result seeking strategies (TestNG method name, for
example)
4. Added new contributors to the project
5. **Code reviewed and refactored several parts of the code, it's way
cleaner now**
6. **Added configuration to make optional attachments upload**
### Release 3.0.2
Minor improvements for issues found during update of Jenkins TestLink
Plug-in Tutorial
### Release 3.0.1
[JENKINS-11264](https://issues.jenkins-ci.org/browse/JENKINS-11264) -
Test execution notes being added twice and incorrectly formatted
### Release 3.0
1. [JENKINS-10623](https://issues.jenkins-ci.org/browse/JENKINS-10623) -
Organize and update French, Spanish and Brazilian Portuguese
translation and documentation
2. [JENKINS-9054](https://issues.jenkins-ci.org/browse/JENKINS-9054)
**- Add support to platforms in TestLink plug-in**
3. [JENKINS-10809](https://issues.jenkins-ci.org/browse/JENKINS-10809) -
Add a way to call other build steps in test execution for the
plug-in (Yay for DRY!)
4. [JENKINS-10849](https://issues.jenkins-ci.org/browse/JENKINS-10849) -
OutOfMemoryError using TestLink plugin (Thanks to YourKit!)
### Release 2.5
1. JENKINS-9811 Add a POST \-field, to execute a
process after the plug-in iterates the retrieved automated test
cases
2. JENKINS-9672 Test link custom field parser split the String value by
semicolon or comma.
3. JENKINS-9993 Add root element for JUnit test results
### Release 2.2.2
1. FIXED-9444 - Add environment variables to single test command
(actually, I used some code from Jenkins core to execute both
commands now :-)
### Release 2.2.1
1. French translation
2. Small issue with non-existent option Debug in Job configuration
3. FIXED-9229 - JUnit wrong status
4. Portuguese i18n messages typo
### Release 2.2
1. JUnit BUG fix
2. Enhancement of the Build logs
### Release 2.1
1. **Migration from Hudson to Jenkins**
2. Test transaction property.
3. i18n (version 1.0 supports only English).
4. Add Javascript validation functions to each field in the global and
config pages.
5. Add single test command feature (it will enable running test suites)
6. Fixed Java class headers
7. JFreechart graphics betterment
8. Fixed BUG JENKINS-8636 TestLink Plugin FATAL: Error creating test
project
9. Fixed BUG JENKINS-8531 Unexprssive error message
### Release 2.0.1
1. Fixed BUG 8292 (java.lang.NullPointerException at
hudson.plugins.testlink.updater.TestLinkTestStatusUpdater.updateTestCases(TestLinkTestStatusUpdater.java:55)
### Release 2.0
1. **Settings automated tests properties as environment variables.**
2. **Switch from dbfacade-testlink-java-api to testlink-java-api**
**.**
3. **JUnit parser.**
4. **TestNG parser.**
5. **TAP parser using tap4j**
**
本源码包内暂不包含可直接显示的源代码文件，请下载源码包。
