Working with an imported QAC project

Once a Helix QAC project is converted into Validate tables, you can you can specify a target project to upload results to in the GUI or via the command line. You can browse the defects in the loaded project and cite them, similarly to the native Klocwork defects. However, there are some minor differences:

• A diagnostic can be 'suppressed' within the Helix QAC product using the usual supported methods such as adding a suppression annotation in the source code. All the suppressed diagnostics are still reported as defects.
• The state of the suppressed defect will be 'Open' instead of 'New', even if the defect is loaded for the first time.
• There is two-way synchronization (2023.1 or later) from your baseline project settings.
• If the diagnostic is suppressed with Helix QAC after the defect is cited in Validate, the defect status is determined by the suppression. Essentially, the portal shows the latest defect status, whether it comes from the portal or Helix QAC infrastructure. The intermediate changes are reflected in the status history.

The import tool also detects project rule configuration and converts it into a Klocwork problem configuration that is uploaded to the server alongside the rest of the project by validate admin load. By default in the portal configuration page, only configurations for native Klocwork checkers are shown.

You can import a rule configuration file (.rcf) into the portal using the Add a configuration file button. You can only manage QAC checker configurations using QAC tools. The QAC taxonomy and checker settings in Validate reflect the QAC configuration and provide a way to view the enabled/disabled states of checkers. The configuration tool only shows the configuration statuses.

You can use the loaded taxonomies for producing compliance reports from the Reports tab in the portal.