This topic explains why and how to run an initial static analysis and/or unit testing test and reduce what you consider to be "noise."

If you review/respond to results after the initial test, the results for subsequent tests will be focused on real problems, such as code that throws unexpected exceptions, previously-verified code functionality that changes unexpectedly, or code that violates your team’s designated coding policies. Subsequent tests will not report results for expected exceptions and static analysis violations that were reported in the initial run, then handled during the baselining process described below.

To run the initial test and reduce "noise":.

  1. Ensure that the code you want to test is available in an appropriate project
  2. If you have not already done so, develop and share custom Test Configurations that tailor testing to your project and environment.
  3. Develop and run command line interface commands for running your preferred Test Configuration(s).
  4. Verify that the test executed successfully.
  5. Import results into the GUI in any of the following ways:
  6. Review the reported static analysis violations reported.
  7. Discuss the violations with the team and modify settings as needed to focus results on static analysis violations that your team cares about.
  8. Review the reported unit testing tasks.
  9. Discuss the reported tasks with the team and respond to the findings to prepare for regression testing.
  10. Ensure that the project and test files are added to the team’s source control system.