Action interfaces
The action interfaces control an instance of the IWDTFTarget2 interface. Every plug-in must support this interface. All action interfaces inherit from IAction, either directly or indirectly.
You can retrieve an action interface for a target by calling the IWDTFTarget2::GetInterface method.
There are two sets of action interfaces: device action interfaces and system action interfaces.
Device Action Interfaces
| Interface | Description |
|---|---|
| IWDTFDriverPackageAction2 | Defines operations and properties that represent a driver package for imported and pre-imported driver packages. |
| IWDTFDriverSetupAction2 | Defines operations that control the target device during driver setup. |
| IWDTFEnhancedDeviceTestSupportAction2 | Defines operations and properties that support the Enhanced Device Test (EDT) filter driver. |
| IWDTFEnhancedDeviceTestSupportActions2 | Defines operations and properties that support the collection of Enhanced Device Test (EDT) actions. |
| IWDTFPNPAction2 | Defines operations and properties for the Plug and Play (PNP) device-related test interfaces. |
| IWDTFPNPActions2 | Defines operations and properties for the collection of Plug and Play (PNP) device-related test interfaces. |
| IWDTFSimpleIOEx2 | Defines operations for a simple synchronous I/O functionality test. |
| IWDTFSimpleIOStressAction2 | Defines operations for a simple asynchronous I/O functionality test. |
| IWDTFSimpleIOStressActions2 | Defines operations for a collection of simple asynchronous I/O functionality tests. |
System Action Interfaces
| Interface | Description |
|---|---|
| IWDTFDriverSetupSystemAction2 | Defines operations that control the system during driver setup. |
| IWDTFSystemAction2 | Defines operations and properties that support driver testing. |
Remarks
In WDTF, the IWDTFSimpleIOStressAction2 interface is implemented once as a wrapper around the numerous SimpleIO implementations.
SimpleIO can be easier to use directly, rather than through IWDTFSimpleIOStressAction2. This is because scenario code must keep a reference to each IWDTFSimpleIOStressAction2 instance that it starts, and remember to stop it before closing. However, because IWDTFSimpleIOStressAction2 runs asynchronously, it enables you to test combinations of events. For example, an IWDTFSimpleIOStressAction2 instance could start I/O testing for an extended period to test hardware sleep features.
Requirements
| Header |
|---|
| WDTFDriverPackageAction (Link Pending) |
| WDTFDriverSetupDeviceAction.h |
| WDTFInterfaces.h |
| WDTFEDTAction.h |
| WDTFPNPAction.h |
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for