| Name | Data Type | Qualifiers |
| Name | Data Type | Value | Scope | Flavors |
| HaltOnError | boolean |
| Description | string | When this flag is true, the test will halt after finding the first error. | None | TRANSLATABLE= true |
| Write | boolean | true | None | None |
| PercentOfTestCoverage | uint8 |
| Description | string | Requests 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 |
| MaxValue | sint64 | 100 | None | None |
| MinValue | sint64 | 0 | None | None |
| ModelCorrespondence | string | CIM_DiagnosticTest.Characteristics | None | None |
| Units | string | Percent | None | TRANSLATABLE= true |
| Write | boolean | true | None | None |
| QuickMode | boolean |
| Description | string | When 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 |
| Write | boolean | true | None | None |
| ReportSoftErrors | boolean |
| Description | string | When 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 |
| Write | boolean | true | None | None |
| ReportStatusMessages | boolean |
| Description | string | When 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 |
| Write | boolean | true | None | None |
| SettingID | string |
| Description | string | The identifier by which the DiagnosticSetting object is known and uniquely named. One possible naming scheme is to name the SettingID using the DiagnosticTest's CreationClassName and DiagnosticName, plus a GUID (Globally Unique IDentifier).
Note that at an enterprise level, there is typically not a one to one mapping between a DiagnosticSetting and all copies of the DiagnosticTest. The proposed naming convention willscale to the entrprise level. | None | TRANSLATABLE= true |
| Key | boolean | true | None | OVERRIDABLE= false
|
| MaxLen | uint32 | 256 | None | None |
| Override | string | SettingID | None | OVERRIDABLE= false
|
| TestWarningLevel | uint16 |
| Description | string | Sets 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 |
| Values | string | No Warnings, Missing Resources, Testing Impacts, All Warnings | None | TRANSLATABLE= true |
| Write | boolean | true | None | None |