Protocol Test Framework 2.5 (Build 2.5.0)

Welcome to the Windows Protocol Test Framework(PTF) release!

We're excited to announce that Protocol Test Framework 2.5.0 is available on Nuget.

Updates in this Release

The PTF supports .NET 6, .NET 7 and .NET 8.
The dependent PowerShell Core SDK is upgraded to version 7.4.1.
The dependent MSTest.TestFramework is upgraded to version 3.2.2.

Protocol Test Framework 2.4 (Build 2.4.0)

Welcome to the Windows Protocol Test Framework(PTF) release!

We're excited to announce that Protocol Test Framework 2.4.0 is available on Nuget.

Updates in this Release

• The PTF now supports both .NET 6 and .NET 7.
• The dependent PowerShell Core SDK is upgraded to version 7.3.3.
• The dependent MSTest.TestFramework is upgraded to version 3.0.2.

Protocol Test Framework 2.3 (Build 2.3.0)

Welcome to the Windows Protocol Test Framework(PTF) release!

We're excited to announce that Protocol Test Framework 2.3.0 is available on Nuget.

Updates in this Release

• The PTF now supports both .NET 5 and .NET 6.
• The dependent PowerShell Core SDK is upgraded to version 7.2.4.
• The dependent MSTest.TestFramework is upgraded to version 2.2.9.

Protocol Test Framework 2.2 (Build 2.2.0)

Welcome to the Windows Protocol Test Framework(PTF) release!

We're excited to announce that Protocol Test Framework 2.2.0 is available on Nuget.

Updates in this Release

• The PTF now supports the HTML Test logger.
• The PTF now supports to specifying a Timeout for the invoke Adapter method.
• The PipeSink now supports specifying pipe name.
• The dependent PowerShell Core SDK is upgraded to 7.1.3.

Protocol Test Framework 2.1 (Build 2.1.0)

Welcome to the Protocol Test Framework v2.1 (Build 2.1.0) release!

We're excited to announce that Protocol Test Framework 2.1.0 cross-platform support is available on Nuget.
 

Updates in this Release

• The PTF now supports Interactive Adapter and Shell Adapter.
• Logging is improved.
• The new PTF is migrated from .NET Core 3.1 to .NET 5.

Note

We have supported cross platform since PTF 2.0. For more details please refer to PTF 2.0 release note.
The development and release of the PTF based on .NET Framework has desisted. Protocol Test Framework version 1.0.7500.0 is the last version that supports the .NET Framework.
The previous version v1.0.7500.0 based on the .NET Framework cannot work with Test Suites after version v3.20.1.0. If you want to continue using a PTF version that supports the .NET Framework, you can use a previously released PTF version, or otherwise, contact us via a GitHub Issue for new features.

Protocol Test Framework 2.0 (Build 2.0.0)

Welcome to the Protocol Test Framework v2.0 (Build 2.0.0) release!

We're excited to announce that Protocol Test Framework 2.0.0 cross-platform support is available on Nuget, meaning that PTF now can run on Windows, Linux, and macOS operating systems.
 

What's New

• The PTF now is based on .NET core and supports cross-platform operating systems.
• The dependency on Spec Explorer no longer exists.
• The PTF is released as a NuGet package, which will be built within Test Suite binaries side-by-side.

Bug Fixing and Improvements

• AdapterProxyBase using DispatchProxy has been re-implemented.
• The PowerShell adapter has been re-implemented.
• The classes ProtocolTestsManager, TestClassBase, and PtfTestClassBase have been rewritten to remove the Spec Explorer dependency.
• The pass rate for Test Reports has been fixed.
• Unused functions and data structures have been cleaned from the project.
   

Features Migrated from Previous .NET Framework Version

The following are a subset of features migrated from PTF v1.0.7500.0 to PTF v2.0.0 which uses .NET Core v3.1:

• Default test environment
• PTF Configuration
• PowerShell Adapter
• Managed Adapter
• File Logging
• Console Logging
• Test validation and verification
   

Note

The development and release of the PTF based on .NET Framework has desisted. Protocol Test Framework version 1.0.7500.0 is the last version that supports the .NET Framework.
The previous version v1.0.7500.0 based on the .NET Framework cannot work with Test Suites after version v3.20.1.0. If you want to continue using a PTF version that supports the .NET Framework, you can use a previously released PTF version, or otherwise, contact us via a GitHub Issue for new features.

Protocol Test Framework 1.0 (Build 1.0.7500.0)

Welcome to the Protocol Test Framework v1.0 (Build 1.0.7500.0) Release!

This release provides two bug fixes of HTML Test Logger, as follows:

1. Escape special characters in the HTML log file, to avoid interpretation as HTML.
2. Enable the retrieval of test category information from a parameter internal to the TestResultHandler function, instead of obtaining it from dll files.

Protocol Test Framework 1.0 (Build 1.0.7000.0)

Welcome to the Protocol Test Framework v1.0 (Build 1.0.7000.0) release!

Prerequisites:

• .NET Framework 4.7.1
• Visual Studio 2017 or higher

For more information, see Prerequisites on Github.

This release provides support for the following features:

• Refactoring HTML test logger to support the exporting of additional test result details in Protocol Test Manager.
• Adding Visual Studio 2019 support along with corresponding prerequisite updates.

Protocol Test Framework 1.0 (Build 1.0.6500.0)

Welcome to the Protocol Test Framework v1.0 (Build 1.0.6500.0) release!

This release provides support for the following features:

• Shell adapter - you can now select the Shell adapter in Protocol Test Manager and remotely control the status of SUT computers through shell scripting.
• Html test logger - you can now specify the output folder for html test logger.

This release deprecates the following feature:

• Script adapter - if you use the Script adapter in Protocol Test Manager, you are advised to switch to the PowerShell adapter instead.

Protocol Test Framework 1.0 (Build 1.0.6500.0) Beta

Welcome to the Protocol Test Framework v1.0 (Build 1.0.6500.0) Beta release!

This release provides support for the following feature:

• Shell adapter - you can now select the Shell adapter in Protocol Test Manager and remotely control the status of SUT computers through shell scripting.

This release deprecates the following feature:

• Script adapter - if you use the Script adapter in Protocol Test Manager, you are advised to switch to the PowerShell adapter instead.