You can create a Test Configuration for triggering code reviews that can be used across multiple Parasoft code analysis and test execution tools. In this section:
If you want to maintain a separate code review process for each language (separate reporting, reviewer configurations, etc.), use separate Parasoft Test products for each language. In other words, if you want to maintain separate processes for C and Java, code reviews, use Jtest for Java code review and C++test for C code review.
This option is covered in the previous code review topics.
If you want to establish a centralized product-independent code review process for all language (e.g., with centralized reporting, reviewer configurations, etc.), create a Parasoft Test (product-independent) code review Test Configuration, then configure your Parasoft Test products to use that Test Configuration.
This option is discussed below.
On all team Parasoft Test installations that you want to configure or access the product-independent code review Test Configuration(s):
You can then create and share a cross-product Test Configuration as follows:
To use this test configuration from the GUI:
To use this test configuration from the command line:
xtestprefix before the name of the Test Configuration. For example: