Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Plugin Information

No information for the plugin 'testopia-plugin' is available. It may have been removed from distribution.

This plug-in integrates Jenkins and 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, 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-api 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.

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 Testopioa.

Testopia configuration section

Test Execution section

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.

Note that the $TESTOPIA_TESTCASE_ALIAS variable is used for naming the .tap file.

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_TEST_CLASS. In this case, Test Case is the name of a custom field in Testopia.

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

  • TESTOPIA_TESTCASE_ID
  • TESTOPIA_TESTCASE_SCRIPT
  • TESTOPIA_TESTCASE_ALIAS

TODO

  • TESTOPIA_TESTCASE_ALIAS
  • TESTOPIA_TESTCASE_AUTHOR
  • TESTOPIA_TESTCASE_SUMMARY
  • TESTOPIA_BUILD_ID
  • TESTOPIA_TESTPLAN_ID
  • TESTOPIA_ENVIRONMENT

For each Custom Field found, Testopia 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 %TESTOPIA_TESTCASE_TEST_CLASS% in Windows or $TESTOPIA_TESTCASE_TEST_CLASS in *nix-like systems.

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 formatsTestNGJUnit 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. 

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.

Feedback

Your feedback is very welcomed, but you don't need donate money. You can drop a message in [http://www.tupilabs.com] with suggestions and ideas (or even patches or pull requests).

Compatibility Matrix

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.

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

Plugin

1.0

1.1

 

 


 






Testopia

2.5

 

 






 



Jenkins

1.7+

 

 

 

 

 

 


 


 

Issues

Resources

  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. Sponsor company (until May 2011): Sysmap Solutions - Brazil.
  8. Sponsor company: TupiLabs - Brazil
  9. Presentation at STPCon Spring March 2012 in New Orleans - USA.

Sponsors

Release Notes

Release 1.1
  1. Execute Test Suites.
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 tested assigned doesn't execute.

  • No labels