Skip to end of metadata
Go to start of metadata

Plugin Information

View Testopia on the plugin site for more information.

This plugin is up for adoption. Want to help improve this plugin? Click here to learn more!

This plug-in integrates Jenkins with Testopia and generates reports on automated test execution. With this plug-in you can manage your tests in Testopia, schedule and control in Jenkins, and execute using your favorite test execution tool (TestPartner, Selenium, TestNG, Perl modules, prove, PHPUnit, among others).

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 (smile)

Description

The Testopia plug-in integrates Jenkins with Testopia. Testopia plug-in uses testopia-java-driver to access Testopia XML-RPC API. With the information that you provide in the build step configuration the plug-in retrieves automated tests from Testopia. With the plug-in, you are able to execute build steps that call testing tools. It reads TestNGJUnit and TAP test report formats, used to update Testopia test cases' executions.

Testopia configuration section

Test Execution section

Result Seeking Strategy section

You can use environment variables. 

How does the plug-in execute my automated tests?

Testopia Plug-in retrieves automated test cases data from Testopia. 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 a ant command passing a Test Class as parameter, more or less something like this, /opt/java/apache-ant-1.8.0/bin/ant -DtestClass=$TESTOPIA_TESTCASE_SCRIPT. In this case, TESTOPIA_TESTCASE_SCRIPT the value of the script automation field in Testopia.

List of environment variables available during Testopia Plug-in execution:

Already implemented:
Test run info
  • TESTOPIA_TESTRUN_ID
  • TESTOPIA_TESTRUN_BUILD
  • TESTOPIA_TESTRUN_ENVIRONMENT
  • TESTOPIA_TESTRUN_MANAGER
  • TESTOPIA_TESTRUN_NOTES
  • TESTOPIA_TESTRUN_PRODUCT_VERSION
  • TESTOPIA_TESTRUN_SUMMARY
  • TESTOPIA_TESTRUN_CASES
  • TESTOPIA_TESTRUN_PLAN_ID
  • TESTOPIA_TESTRUN_PLAN_TEXT_VERSION
  • TESTOPIA_TESTRUN_RUN_ID
  • TESTOPIA_TESTRUN_STATUS
  • TESTOPIA_TESTRUN_TARGET_COMPLETION
  • TESTOPIA_TESTRUN_PLAN_TARGET_PASS
Test case info
  • TESTOPIA_TESTCASE_ID
  • TESTOPIA_TESTCASE_RUN_ID
  • TESTOPIA_TESTCASE_BUILD_ID
  • TESTOPIA_TESTCASE_SCRIPT
  • TESTOPIA_TESTCASE_ALIAS
  • TESTOPIA_TESTCASE_ARGUMENTS
  • TESTOPIA_TESTCASE_REQUIREMENT
  • TESTOPIA_TESTCASE_SORT_KEY
  • TESTOPIA_TESTCASE_SUMMARY
  • TESTOPIA_TESTCASE_AUTHOR_ID
  • TESTOPIA_TESTCASE_CATEGORY_ID
  • TESTOPIA_TESTCASE_DEFAULT_TESTER_ID
  • TESTOPIA_TESTCASE_PRIORITY_ID
  • TESTOPIA_TESTCASE_STATUS_ID
  • TESTOPIA_TESTCASE_AUTOMATED
  • TESTOPIA_TESTCASE_CREATION_DATE
  • TESTOPIA_TESTCASE_ESTIMATED_TIME
  • TESTOPIA_TESTCASE_ESTIMATED_ENV_ID

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 will support three result formatsTestNGJUnit and TAP

Already implemented:

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.

Does the plugin record the test results in Testopia?

Yes, the plugin will update the testcase in Testopia and set the status according to the result of the testcase.

Configuration

  1. Download and install the latest version of Testopia (http://www.mozilla.org/projects/testopia).
  2. Create automated tests in Testopia (Check automated field).
  3. Install the Testopia plug-in from the Jenkins Plugin Manager
  4. Define a Testopia configuration from the Configure System page.
  5. Add a Invoke Testopia build step in the job you want execute automated tests.
  6. Configure the required properties.

Languages Supported

  1. English (American)
  2. Dutch (the Netherlands)
  3. Portuguese (Brazil)

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.

Compatibility Matrix

We don't maintain the plug-in for Hudson. Issues happening in Hudson may not be fixed here.

Plugin

1.0

1.1

1.2

1.3 

Testopia

2.5+

2.5+

2.5+

2.5+

Jenkins

1.424+

1.424+

1.424+

1.424+

Issues

type key summary assignee reporter priority status resolution created updated due

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

Resources

Testopia Plug-in used TestLink Plug-in as basis. Below you will find resources for Testopia and TestLink plug-ins, as the concept in both plug-ins is very similar.

  1. Article published in Testing Experience magazine issue number 12 (Open Source Tools) written by Bruno P. Kinoshita and Anderson dos Santos. 2010.
  2. Slides used in the lighting talk presented at Encontro Ágil 2010 in IME-USP (Portuguese Only). 2010.
  3. Article published in Automated Software Testing Magazine, volume 3, issue 1. March, 2011.
  4. Slides used in the presentation done in Belgium Testing Days 2011.
  5. Lighting talk for Encontro Ágil 2010, at IME-USP.
  6. More articles and tips on Bruno P. Kinoshita's website.
  7. Presentation at STPCon Spring March 2012 in New Orleans - USA.
  8. Automated Testing Environment by Bugzilla, Testopia and Jenkins by Chin Pin Chang. July, 2014.

Documentation

  1. Various Testopia documentation assembled on Storify
  2. How to handle self signed certificates on Jenkins Server (TestLink Plugin SSL support)

Sponsors

Release Notes

Release 1.3
  1. JUnit and TestNG result seeking strategies
Release 1.0
  1. First version of the plug-in (the development was guided based on the source code of the following plug-ins: TestLink  CCM , Sonar (how to ref maven installations)).

Roadmap

  1. Keep compatibility with latest versions of Jenkins and Testopia.

Troubleshooting

  • A test case without a tester assigned doesn't execute.

1 Comment

  1. Is there a way to import test statuses that were executed manually and put it in jenkins test report?