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 11 Next »

Plugin Information

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


This Plugin provides an interface to connect to Zermatt server and report test execution details.


  • Navigate to Manage Jenkins > Manage Plugins
  • Click Advanced tab
  • Upload automature-reporter.hpi file

Set Up

  • Navigate to Manage Jenkins > Configure System > Automature Plugin
  • Test Connection** Click on Test Connection to verify if the connection is established*.* On successful connection, the following message will be shown. See the figure below.                                                                                                                                                              

Create Job

After successfully connecting to Zermatt server, create a job and configure Automature Jenkins Plugin for reporting.

Steps Involved:

  • Click on New Item. See the figure below.
  • Enter an item name. See the figure below.


  • Select Freestyle project. Click OK. See the figure below.


Job created. For example:

DemoJob created as shown in the figure below.


Configure Job

Steps Involved:

  • Select *Invoke Automature Reporting* from *Add build step* dropdown list under Build. See the figure below.
  • Test Plan** Provide a {*}Test Plan{*} name where a test cycle will be created and test cases are reported.
    • The value of this field must contain a fully qualified TestPlan name preceded by the Product name separated by a dot(.). 
      • For example, if product name is DemoProduct and test plan name is DemoTestPlan then the value of this field should be: DemoProduct.DemoTestPlan
    • The product and testplan under consideration must exist in Zermatt. Create a new product and testplan if it does not exist.
  • Topologyset Description** Provide a {*}Topologyset Description.*
    • If {*}TopologySet Description{*} is omitted, then a default TopologySet is assigned for the given Test Plan.
    • The topology (machine participating in the test execution) must exist in Zermatt. Create a new topology if it does not exist.
    • The topology must be associated with an existing topology set.
  • Build Description** Provide a Build Description for product under consideration.
    • If {*}Build Description{*} is omitted then a default build is assigned.
  • Test Report** Provide name of the test execution report file path (.xml).
    • The file must exist in the project's workspace.
    • If the file name is TestReports.xml then the value of the field is the file name itself. If the file is located in a subdirectory called dir (at workspace) then the value of the field is dir/TestReports.xml.
    • The test report file, an xml file, must be in the following format as illustrated by the figure below.



  • Save configuration** Click on Apply and Save to save configuration.

Change Log

Version 1.0.1 (Sept 30, 2016)

  • First release, split off from the core.
  • No labels