{"id":27243740,"url":"https://github.com/jenkinsci/testlink-plugin","last_synced_at":"2025-09-12T03:40:05.567Z","repository":{"id":41348106,"uuid":"1163782","full_name":"jenkinsci/testlink-plugin","owner":"jenkinsci","description":"Jenkins testlink plugin","archived":false,"fork":false,"pushed_at":"2025-04-09T15:55:38.000Z","size":30945,"stargazers_count":45,"open_issues_count":11,"forks_count":78,"subscribers_count":105,"default_branch":"master","last_synced_at":"2025-04-09T16:51:33.471Z","etag":null,"topics":["adopt-this-plugin"],"latest_commit_sha":null,"homepage":"https://plugins.jenkins.io/testlink/","language":"Java","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/jenkinsci.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2010-12-13T05:56:04.000Z","updated_at":"2025-04-09T15:55:44.000Z","dependencies_parsed_at":"2025-04-09T16:40:29.378Z","dependency_job_id":"62208b11-4e22-4206-a76b-8267c407461a","html_url":"https://github.com/jenkinsci/testlink-plugin","commit_stats":null,"previous_names":[],"tags_count":41,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jenkinsci%2Ftestlink-plugin","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jenkinsci%2Ftestlink-plugin/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jenkinsci%2Ftestlink-plugin/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/jenkinsci%2Ftestlink-plugin/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/jenkinsci","download_url":"https://codeload.github.com/jenkinsci/testlink-plugin/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248298435,"owners_count":21080318,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["adopt-this-plugin"],"created_at":"2025-04-10T20:58:22.544Z","updated_at":"2025-04-10T20:58:23.229Z","avatar_url":"https://github.com/jenkinsci.png","language":"Java","funding_links":[],"categories":[],"sub_categories":[],"readme":"| Plugin Information                                                                            |\n|-----------------------------------------------------------------------------------------------|\n| View TestLink [on the plugin site](https://plugins.jenkins.io/testlink) for more information. |\n\nThe current version of this plugin may not be safe to use. Please review\nthe following warnings before use:\n\n-   [Credentials stored in plain\n    text](https://jenkins.io/security/advisory/2019-08-07/#SECURITY-1428)\n\nOlder versions of this plugin may not be safe to use. Please review the\nfollowing warnings before using an older version:\n\n-   [Stored cross-site scripting\n    vulnerability](https://jenkins.io/security/advisory/2018-02-26/#SECURITY-731)\n\n**This plugin is up for adoption.** Want to help improve this plugin?\n[Click here to learn\nmore](https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin \"Adopt a Plugin\")!\n\nThis plug-in integrates Jenkins and [TestLink](http://testlink.org/) and\ngenerates reports on automated test execution. With this plug-in you can\nmanage your tests in TestLink, schedule and control in Jenkins, and\nexecute using your favorite test execution tool (TestPartner, Selenium,\nTestNG, Perl modules, PHPUnit, among others).  \nThis plug-in is not part of TestLink project, issues regarding Jenkins\nand TestLink integration must be reported in [Jenkins\nJIRA](http://issues.jenkins-ci.org/). It has been reported by users that\nit is also possible to use ReportNG, as this tool has an option to\noutput TestNG XML too.\n\nWhen filing an issue, remember to include as much data as possible, but\navoid including sensitive data, as attachments can take a while to be\ndeleted from JIRA, as the process is manual and quite troublesome\n![(smile)](https://wiki.jenkins.io/s/en_GB/8100/5084f018d64a97dc638ca9a178856f851ea353ff/_/images/icons/emoticons/smile.svg)\n\n## Jenkins TestLink Plug-in Tutorial\n\nCheck out this tutorial with step-by-step instructions on how to\nintegrate Jenkins and TestLink using TestLink Plug-in.\n\n-   [Jenkins TestLink Plug-in Tutorial\n    (HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/en/index.html)\n-   [Jenkins TestLink Plug-in Tutorial\n    (PDF)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/en/book.pdf)\n-   [Jenkins TestLink Plug-in Tutorial\n    (HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/de-de/index.html)\n    (German)\n-   [Jenkins TestLink Plug-in Tutorial\n    (HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/fr/index.html)\n    (French)\n-   [Jenkins TestLink Plug-in Tutorial\n    (HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/es/index.html)\n    (Spanish)\n-   [Jenkins TestLink Plug-in Tutorial\n    (HTML)](http://tupilabs.com/books/jenkins-testlink-plugin-tutorial/pt-br/index.html)\n    (Brazilian Portuguese)\n\n#### [Who is using Jenkins TestLink Plug-in](https://wiki.jenkins.io/display/JENKINS/Who+is+using+TestLink+Plug-in)\n\n[Let us know if you are using this\nplug-in.](https://wiki.jenkins.io/display/JENKINS/Who+is+using+TestLink+Plug-in)\n\n## Description\n\nThe TestLink plug-in integrates **Jenkins** with\n[TestLink](http://testlink.org/). TestLink plug-in uses\n[testlink-java-api](https://github.com/kinow/testlink-java-api \"testlink-java-api\")\nto access TestLink **XML-RPC** API. With the information that you\nprovide in the build step configuration the plug-in **retrieves\nautomated tests from TestLink**. With the plug-in, you are able to\nexecute **build steps** that call testing tools. It reads **TestNG**,\n**JUnit** and **TAP** test report **formats**, used to update TestLink\ntest cases' executions.\n\n![](https://wiki.jenkins.io/download/attachments/46335320/1.png?version=2\u0026modificationDate=1318036291000\u0026api=v2)\n\nThe job configuration changed! Now there are three sections, what helps\nyou to configure your job, and add extra build steps, result seeking\nstrategies and general information about TestLink.\n\nTestLink configuration section\n\n![](https://wiki.jenkins.io/download/attachments/46335320/001.PNG?version=2\u0026modificationDate=1331609348000\u0026api=v2)\n\nTest Execution section\n\n![](https://wiki.jenkins.io/download/attachments/46335320/002.PNG?version=2\u0026modificationDate=1331609353000\u0026api=v2)\n\nAnd Result Seeking Strategy section\n\n![](https://wiki.jenkins.io/download/attachments/46335320/003.PNG?version=2\u0026modificationDate=1331609355000\u0026api=v2)\n\nYou can use environment variables in Test project name, Test plan name\nor Build name. For instance, build-project-$BUILD\\_NUMBER would be\nreplaced by build-project- and the number of the Build executed in\nJenkins.\n\n![](https://wiki.jenkins.io/download/attachments/46335320/3.png?version=1\u0026modificationDate=1318035980000\u0026api=v2)\n\n![](https://wiki.jenkins.io/download/attachments/46335320/4.png?version=1\u0026modificationDate=1318035980000\u0026api=v2)\n\n![](https://wiki.jenkins.io/download/attachments/46335320/5.png?version=1\u0026modificationDate=1318035979000\u0026api=v2)\n\n#### How does the plug-in execute my automated tests?\n\nTestLink Plug-in retrieves automated test cases data from TestLink. This\ndata is then set as environment variables. This way your build steps can\nmake use of this information to execute your automated tests.\n\nFor instance, you could run ant passing a Test Class as parameter, more\nor less something like this, /opt/java/apache-ant-1.8.0/bin/ant\n-DtestClass=$TESTLINK\\_TESTCASE\\_TEST\\_CLASS. In this case, Test Case is\nthe name of a custom field in TestLink.\n\nList of environment variables available during TestLink Plug-in\nexecution of single build steps\n([JENKINS-17622](https://issues.jenkins-ci.org/browse/JENKINS-17622)):\n\n-   TESTLINK\\_BUILD\\_NAME\n-   TESTLINK\\_TESTPLAN\\_NAME\n-   TESTLINK\\_TESTPROJECT\\_NAME\n-   TESTLINK\\_TESTCASE\\_TOTAL\n\nList of environment variables available during TestLink Plug-in\nexecution of iterative build steps:\n\n-   TESTLINK\\_TESTCASE\\_ID\n-   TESTLINK\\_TESTCASE\\_NAME\n-   TESTLINK\\_TESTCASE\\_TESTPROJECTID\n-   TESTLINK\\_TESTCASE\\_AUTHOR\n-   TESTLINK\\_TESTCASE\\_SUMMARY\n-   TESTLINK\\_BUILD\\_NAME\n-   TESTLINK\\_TESTCASE\\_TESTSUITEID\n-   TESTLINK\\_TESTPLAN\\_NAME\n-   TESTLINK\\_TESTPROJECT\\_NAME\n-   TESTLINK\\_TESTCASE\\_$CUSTOM\\_FIELD\\_NAME\n\nFor each Custom Field found, TestLink Plug-in defines an environment\nvariable for with its name and value, as shown above\n(%CUSTOM\\_FIELD\\_NAME%). If the custom field name contains spaces the\nplug-in will convert them into \\_'s. i.e., Test Class can be accessed as\n%TESTLINK\\_TESTCASE\\_TEST\\_CLASS% in Windows or\n$TESTLINK\\_TESTCASE\\_TEST\\_CLASS in \\*nix-like systems.\n\nFor each test case, the plug-in executes one call for each custom field.\nIn other words, if you have 1000 tests in a test plan, the plug-in will\nexecute a lot of calls to TestLink, downgrading the execution of your\njob.\n\n#### How does the plug-in know if a test passed or failed?\n\nYou can choose among different **result seeking strategies** in your job\nconfiguration. The plug-in supports three **result formats**, *TestNG*,\n*JUnit* and *TAP*. \n\n#### TestNG result seeking strategies\n\n**TestNG class name**: The plug-in matches the TestNG class name (e.g.:\norg.tap4j.TestParser) and the key custom field value.\n\n**TestNG method name**: The plug-in matches the TestNG method name\n(e.g.: org.tap4j.TestParser\\#testTokenizer) and the key custom field\nvalue.\n\n**TestNG suite name**: The plug-in matches the TestNG suite name (e.g.:\nfunctional tests) and the key custom field value.\n\n#### JUnit result seeking strategies\n\n**JUnit case class name**: The plug-in matches the JUnit case class name\n(e.g.: org.tap4j.TestParser) and the key custom field value.\n\n**JUnit case name**: The plug-in matches the JUnit case class name\n(e.g.: testTokenizer) and the key custom field value.\n\n**JUnit method name**: The plug-in matches the JUnit case class name\n(e.g.: org.tap4j.TestParser\\#testTokenizer) and the key custom field\nvalue.\n\n**JUnit suite name**: The plug-in matches the JUnit suite name\n(e.g.:functional tests) and the key custom field value.\n\n#### TAP result seeking strategies\n\n**TAP file name**: The plug-in matches the TAP file name (e.g.:\ntestFtpProtocol.tap) and the key custom field value. \n\n**TAP file name multiple test points:** Adds one test execution in\nTestLink for each TAP Test Result with its execution status\n\n## Configuration\n\n1.  Download and install the latest version of TestLink\n    (\u003chttp://testlink.org/\u003e).\n2.  Create automated tests in TestLink with Custom Field for automation.\n3.  Install the TestLink plug-in from the Jenkins Plugin Manager\n4.  Define a TestLink configuration from the Configure System page.\n5.  Add a Invoke TestLink build step in the job you want execute\n    automated tests.\n6.  Configure the required properties.\n\n## Languages Supported\n\n1.  English (American)\n2.  Portuguese (Brazil)\n3.  Spanish (Thanks to César Fernandes de Almeida)\n4.  French (Thanks to Floréal Toumikian, Olivier Renault, Latifa\n    Elkarama)\n\nWant to see this plug-in in your language? Send us an e-mail and we will\nget in touch with the text that needs to be translated.\n\n## Resources\n\n1.  [Enabling SSL for Jenkins TestLink plugin in\n    Tomcat](http://yasassriratnayake.blogspot.co.nz/2016/04/enabling-ssl-for-jenkins-testlink.html)\n2.  [Google Test + TAP Listener + Jenkins TestLink\n    Plug-in](http://www.kinoshita.eti.br/2012/10/11/jenkins-testlink-and-gtest-in-5-minutes-or-so/)\n3.  [Article](http://www.kinoshita.eti.br/wp-content/uploads/2010/12/testingexperience12_12_10_Kinoshita_Santos.pdf)\n    published in [Testing Experience\n    magazine](http://www.testingexperience.com/) issue number 12 (Open\n    Source Tools) written by [Bruno P.\n    Kinoshita](http://www.kinoshita.eti.br/) and Anderson dos\n    Santos. 2010.\n4.  [Slides](http://www.scribd.com/doc/43729582/Automatizando-Testes-Com-Hudson-e-TestLink)\n    used in the lighting talk presented at [Encontro\n    Ágil](http://www.encontroagil.com.br/) 2010 in\n    [IME-USP](http://www.ime.usp.br/) (Portuguese Only). 2010.\n5.  [Article](http://www.automatedtestinginstitute.com/home/ASTMagazine/2011/AutomatedSoftwareTestingMagazine_March2011.pdf)\n    published in [Automated Software Testing\n    Magazine](http://www.automatedtestinginstitute.com/), volume 3,\n    issue 1. March, 2011.\n6.  [Slides](http://www.belgiumtestingdays.com/archive/bruno_de_paula_kinoshita_how_to_automate_tests_using_testlink_and_hudson.pdf)\n    used in the presentation done in [Belgium Testing\n    Days](http://www.belgiumtestingdays.com/) 2011.\n7.  [Lighting talk](http://www.vimeo.com/16924211) for [Encontro\n    Ágil](http://www.encontroagil.com.br/) 2010, at\n    [IME-USP](http://www.ime.usp.br/).\n8.  More articles and tips on [Bruno P. Kinoshita's\n    website](http://www.kinoshita.eti.br/).\n9.  Sponsor company (until May 2011): [Sysmap\n    Solutions](http://www.sysmap.com.br/) - Brazil.\n10. Sponsor company: [TupiLabs](http://www.tupilabs.com/) - Brazil\n11. Presentation at [STPCon](http://www.stpcon.com/) Spring March 2012\n    in New Orleans - USA.\n12. A [collection of\n    links](http://forza.cocolog-nifty.com/blog/2012/10/jenkins-testlin.html)\n    about jenkins-testlink plugin\n    by [http://forza.cocolog-nifty.com](http://forza.cocolog-nifty.com/) (Japanese/日本語)\n\n## Sponsors\n\n[![](https://wiki.jenkins.io/download/attachments/46335320/logo1.png?version=1\u0026modificationDate=1342969072000\u0026api=v2)](http://www.tupilabs.com/)\n\nFor commercial support, please get contact us\nvia [@tupilabs](https://twitter.com/tupilabs)\n\n## Release Notes\n\n### Release 4.0 (????-??-??)\n\n1.  [JENKINS-64023](https://issues.jenkins-ci.org/browse/JENKINS-64023) - org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/testlink/WEB-INF/lib/testlink.jar!/hudson/plugins/testlink/TestLinkResult/index.jelly:6:57: No page found 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult\n\n### Release 3.16 (2019-02-07)\n\n1.  [JENKINS-48488](https://issues.jenkins-ci.org/browse/JENKINS-48488) -\n    Request to make Testcase version available in Jenkins Build\n    environment\n\n### Release 3.15 (2018-12-29)\n\n1.  Updated testlink-java-api to 1.9.17-0\n2.  Updated Jenkins parent in pom.xml\n3.  Updated dependencies (lang, io, codec)\n4.  Set project Java to 8\n5.  Tested with TestLink 1.9.17 (basic workflow, with a TAP file name\n    strategy)\n\n### Release 3.14 (2018-03-28)\n\n1.  [JENKINS-50445](https://issues.jenkins-ci.org/browse/JENKINS-50445) -\n    Add tap4j model objects to the whitelist for serialization to make\n    TAP reporting compatible with Jenkins 2.102+\n2.  [JENKINS-49302](https://issues.jenkins-ci.org/browse/JENKINS-49302) -\n    Fix escaping of summary reports (regression in 3.13)\n3.  [PR \\#31](https://github.com/jenkinsci/testlink-plugin/pull/31) -\n    Fix issues in French localization\n\n### Release 3.13 (2017--)\n\n1.  [Pull request \\#26: make the testcase external ID visible as an\n    environment variable in a Jenkins\n    shell](https://github.com/jenkinsci/testlink-plugin/pull/26) thanks\n    @johnwalker247!\n2.  [Pull request \\#22: Updateparser to version 0.5 with code\n    fixes](https://github.com/jenkinsci/testlink-plugin/pull/22) thanks\n    @yasassri\n3.  [Fix security\n    issue](https://jenkins.io/security/advisory/2018-02-26/)\n\n### Release 3.12 (2016-04-17)\n\n1.  Upgraded\n    [tap4j](https://wiki.jenkins.io/display/JENKINS/TestLink+Plugin#)([http://tap4j.org](http://tap4j.org/))\n2.  Upgraded\n    [testlink-java-api](https://wiki.jenkins.io/display/JENKINS/TestLink+Plugin#)(\u003chttps://github.com/kinow/testlink-java-api\u003e)\n3.  [Pull request \\#20: Plan and build custom fields\n    support](https://github.com/jenkinsci/testlink-plugin/pull/20)\n    thanks @maiksaray!\n\n### Release 3.11 (2015-11-14)\n\n1.  [TAP test plans support \"n..m\" with\n    n\\\u003e1](https://github.com/jenkinsci/testlink-plugin/pull/19)\n2.  [Added build number and error message in notes of JUnit Test\n    Result](https://github.com/jenkinsci/testlink-plugin/pull/18)\n3.  [Update\n    TestLinkSite.java](https://github.com/jenkinsci/testlink-plugin/pull/17)\n\n### Release 3.10\n\n1.  \u003chttps://issues.jenkins-ci.org/browse/JENKINS-20599\u003e\n\n### Release 3.9\n\n1.  \u003chttps://issues.jenkins-ci.org/browse/JENKINS-20587\u003e\n2.  \u003chttps://issues.jenkins-ci.org/browse/JENKINS-20589\u003e\n\n### Release 3.8\n\n1.  [JENKINS-20014: Jenkins Testlink plugin reports \"Found 0 automated\n    test cases in\n    TestLink.\"](https://issues.jenkins-ci.org/browse/JENKINS-20014)\n2.  Reverted [JENKINS-17567: Allow the plug-in to filter test cases by\n    last execution\n    status](https://issues.jenkins-ci.org/browse/JENKINS-17567) due to a\n    backward incompatibility in TestLink 1.9.8 XML-RPC API\n3.  Updated [tap4j](http://tap4j.org/) to 4.0.4\n\n### Release 3.7\n\n1.  Merged pull\n    request \u003chttps://github.com/jenkinsci/testlink-plugin/pull/8\u003e that\n    adds platforms to the job config\n\n### Release 3.6\n\n1.  [JENKINS-17801: TAP-attachments produce file not found\n    error](https://issues.jenkins-ci.org/browse/JENKINS-17801)\n2.  [JENKINS-15790: Name of Test Case is\n    null](https://issues.jenkins-ci.org/browse/JENKINS-15790)\n3.  [JENKINS-19209: Testlink Plugin Not Run Test should mark build as\n    failed](https://issues.jenkins-ci.org/browse/JENKINS-19209)\n4.  [JENKINS-19390: Testlink Plugin did not manage to get 2nd execution\n    status](https://issues.jenkins-ci.org/browse/JENKINS-19390)\n5.  Updated testlink-java-api to 1.9.7-0\n\n### Release 3.5\n\n1.  [JENKINS-17622: Cannot access TestLink environment variables within\n    Jenkins build](https://issues.jenkins-ci.org/browse/JENKINS-17622)\n2.  [JENKINS-16640: Mark in Jenkins build with \"NOT RUN\" Test Cases and\n    display in the UI (with colours,\n    etc)](https://issues.jenkins-ci.org/browse/JENKINS-16640)\n\n### Release 3.4\n\n1.  [JENKINS-17567: Allow the plug-in to filter test cases by last\n    execution\n    status](https://issues.jenkins-ci.org/browse/JENKINS-17567)\n2.  [JENKINS-13821: When test uses DataProvider it mark in TestLink only\n    by last result](https://issues.jenkins-ci.org/browse/JENKINS-13821)\n3.  [JENKINS-17642: Trouble finding test results using TAP result\n    seeking\n    strategy](https://issues.jenkins-ci.org/browse/JENKINS-17642)\n4.  Quick profiling with Yourkit. Nothing worth of refactoring was\n    found. Thanks to Yourkit for providing an Open Source license to us.\n\n### Release 3.3\n\n1.  **[Jenkins-17442: When connectin to TestLink find error\n    ClassCastException](https://issues.jenkins-ci.org/browse/JENKINS-17442) (due\n    to a bug in TL XML-RPC API, the plug-in wasn't working with TestLink\n    1.9.6)**\n2.  [Jenkins-16118: Testlink Plug-In: get Custom field information for\n    Testplans and\n    Testprojects](https://issues.jenkins-ci.org/browse/JENKINS-16118)\n3.  [Jenkins-17023: Jenkins Testlink plugin Found 0 test result is show\n    while test is\n    runned](https://issues.jenkins-ci.org/browse/JENKINS-17023)\n4.  [Jenkins-15588: TestLink is not getting\n    Updated](https://issues.jenkins-ci.org/browse/JENKINS-15588)\n5.  [Jenkins-17147: The configuration for testng method name and data\n    provider is not\n    saved](https://issues.jenkins-ci.org/browse/JENKINS-17147)\n\n### Release 3.2\n\n1.  **Updated Jenkins version to 1.466**\n2.  The plug-in now should work correctly with other plug-ins that\n    require a BuildStepDescriptor, as Conditional Build Step\n3.  [JENKINS-15486: Documentation is needed for Project GTest Sample\n    Tap\u0026Testlink for C++\n    testing](https://issues.jenkins-ci.org/browse/JENKINS-15486)\n4.  [JENKINS-15343: Unable to use Conditional BuildStep Plugin with\n    Testlink Plugin](https://issues.jenkins-ci.org/browse/JENKINS-15343)\n\n### Release 3.1.5\n\n[JENKINS-10904](https://issues.jenkins-ci.org/browse/JENKINS-10904) -\nInclude test step information as env vars. We had to update\ntestlink-java-api, as the bug was in there. However, the TestLink data\nstored in builds will be lost. So if you need any of the data, back it\nup before updating the plug-in. \n\n### Release 3.1.2\n\nAdded test summary. This way the user can see more details in TestLink\nreports.\n\n### Release 3.1.1\n\nFixing bugs in JUnit and TestNG strategies\n\n### Release 3.1\n\n1.  **Created Result Seeking Strategy extension point**\n2.  Fixed all blocker issues\n3.  Added more result seeking strategies (TestNG method name, for\n    example)\n4.  Added new contributors to the project\n5.  **Code reviewed and refactored several parts of the code, it's way\n    cleaner now**\n6.  **Added configuration to make optional attachments upload**\n\n### Release 3.0.2\n\nMinor improvements for issues found during update of Jenkins TestLink\nPlug-in Tutorial\n\n### Release 3.0.1\n\n[JENKINS-11264](https://issues.jenkins-ci.org/browse/JENKINS-11264) -\nTest execution notes being added twice and incorrectly formatted\n\n### Release 3.0\n\n1.  [JENKINS-10623](https://issues.jenkins-ci.org/browse/JENKINS-10623) -\n    Organize and update French, Spanish and Brazilian Portuguese\n    translation and documentation\n2.  [JENKINS-9054](https://issues.jenkins-ci.org/browse/JENKINS-9054)\n    **- Add support to platforms in TestLink plug-in**\n3.  [JENKINS-10809](https://issues.jenkins-ci.org/browse/JENKINS-10809) -\n    Add a way to call other build steps in test execution for the\n    plug-in (Yay for DRY!)\n4.  [JENKINS-10849](https://issues.jenkins-ci.org/browse/JENKINS-10849) -\n    OutOfMemoryError using TestLink plugin (Thanks to YourKit!)\n\n### Release 2.5\n\n1.  JENKINS-9811 Add a POST \\\u003cSingle test command\\\u003e-field, to execute a\n    process after the plug-in iterates the retrieved automated test\n    cases\n2.  JENKINS-9672 Test link custom field parser split the String value by\n    semicolon or comma.\n3.  JENKINS-9993 Add root element for JUnit test results\n\n### Release 2.2.2\n\n1.  FIXED-9444 - Add environment variables to single test command\n    (actually, I used some code from Jenkins core to execute both\n    commands now :-)\n\n### Release 2.2.1\n\n1.  French translation\n2.  Small issue with non-existent option Debug in Job configuration\n3.  FIXED-9229 - JUnit wrong status\n4.  Portuguese i18n messages typo\n\n### Release 2.2\n\n1.  JUnit BUG fix\n2.  Enhancement of the Build logs\n\n### Release 2.1\n\n1.  **Migration from Hudson to Jenkins**\n2.  Test transaction property.\n3.  i18n (version 1.0 supports only English).\n4.  Add Javascript validation functions to each field in the global and\n    config pages.\n5.  Add single test command feature (it will enable running test suites)\n6.  Fixed Java class headers\n7.  JFreechart graphics betterment\n8.  Fixed BUG JENKINS-8636 TestLink Plugin FATAL: Error creating test\n    project\n9.  Fixed BUG JENKINS-8531 Unexprssive error message\n\n### Release 2.0.1\n\n1.  Fixed BUG 8292 (java.lang.NullPointerException at\n    hudson.plugins.testlink.updater.TestLinkTestStatusUpdater.updateTestCases(TestLinkTestStatusUpdater.java:55)\n\n### Release 2.0\n\n1.  **Settings automated tests properties as environment variables.**\n2.  **Switch from dbfacade-testlink-java-api to testlink-java-api**\n    **\u003chttps://github.com/kinow/testlink-java-api\u003e.**\n3.  **JUnit parser.**\n4.  **TestNG parser.**\n5.  **TAP parser using tap4j**\n    **\u003chttp://tupilabs.com/tap4j/\u003e.**\n\n### Release 1.1\n\n1.  Execute Test Suites.\n2.  Let the user define the custom fields name.\n3.  Implement feature that lets user to use the latest revision from a\n    SVN repository as Build name.\n\n### Release 1.0\n\n1.  First version of the plug-in (the development was guided based on\n    the source code of the following plug-ins:\n    [CCM](http://wiki.jenkins-ci.org/display/HUDSON/CCM+Plugin \"CCM\") ,\n    [Sonar](http://wiki.jenkins-ci.org/display/HUDSON/Sonar+Plugin \"Sonar\")\n    (how to ref maven installations)).\n\n## Roadmap\n\n1.  Keep compatibility with latest versions of Jenkins and TestLink.\n2.  Add test case steps\n    ([JENKINS-10904](https://issues.jenkins-ci.org/browse/JENKINS-10904))\n\n## Open source licenses donated for this project\n\n[![](https://wiki.jenkins.io/download/attachments/46335320/stan4j-88x31-o1.png?version=1\u0026modificationDate=1301522276000\u0026api=v2)](http://stan4j.com/)\n\nYourKit is kindly supporting open source projects with its full-featured\nJava Profiler.  \nYourKit, LLC is the creator of innovative and intelligent tools for\nprofiling  \nJava and .NET applications. Take a look at YourKit's leading software\nproducts:  \n[YourKit Java Profiler](http://www.yourkit.com/java/profiler/index.jsp)\nand  \n[YourKit .NET Profiler](http://www.yourkit.com/java/profiler/index.jsp).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjenkinsci%2Ftestlink-plugin","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjenkinsci%2Ftestlink-plugin","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjenkinsci%2Ftestlink-plugin/lists"}