Page tree

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

Version 1 Next »

This topic describes how to connect all team Parasoft products to Parasoft Concerto as well as the Parasoft Concerto Report Center server. Among other things, Parasoft Concerto enables task management and allows teams to configure (or update) team-wide settings once, then have those settings propagated across the team’s Parasoft Test installations. Report Center correlates data sent from Parasoft Test to other quality and compliance data, providing visibility and control into the software development process and the products it is delivering.

Sections include:

Prerequisites

If your team is using Parasoft Report Center, at least one installation of Parasoft Test—your designated server machine that runs nightly tests—should be connected  (with reporting enabled).  

If your team is using Parasoft Concerto Project Center for task management—and/or if you are using Parasoft Concerto to share settings across products—you should also have all desktop installations connected.

Connecting to Parasoft Concerto

To connect a machine to Parasoft Concerto:

  1. Choose Parasoft> Preferences to open the Preferences dialog.
  2. Select the Parasoft> Concerto category in the left pane.
  3. If the appropriate Concerto information is not already set (from the auto-configuration process described in C++test Configuration Overview), select the desired server from the Auto detected servers list or enter connection details under the Server information area.
  4. Click the Configure button in the General Project area and select the Concerto project that you are currently working on.

General Project - Notes

When you enter a new project name, Report Center will automatically create a new project on the Concerto server and add a Test Group Properties Filter called "User-Attribute: Project". For example, if you type in the project name "Parabank 2.0", the project will be created in Concerto (when the first test results are received) and the "User-Attribute: Project" = "Parabank 2.0" key-value pair will be added in this project definition Test Group Properties Filter

When you click Find to locate an existing project, we recommend that you go into Report Center Administration, view the specific project definition, and ensure add the "User-Attribute: Project"  attribute is correctly set in the  Test Group Properties Filter. For example, for a project named
"Parabank 2.0", you should see a "User-Attribute: Project" = "Parabank 2.0" key-value pair in this project definition Test Group Properties Filter. These key-value pairs are automatically added for newly-created projects.

Connecting to Parasoft Report Center

To connect a machine to Parasoft Report Center:

  1. Choose Parasoft> Preferences to open the Preferences dialog.
  2. Select the Parasoft> Concerto> Report Center category in the left pane.
  3. If the appropriate Report Center is not already set (from the auto-configuration process described in C++test Configuration Overview), enter your Report Center’s host (either a name or an IP address) in the Host name field, then enter its port in the Port number field.
  4. (Optional) If you want results from this machine sent to Report Center, check the Enable test result reporting option.
    • Most teams connect only their Parasoft Test Server installation to Parasoft Report Center because they do not want their Parasoft Report Center reports and statistics to contain data from tests performed on developer desktops. However, Professional and/or Architect installations can also be configured to send data to Parasoft Report Center.
  5. (Optional) If you want Report Center to log results from this installation as the results from the nightly tests, check the Log results as nightly test run option.
    • If you enable this option, the test group sent to Concerto Report Center will have an additional key-value attribute pair: NIGHTLY=true .This attribute is not visible in Report Center reports, but it can be used in Test Group Properties Filter when defining a Concerto project.
  6. (Optional) If you want this machine to send only a brief summary report sent to Report Center, check the Send summary only option.
    • If you enable this option, only results summaries from static analysis and test execution (not individual violations) will be sent to Report Center.
  7. (Optional) Specify user-defined attributes as described in Configuring Parasoft Report Center Attributes below. Such attributes will be sent to Concerto along with test results; they  can be used to identify and filter results in Concerto.
  8. Click Apply.
  9. Click OK to set and save your settings.

Configuring Parasoft Report Center Attributes

Report Center attributes help you mark results in ways that are meaningful to your organization. Test group results sent to Concerto will contain:

  • Default attributes (for example, EXECUTION MODE=COMMAND-LINE is sent when tests run in command line mode; EXECUTION MODE=GUI is sent when tests are run in GUI mode; NIGHTLY=true is sent when the "Log results as nightly test runs" option is enabled).
  • Any custom attributes you  set in the Parasoft preferences panel (Concerto> Report Center page, Report Attributes area).

Both types of attributes can be used when defining a project in Concerto (you can access them in the Test Group Attributes Filter area).

For example, when you select "General Project" (for instance, "Parabank 2.0"), the attribute pair "User-Attributes: Project" = "Parabank 2.0" is sent to Concerto by default. You could also configure it to send additional attributes. For example, assume you define "milestone" = "beta" In that case, "User-Attributes: milestone" = "beta" is sent to Concerto in Test Group attributes.

Note for Long-Time Parasoft Users

In earlier versions of Parasoft products (e.g.,  Jtest 8.x, C++test 6.x) the "General Project" field did not exist. User attributes were used to match results to projects. This is no longer needed.

With the current versions, user attributes should be used only as auxiliary means to express "Nightly" or "Beta." Do not use them to express the exact Concerto project version; this should be set by choosing the appropriate "General Project."

Using the old style user attributes rather than choosing the appropriate General Project may prevent results from being properly assigned to the Concerto project.

Custom Report Center attributes can be specified in two ways:

  • Through the GUI.
  • Through localsettings.

To set general attributes (attributes that apply to all tests) through the GUI:

  1. Do one of the following:
    • If you want to set attributes that will be applied to all tests run by this installation, choose Parasoft> Preferences to open the Preferences dialog, then select the Parasoft> Concerto> Report Center category in the left pane.
    • If you want to set attributes that will be applied only to tests of a specific project or file, right-click the item(s) that you want to set Parasoft Report Center attributes for, then choose  Properties from the shortcut menu, then choose Parasoft> Report Center Attributes in the left pane.
  2. Use the available controls in the Attributes section to add or import Parasoft Report Center attribute settings. Each attribute contains two components: a general attribute category name and a specific identification value.
    • Example 1: If your group wants to label results by project names that are more specific than those used in the Parasoft Test project, you might use the attribute name PROJECT_NAME and the attribute value projname1. For the next project, you could specify an attribute with the attribute name PROJECT_NAME and the attribute value projname2.
    • Example 2: If your organization wants to label results by division, you might use the attribute name DIVISION and the attribute value division1 for all tests performed by your division. Another division could specify an attribute with the attribute name DIVISION and the attribute value division2.
    • Example 3: If your group wants to label results by project versions, you might use the attribute name VERSION and the attribute value 1.1. For the next project, you could specify an attribute with the attribute name VERSION and the attribute value 1.2.


For details on setting attributes through localsettings, see Configuring Localsettings

  • No labels