Exercise 3: Viewing Reports in Microsoft Visual Studio 2010

In this exercise, you will learn how to access various reports available in Microsoft Visual Studio 2010.

1. Open Microsoft Visual Studio 2010 by going to Start | All Programs | Microsoft Visual Studio 2010 | Microsoft Visual Studio 2010 if it is not already open.

2. In Team Explorer, expand Tailspin Toys to open the Tests report folder (Tailspin Toys | Reports | Tests).

   Figure 1

   Locating test reports

3. You should see two reports in the Tests folder, Test Case Readiness and Test Plan Progress.
4. The Test Case Readiness report shows the state of preparation for test cases, including those that are ready to run.
5. The Test Plan Progress report helps track the progress of the overall test plan by showing the number of test cases that were ran, passed, failed, blocked, etc. For those test cases that were run, a state is assigned such as Aborted, Not Executed, PassedButRunAborted, NotRunnable, Disconnected, Timeout, etc.

6. In Team Explorer, locate and expand the Project Management report folder (Tailspin Toys | Reports | Project Management).

   Figure 2

   Multiple project management reports are available in Microsoft Visual Studio 2010

7. Double-click the Stories Overview report to open it. This report shows each user story and the development progress, acceptance tests, and number of bugs that have been filed against it.

   Figure 3

   Stories Overview report offers progress and related project information on each user story

8. In Team Explorer, locate and expand the Builds report folder (Tailspin Toys | Reports | Builds).

   Figure 4

   Builds reports show quality, success and summary information of each build

9. The Build Quality Indicators report shows test coverage, code churn, and bug counts for a specified build definition. You can use this report to help determine how close portions of the code are to being release quality.
10. The Build Summary report helps determine the status of each build. It shows a list of builds with test results, test coverage, code churn, and quality notes.
11. This Build Success Over Time report helps track changes in code quality and also shows the test results for the last build of each day.

Next Step

Exercise 4: Creating a Complex Query for Advanced Reporting