Examining the Result of Executing a Job

You can use Result Explorer to examine the result of executing a job. A result contains the start time, end time, and completion status of the job’s tasks, any error messages, a link to the job’s log files, and more detailed information. You can examine a job’s result while the job is executing or after it has completed. The following illustration shows an example of the Result Explorer window.

The Result Explorer** window**

When you execute a job, you can specify a result collection to hold the results of the job. By default, each time you execute a job, a new result collection is created. As the job executes, information about the job is added to a result that is part of the result collection. You can create your own result collections and move results from one collection to another collection. You can also delete or edit results.

Note  Although you can edit results, the changes that you make to the result will not affect the information if it is part of the logo submission package.

Four reports and logs are associated with each result that is displayed in the Result Explorer window:

1. Result report:  Detailed information about the execution of the job, including the values of parameters, task completion status, and pointers to any task logs. For more information about result reports, see Reviewing the Result Report.
2. Job report:  Descriptions of the parameters and tasks within the job. For more information about job reports, see Reviewing the Job Report.
3. Job log:  Any log files that were created by the tests that were run as part of the job. For more information about job logs, see Reviewing the Job Log.
4. Machine configuration log:  Detailed information about the dimensions of the computer that the job executed on. For more information about machine configuration logs, see Reviewing the Machine Configuration Logs.

To view the result of running a job

1.

2. Switch to the Result Explorer window.
   You can also open a new Result Explorer window by clicking Explorers, and then clicking Result Explorer.

3. Select your DTM controller from the drop-down box in the upper left of the Result Explorer window.

4. In the Feature tab, select the feature node that contains the jobs whose results you want to examine.
   All instances of jobs within the feature node that are executing or have finished executing are listed in the Results pane.

   Note  The jobs that you must execute to qualify for a “Designed for Microsoft Windows” logo are usually in a category that has the same name as the type of device or system that you are testing.

To interpret the information in the Results pane

1. The default columns in the Results pane include the following information:

2. The first column is unnamed and shows the following icons to indicate the status of the job that is associated with the result. ****

   • :  The job is executing.
   • :  The job has ended and passed.
   • :  The job has ended and failed.

3. Result Status:  One of the following values: ****

   • In Progress:  The job is executing.
   • Resolved:  The user can change the job’s status to “resolved” for any reason.
   • Investigate:  The client computer on which the job is executing has entered a debug state, or the job completed and failed.
   • Canceled:  The user canceled the job manually, or the job was defined to be canceled if it wasn’t executed within a specified amount of time.
   • Completed:  The job finished executing and passed.

4. Job Name:  The name of the job.

5. **Job Execution Type:  **One of the following values: ****

   • **Automated:  **The job executes automatically.
   • Manual:  The job requires manual intervention.

6. Assigned To:  The user name of the person who created the job.

7. **Pass:  **The number of tasks in the job that have ended with status ”Pass”. This value is not updated until the job has finished executing.

8. **Fail:  **The number of tasks in the job that have ended with status ”Fail”. This value is not updated until the job has finished executing.

9. Not Run: The number of tasks in the job that have not yet completed.

Send feedback on this topic
Built on December 10, 2009