Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space CPPTDESKDEV and version 10.4.2

...

Info
iconfalse
titleRelated Topics

Configuration Overview

Configuring a post-commit code review requires:

...

To run a Code Review scan from the command line interface, use a command such as:

...

that resembles the following:

cpptestcli -publishteamserver -config "team://xtest-codereview.properties" -resource

...

"my_resource" -localsettings C:\

...

tm\localsettings.properties

The following options are used here:

...

If you are using a localsettings file to override the settings specified in the UI, you can add -localsettings; for example:

...

cpptestcli -publishteamserver -config "team://xtest-codereview.properties" -resource

...

"my_resource"  -localsettings C:\

...

tm\localsettings.properties

...

iconfalse
titleUsing -config with parasofttestcli if you have multiple Parasoft products installed

If you have multiple Parasoft products installed and want to run tests using parasofttestcli (rather than the product-specific commands such as jtestcli, cpptestcli, etc.), be sure to add the name of the product after -config to specify which product’s Test Configuration you want to use. 

For example, to use parasofttestcli to run the SOAtest "Code Review" Team Test Configuration, you might use 

...

Notifications

After each Code Review scanner execution, the designated reviewers will then be alerted that code is ready for review. The reviewers can perform the review as described in Reviewers - Reviewing Code Modifications.

...

  • Establish a two-tiered notification system where both of the following occur:
    • IDE notifications alert each team member to review tasks. This is achieved by enabling the Notify me about new or updated reviews every [  ] minutes option.
    • The server emails summary report and send remainders to reviewers and monitors about pending code review tasks. Emails will be generated if you have the appropriate reporting options set. If you enable the Generate comprehensive report (includes all scanners) option, the report will include tasks from  all code review scans (pre-commit and post-commit). Otherwise, it will include only tasks from the current post-commit scan. For more details about configuring report generation from command line runs, see Generating Reports.
  • Identify any code changes that were committed to source control, but were not submitted for review using the pre-commit procedure.

...