Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Validation of each of the features described within this document and its associated texts is necessary in order to ensure that the solution you are developing will land in the hands of your customers with high quality. This section provides a set of recommendations on how to validate functionality and maximize quality.
There are 3 primary means of validation testing:
| Validation | Validation Method | Checklist |
|---|---|---|
| Wi-Fi Driver verification | Microsoft Hardware Lab Kit (HLK) | Required |
| Wi-Fi Interoperability Testing | Wi-Fi Alliance (WFA) Miracast testing | Strongly Recommended |
| Wireless Projection Stress Testing | Windows Wireless Projection Stress Lab and Testing | Strongly Recommended |
Wi-Fi Alliance (WFA) testing for Miracast
If you are either a Wi-Fi device manufacturer or a Miracast Receiver manufacturer you will want to ensure that, even if you do not intend to obtain certification of your device, you at least pass the WFA Wi-Fi CERTIFIED Miracast Test Plan tests to ensure a base level of interoperability with other devices in the ecosystem.
Windows Hardware Lab Kit (HLK) Validation
If you are a Wi-Fi device manufacturer then the Windows driver that you build for your device MUST be successfully validated through the Windows Hardware Lab Kit (HLK) tests. To support Miracast your device MUST pass the following suites of tests:
Microsoft.Test.Networking.Wireless.WiFiDirect.BasicDiscoveryTests.*
Microsoft.Test.Networking.Wireless.WiFiDirect.BasicPairingTests.*
Microsoft.Test.Networking.Wireless.WiFiDirect.BasicReconnectTests.*
Details on the Windows Hardware Lab Kit (HLK) can be found on the download page for the HLK.
Windows Stress automation
The testing that is performed above through the Windows HLK and WFA certification is necessary and foundational. These two methods of testing yield a guarantee that an implementation conforms to the protocols defined for Miracast. While this is necessary, it does not reflect the full interoperability complexity that is felt by users once they attempt to use Miracast in their own environments with their own hardware and software combinations.
In response to this, Windows has created a stress test environment that allows the automation of any Windows (PC) Source for the purpose of performing pairing and reconnection attempts to a given Miracast Receiver. The benefit of leveraging this stress setup and automation is that the automation will gather up any needed OS traces, over the air sniffer traces, and can be extended to include your own driver or firmware tracing. When a failure is captured using this automation all the collateral needed to diagnose the root cause of the failure is present in a single comprehensive package that is ready for debug analysis.
Partners who have been onboarded to the Microsoft Collaborate partner portal can download the Miracast stress tool package here:
Client | UTIL | Miracast | Miracast stress test automation toolkit
https://partner.microsoft.com/dashboard/collaborate/packages/7576
This package contains Miracast stress test tools and scripts to automate client / sink Miracast connection testing to help identify reliability issues.