Fix storage service-version gates for all-version tests

[browndav-msft]

Description

Problem

RequiredServiceVersionExtension receives service versions in two different string representations:

• The all-versions test matrix sets AZURE_LIVE_TEST_SERVICE_VERSION to an enum name such as V2021_06_08.
• @RequiredServiceVersion annotations use the service wire value, such as "2026-02-06".

For example, QueueServiceAsyncApiTests.queueServiceGetUserDelegationKey, which requires "2026-02-06", while platform-matrix-all-versions.json includes runs configured with V2021_06_08.

The extension previously resolved both inputs by comparing them with String.valueOf(serviceVersion). Storage service-version enums do not override Enum.toString(), so that expression produces the enum name (V2026_02_06) rather than the wire value (2026-02-06).

Consequently, the required wire value could not be found and received ordinal -1 even though the value actual exists (see screenshots below):

The extension therefore enabled a test requiring service version 2026-02-06 during a V2021_06_08 matrix run instead of skipping it. Unknown versions also returned -1, allowing malformed annotations or configuration to fail open in the same way.

Fix

• Resolve each service version by either its explicit wire value (ServiceVersion.getVersion()) or its exact enum name (Enum.name()).
• Throw a descriptive exception for unknown minimum or configured versions instead of returning -1.
• Use the latest version's wire value when no environment version is configured.
• Add an injectable overload for deterministic unit testing while retaining the existing environment lookup for production test execution.

This does not change how x-ms-version is sent to Storage. The test infrastructure still converts the configured enum name to a ServiceVersion, and the client sends that enum's getVersion() value over the wire.

Testing

Added focused unit coverage for:

• Configured versions older than, equal to, and newer than the required version.
• Required wire values compared with configured enum names.
• The latest-version fallback.
• Unknown configured and minimum versions.

Validated with the focused RequiredServiceVersionExtensionTests, Spotless, and Checkstyle. The Maven test compilation covered both Java 8 and Java 21.

All SDK Contribution checklist

• The pull request does not introduce breaking changes.
• CHANGELOG is updated for new features, bug fixes or other significant changes. Not applicable because this only changes test infrastructure.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There is one commit with an informative message.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
34 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

This PR fixes the Storage test gating logic in RequiredServiceVersionExtension so that minimum required service versions declared as wire values (e.g., "2026-02-06") are correctly compared against configured versions that may be provided as enum names (e.g., V2021_06_08) in all-version test matrix runs.

Changes:

• Correctly resolve service versions by matching either ServiceVersion.getVersion() (wire value) or Enum.name() (enum name), rather than relying on toString().
• Fail closed by throwing a descriptive IllegalArgumentException when configured or minimum versions are unknown, instead of returning -1 and potentially enabling tests incorrectly.
• Add focused unit tests for ordering comparisons, latest-version fallback behavior, and unknown-version validation.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
sdk/storage/azure-storage-common/src/test-shared/java/com/azure/storage/common/test/shared/extensions/RequiredServiceVersionExtension.java	Fixes version resolution and comparison logic; adds injectable overload and throws on unknown versions.
sdk/storage/azure-storage-common/src/test/java/com/azure/storage/common/test/shared/extensions/RequiredServiceVersionExtensionTests.java	Adds unit coverage validating correct skip behavior across wire values, enum names, fallback, and unknown inputs.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[Isabelle (ibrandes)]

overall looks good! just a couple of small comments. good catch though!

[Isabelle (ibrandes)]

getOrdinal now throws IllegalArgumentException for both min and the configured version - throwing on min is good since it catches annotation typos. But we shouldn't throw on the configured version (AZURE_LIVE_TEST_SERVICE_VERSION), it's externally supplied and shared across services, so a name absent from one service's enum would turn every @RequiredServiceVersion test in that module into an error instead of running. we should keep the throw for min, but for the configured version fall back to "latest" (or skip) on an unknown value.

[Isabelle (ibrandes)]

we might want to add a comment explaining that both getVersion() (wire value, e.g. 2026-02-06) and name() (enum name, e.g. V2026_02_06) are accepted here (future refactor could tighten it to one format and silently break skipping again)