Share via


AXE Results Manifest

The final results file is an XML file that describes the results produced by one or more AXE assessments. The AXE Results Manifest format describes one job. The AssessmentJobManifest node contains the entire job used to generate the results. This means that a reporting tool never needs to hunt down or find links to other sources of essential information such as meta information about metrics, or reporting hints. AXE adds all the information for the job to the final report file into the AssessmentJobManifest element of the AXE Results Manifest.

They key design goal for this schema is to put everything in one file that a reporting tool needs to generate reports. This means that a reporting tool never needs to hunt down or find links to other sources of essential information such as meta information about metrics, or reporting hints. Once aggregated the job result file is designed to be immutable – solutions should not modify a job results file after it has been created by AXE.

Elements that can be used in an AXE Result Manifest

Activities

Activity

ActivityClass

ActivityDescription

ActivityEndThread

ActivityEndTime

ActivityReference

ActivityStartThread

ActivityStartTime

ActivityTitle

AffectedMetrics

AnalysisLinks

AssessmentResult

AssessmentResults

AxeJob

AxeJobManifest

AxeJobResults

Build

Company

Description

Error

ErrorsAndWarnings

ExitCode

File

FileVersion

GUID

Hresult

Id

Impact

Issue

IssueDescription

IssueReference

Issues

IssueTitle

IssueToolTip

Iteration

Iterations

JobDuration

JobParameters

JobStartDateTime

Key

Link

LinkTitle

LinkToolTip

LinkURI

LogFile

LogFiles

MachineConfiguration

Major

Message

Meta

MetricReference

MetricThresholdValue

MetricValue

MetricValues

Minor

Name

Ordinal

Parent

Parents

ProgrammaticName

References

RelatedActivities

ResultsLocation

Revision

Solution

SolutionData

SolutionDescription

SolutionLinks

TestCase

TestCases

Trace

Value

Warning

AXE Results Schema At A Glance

 

 

Send comments about this topic to Microsoft

Build date: 9/27/2013