Class CIM_DiagnosticResult

When a DiagnosticTest Service is running, test results are reported using a DiagnosticResult object, or one of its subclasses. A DiagnosticTest may be running because its Service is Started or due to an invocation of the RunTest method. DiagnosticResults are related to their Test via an instance of the DiagnosticResultsForMSE association. For every running of DiagnosticTest, a new instance of DiagnosticResult, or one of it's subclasses should be created.

Class Hierarchy

CIM_DiagnosticResult

Direct Known Subclasses

None.

Class Qualifiers

NameData TypeValueScopeFlavors
DescriptionstringWhen a DiagnosticTest Service is running, test results are reported using a DiagnosticResult object, or one of its subclasses. A DiagnosticTest may be running because its Service is Started or due to an invocation of the RunTest method. DiagnosticResults are related to their Test via an instance of the DiagnosticResultsForMSE association. For every running of DiagnosticTest, a new instance of DiagnosticResult, or one of it's subclasses should be created.None TRANSLATABLE= true

Local Class Properties

NameData TypeQualifiers
NameData TypeValueScopeFlavors
DiagnosticCreationClassNamestring
DescriptionstringThe scoping Test's CreationClassName.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
MaxLenuint32256None None
PropagatedstringCIM_DiagnosticTest.CreationClassNameNone OVERRIDABLE= false
DiagnosticNamestring
DescriptionstringThe scoping Test's Name.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
MaxLenuint32256None None
PropagatedstringCIM_DiagnosticTest.NameNone OVERRIDABLE= false
DiagSystemCreationClassNamestring
DescriptionstringThe scoping Test's SystemCreationClassName.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
MaxLenuint32256None None
PropagatedstringCIM_DiagnosticTest.SystemCreationClassNameNone OVERRIDABLE= false
DiagSystemNamestring
DescriptionstringThe scoping Test's SystemName.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
MaxLenuint32256None None
PropagatedstringCIM_DiagnosticTest.SystemNameNone OVERRIDABLE= false
EstimatedTimeOfPerforminguint32
DescriptionstringEstimated number of seconds to perform the DiagnosticTest indicated by the DiagnosticCreationClassName and DiagnosticName properties. After the test has completed, the actual elapsed time can be determined by subtracting the TestStartTime from the TestCompletionTime. A similar property is defined in the association, DiagnosticTestForMSE. The difference between the two properties is that the value stored in the association is a generic test execution time for the Element and the Test. But, the value here (in DiagnosticResult) is the estimated time that this instance with the given settings would take to run the test. A CIM Consumer can compare this value with the value in the association DiagnosticTestForMSE to get an idea what impact their settings have on test execution.None TRANSLATABLE= true
ModelCorrespondencestringCIM_DiagnosticTestForMSE.EstimatedTimeOfPerformingNone None
UnitsstringSecondsNone TRANSLATABLE= true
ExecutionIDstring
DescriptionstringThe Unique identifier for an instance of DiagnosticResults.None TRANSLATABLE= true
KeybooleantrueNone OVERRIDABLE= false
MaxLenuint321024None None
HaltOnErrorboolean
DescriptionstringWhen this flag is true, the test will halt after finding the first error.None TRANSLATABLE= true
WritebooleantrueNone None
IsPackageboolean
DescriptionstringIf this property is TRUE, then this DiagnosticResult summarizes the results from the execution of a packaged set of DiagnosticTests. The Tests in the package can be identified by following the DiagnosticResultForTest association to the test and then using the DiagnosticTestInPackage aggregation. The individual Results can be broken out by instantiating DiagnosticResults for the individual lower level tests and aggregating into the 'summary' Result using the DiagnosticResultInPackage association.None TRANSLATABLE= true
OtherStateDescriptionstring
DescriptionstringWhen "Other" (value=1) is entered in the TestState property, OtherStateDescription can be used to describe the test's state.None TRANSLATABLE= true
ModelCorrespondencestringCIM_DiagnosticResult.TestStateNone None
PercentCompleteuint8
DescriptionstringThe percentage of the test that has executed thus far, if the TestState property is set to "In Progress" or the percentage of the complete test that was executed if the TestState property is set to any of the completed states ("Passed", "Failed" or "Stopped"). Final results may be based on less than 100% coverage due to the parameters defined in DiagnosticSetting (such as QuickMode, PercentOfTestCoverage or HaltOnError).None TRANSLATABLE= true
MaxValuesint64100None None
MinValuesint640None None
UnitsstringPercentNone TRANSLATABLE= true
PercentOfTestCoverageuint8
DescriptionstringRequests the diagnostic software to reduce test coverage to the specified percentage. For example, a hard drive scan test could be asked to run at 50%. The most effective way to accomplish this is for the test software to scan every other track, as opposed to only scanning the first half of a drive. It is assumed that the effectiveness of the test is impacted proportional to the percentage of testing requested. Permissible values for this property range from 0 to 100. This property may not be applicable to all tests. If it can be set for a test, the value 7 ("Supports PercentOfTestCoverage") should be entered into the DiagnosticTest's Characteristics array.None TRANSLATABLE= true
MaxValuesint64100None None
MinValuesint640None None
ModelCorrespondencestringCIM_DiagnosticTest.CharacteristicsNone None
UnitsstringPercentNone TRANSLATABLE= true
WritebooleantrueNone None
QuickModeboolean
DescriptionstringWhen this flag is true, the test software should attempt to run in an accelerated fashion either by reducing the coverage or number of tests performed.None TRANSLATABLE= true
WritebooleantrueNone None
ReportSoftErrorsboolean
DescriptionstringWhen this flag is true, the diagnostic test will report 'soft errors'. In this context, a soft error is a message from the diagnostic reporting a known defect in the hardware or driver configuration, or execution environment. Examples are: "Not enough memory", "Driver IOCTL not implemented", "Video RAM compare failed during polygon fill test (A known defect in the video chipset)", etc.None TRANSLATABLE= true
WritebooleantrueNone None
ReportStatusMessagesboolean
DescriptionstringWhen this flag is true, the diagnostic test will report 'status messages'. In this context, a status message indicates that the diagnostic code is at a checkpoint. Examples are: "Completion of phase 1", "Complex pattern", etc.None TRANSLATABLE= true
WritebooleantrueNone None
TestCompletionTimedatetime
DescriptionstringThe date and time when this test completed.None TRANSLATABLE= true
TestStartTimedatetime
DescriptionstringThe date and time when this test started.None TRANSLATABLE= true
TestStateuint16
DescriptionstringDescribes how the test is progressing. For example, if the test was discontinued, the TestState will be "Stopped" (value=5), or if testing is currently executing, TestState will be "In Progress" (4).None TRANSLATABLE= true
ModelCorrespondencestringCIM_DiagnosticResult.OtherStateDescriptionNone None
ValuesstringUnknown, Other, Passed, Failed, In Progress, StoppedNone TRANSLATABLE= true
TestWarningLeveluint16
DescriptionstringSets the level of warning messages to be logged. If for example no warning information is required, the level would be set to "No Warnings" (value=0). Using "Missing Resources" (value=1) will cause warnings to be generated when required resources or hardware are not found. Setting the value to 2, "Testing Impacts", results in both missing resources and 'test impact' warnings (for example, multiple retries required) to be reported.None TRANSLATABLE= true
ValuesstringNo Warnings, Missing Resources, Testing Impacts, All WarningsNone TRANSLATABLE= true
WritebooleantrueNone None
TimeStampdatetime
DescriptionstringThe date and time the result was last updated.None TRANSLATABLE= true