...
Test configurations specify how Parasoft tools should execute their core features and functionality. They define the checkers that are enabled during code analysis, as well as configurations for checkers that support parameterization. Parasoft tools also ship with test configurations for executing unit tests, which specify how to instrument code for collecting coverage during test execution.
The following step are intended to help you refine your compliance plan and define the methods used to achieve compliance:
...
Use the default test configurations as starting points and adapt them to meet your specific needs. Some checkers, for example, will need to be parameterized based on your code. Some checkers may not be a good fit for your codebase and should be disabled. If you do not need to handle input validation, for example, you may want to disable a checker that reports a violation when input validation isn't handled in a manner that's consistent with the guideline.
Refer to the Parasoft tool documentation for additional information about the default security compliance test configurations included with the tools:
- Built-in Test Configurations#Compliance Packs
- Built-in Test Configurations#Security Pack
- Built-in Test Configurations#Security Pack
- Built-in Test Configurations#Security Compliance Pack
- Built-in Test Configurations#compliance_dottest
You can review the test configuration prior to execution and make some initial modifications, but fully understanding how to adjust the test configuration is an iterative process. Refer to the Updating Your Configuration section for information about modifying the test configuration.
...