Skip to content

Welcome to the Windows Protocol Test Suites v4.26.8.0 Release

Latest
Latest

Choose a tag to compare

View all tags
@anamikoye anamikoye released this 05 Aug 20:29
4.26.8.0
cbaf55b

Welcome to the Windows Protocol Test Suites v4.26.8.0 Release!

This release includes FileServer Test Suite v4.26.8.0 and PTMService v1.1.2.

Test Suites Prerequisites

See Prerequisites on GitHub for more information.

FileServer Test Suite v4.26.8.0

[NEW!] One-Click FileServer Deployment on Azure

Signed, credential-free deployment packages are now available for creating FileServer test
environments directly from the Azure Portal. Select the scenario that matches your environment:

Scenario Documentation Deployment
Workgroup Deployment guide Deploy to Azure
Domain Deployment guide Deploy to Azure

The release includes:

  • Workgroup-Package.zip — Signed DSC resources and scripts for provisioning a standalone FileServer workgroup test environment.
  • Domain-Package.zip — Signed DSC resources and scripts for provisioning an Active Directory domain-based FileServer test environment.

Cluster deployment continues to use the existing phased deployment workflow.

PTMService v1.1.2

[NEW!] Parallel FileServer Test Execution in PTMService

PTMService now supports optional staged parallel execution for the FileServer test suite when
Common.PTF.LogProfileParserPatch.Enabled is enabled.

Execution is organized into SMB2Model shards, SMB2, AppInstanceId, FSA/FSAModel, and remaining FileServer assemblies,
with up to five execution units running concurrently. Pipe handling, cancellation, result aggregation, and failure
reporting were updated to support concurrent test hosts reliably.

[NEW!] Live Test Case Logs

Test case logs can now be viewed in PTMService while a test run is still in progress.

Logs are correlated with individual test cases and retained until the corresponding result artifacts are available.
The test result UI automatically refreshes the selected test case during active runs.

[NEW!] Live Auto-Detection Logs

Auto-detection logs are now streamed incrementally to a responsive log panel while detection is running.

Each detection run has isolated state, cancellation, and logging. Run identifiers, log offsets, completion indicators,
and stale-response protection prevent output from previous detection runs from appearing in the current run.

Bug Fixes & Reliability

  • Fixed warning-level auto-detection messages not being written to detection logs
  • Fixed detected multi-value configuration properties not being persisted correctly
  • Made completed and failed detection-step logs accessible from the PTMService UI
  • Added protection against duplicate auto-detection starts and concurrent result application
  • Improved concurrent named-pipe connection handling and shutdown behavior
  • Improved cancellation and failure reporting for parallel test execution
  • Fixed PTMService React development-server compatibility with newer webpack-dev-server versions
  • Removed obsolete PTM test-logging infrastructure

Security

  • Bumped lodash from 4.17.23 to 4.18.1
  • Replaced MD5 with SHA-256 for Webpack persistent-cache environment hashing

Build & Infrastructure

  • Updated the PTMService frontend build system with explicit Webpack, Jest, TypeScript, and ESLint configuration
  • Added unit coverage for parallel execution plans, concurrent pipe connections, cancellation, test-host failures,
    configuration parsing, and live test logging
Assets 8
Loading