⭐⭐ 请加入 SambaXP 的 SMB3 IO Lab (2026 年 4 月 20 日至 23 日),查看即将举办的互操作性活动
⭐⭐ 请加入 SambaXP 的 SMB3 IO Lab (2026 年 4 月 20 日至 23 日),查看即将举办的互操作性活动
Windows Protocol Test Suites provide interoperability testing against the implementation of Windows open specifications including File Services, Identity Management, Remote Desktop and etc.
Originally developed for in-house testing of the Microsoft Open Specifications, Microsoft Protocol Test Suites have been used extensively during Plugfests and interoperability labs to test against partner implementations. A Test Suite evaluates whether a protocol or protocol family implementation meets certain interoperability requirements. Test Suites do not cover every protocol requirement and in no way certify an implementation, even if all tests pass. However, each test suite provides users with a useful indication of interoperability.
Windows Protocol Test Suites contain below components:
Windows Protocol Test Suites are based on .NET so they can be developed and run across different platforms. You should install the software listed below based on your testing purpose, including their own dependencies.
.NET and related components
a. For Windows, Linux and macOS, install .NET 8.0 SDK to build or run test suites.
b. For those who work on Windows and prefer IDE, install Visual Studio 2022 or higher (Visual Studio 2022 Community recommended), together with these individual components from the installer:
| Section | Individual Component in Visual Studio 2022 | Run Windows Protocol Test Suites | Build Windows Protocol Test Suites from source code |
|---|---|---|---|
| .NET | .NET SDK | Required | Required |
| Compilers, build tools, and runtime | C# and Visual Basic Roslyn compilers | Required | |
| Compilers, build tools, and runtime | MSVC v143 - VS 2022 C++ x64/x86 build tools (Latest) | Required1 | |
| Compilers, build tools, and runtime | C++/CLI support for v143 build tools (Latest) | Required1 | |
| Compilers, build tools, and runtime | C++ 2022 Redistributable Update | Required1 | Required1 |
| Development Activities | C++ core features | Required1 | |
| SDKs, libraries, and frameworks | Windows 10 SDK (10.0.19041.0) | Required1 |
Note:
[1]: This individual component is required by ADFamily and MS-SMBD which have C++ code.
Protocol Test Framework v2.6 (build 2.6.1)
Protocol Test Framework is referenced by projects of ProtoSDK and TestSuites as NuGet packages.
From NetworkDirect_DDK.zip extract ndspi.h and ndstatus.h into project path ProtoSDK\RDMA\include. This is to build SMBD test suite.
This is required only when user want to use PowerShell Core Remoting over SSH.
This is required only when user want to use PowerShell Core Remoting over SSH for Windows platform.
This is required only when user want to use PowerShell implementation on Windows Server 2012R2 for ISutCommonControlAdapter in CommonTestSuite.ptfconfig.
a. If you choose PowerShell implementation for ISutCommonControlAdapter in a domain environment where the DC runs Windows Server 2012R2, in order to get SID from the DC, you need to install WMF 5.1 on the DC, for other Windows Server versions newer than Windows Server 2012R2, you do not need to install WMF 5.1 on the DC.
b. If you choose PowerShell implementation for ISutCommonControlAdapter on Windows platforms (including Windows Server 2012R2 and newer versions) in workgroup environment, you do not need to install WMF 5.1 on the SUT.
c. If you choose managed implementation for ISutCommonControlAdapter on Windows platforms (including Windows Server 2012R2 and newer versions), it will use LDAP queries to get SID and only supports domain environment.
If your work on Windows, you can use the script in InstallPrerequisites folder to automatically download and install these software.
Tips when using the script in InstallPrerequisites folder:
The script requires internet connectivity to download some dependencies.
The parameter Category is used to specify which set of tools need to be downloaded and installed, based on the different test suite names, such as FileServer, Kerberos, SMBD, RDP, BranchCache, ADFamily, AZOD, ADFSPIP and ADOD. Categories are defined in PrerequisitesConfig.xml and you can update this configuration file to achieve your desired requirement.
The parameter ConfigPath is used to specify prerequisites configuration file path, default value is ".\PrerequisitesConfig.xml".
To run the script for the FileServer test suite, for example, open Windows PowerShell, and execute the commands below in the PowerShell Window:
cd WindowsProtocolTestSuites\InstallPrerequisites
.\InstallPrerequisites.ps1 -Category FileServer -ConfigPath ".\PrerequisitesConfig.xml"Set-ExecutionPolicy RemoteSignedYou could run the command below to verify if the Execution Policy is correctly set:
Get-ExecutionPolicyThen rerun the script.
After you clone a copy of this repo, you can run build.ps1 in PowerShell or build.sh in shell for each test suite separately after you have installed all the softwares required for build listed in Prerequisites.
For example, if you want to build FileServer test suite:
cd WindowsProtocolTestSuites\TestSuites\FileServer\src
build.ps1After the build succeeds, the common folder structure should be genera
暂无开放 Issues,或尚未同步最近议题。