Because C++test performs a thorough analysis of code, the initial tests often identify a large number of errors, potential errors, and items to review.
To ensure that C++test does not report an overwhelming number of tasks, the team manager can specify a reporting limit (such as "Do not report more than 25 static analysis tasks per developer per day") and/or a quality goal (such as "All static analysis violations should be fixed in 2 months"). C++test will then use the specified criteria to select a subset of testing tasks for each developer to perform each day. These goals are specified in the Goals tab. Progress towards these goals can then be monitored in reports.
Alternatively, you can set global team goals—goals that may span across multiple Test Configurations—as described in the Configuring Task Goals (Deprecated). If goals are set globally, the Goals tab in the Test Configuration panel will be disabled.
The Goals tab has the following settings:
Static tab
- Perform all tasks: Specifies that you want C++test to report all static analysis tasks it recommends, and the team should perform all static analysis tasks immediately.
- Don’t perform tasks: Specifies that you want C++test to report all static analysis tasks it recommends, but the team is not required to perform all static analysis tasks immediately. This is useful, for instance, if you want to see all recommended static analysis tasks, but you want the team to focus on fixing unit test problems before addressing static analysis violations.
- No more than n tasks per developer by date: Specifies that you want each developer to have only n static analysis tasks by the specified date.
- Max tasks to recommend: Limits the number of static analysis tasks reported for each developer on any test run. The tasks shown are selected randomly so that different tasks are shown after each run. For example, if you set the parameter to 50, the first task shown after each run is selected at random, and the following 49 tasks shown are the ones that would follow that first task in a complete report.
Execution tab
- Perform all tasks: Specifies that you want C++test to report all tasks for the specified category (fix unit test problems, etc.), and the team should perform the specified tasks immediately.
- Don’t perform tasks: Specifies that you want C++test to report all tasks for the specified category, but the team is not required to perform the specified tasks immediately. This is useful, for instance, if you want to see a list of all necessary unit testing tasks, but you want the team to focus on fixing unit test problems before performing other unit testing tasks.
- No more than n tasks per developer by date: Specifies that you want each developer to have only n tasks for the specified category by the specified date.
- Max tasks to recommend: Limits the number of category tasks reported for each developer on any test run. The tasks shown are selected randomly so that different tasks are shown after each run. For example, if you set the parameter to 50, the first task shown after each run is selected at random, and the following 49 tasks shown are the ones that would follow that first task in a complete report.
