Skip ResourceHealth tests that depend on Azure CLI profile absence

[chidozieononiwu]

What does this PR do?

Skip ResourceHealth tests that depend on Azure CLI profile absence when the profile is present

Pre-merge Checklist

• Required for All PRs
  • Read contribution guidelines
  • PR title clearly describes the change
  • Commit history is clean with descriptive messages (cleanup guide)
  • Added comprehensive tests for new/modified functionality
  • Created a changelog entry if the change falls among the following: new feature, bug fix, UI/UX update, breaking change, or updated dependencies. Follow the changelog entry guide
• For MCP tool changes:
  • One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
  • Updated servers/Azure.Mcp.Server/README.md and/or servers/Fabric.Mcp.Server/README.md documentation
  • Validate README.md changes running the script ./eng/scripts/Process-PackageReadMe.ps1. See Package README
  • For new or modified tool descriptions, ran ToolDescriptionEvaluator and obtained a score of 0.4 or more and a top 3 ranking for all related test prompts
  • For tools with new names, including new tools or renamed tools, update consolidated-tools.json
  • For renamed tools, follow the Tool Rename Checklist and tag the PR with the breaking-change label
  • For new tools associated with Azure services or publicly available tools/APIs/products, add URL to documentation in the PR description
• Extra steps for Azure MCP Server tool changes:
  • Updated command list in servers/Azure.Mcp.Server/docs/azmcp-commands.md
  • Ran ./eng/scripts/Update-AzCommandsMetadata.ps1 to update tool metadata in azmcp-commands.md (required for CI)
  • Updated test prompts in servers/Azure.Mcp.Server/docs/e2eTestPrompts.md
  • 👉 For Community (non-Microsoft team member) PRs:
    • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
    • Manual tests run: added comment /azp run mcp - pullrequest - live to run Live Test Pipeline

[Copilot]

Pull request overview

This PR updates Azure ResourceHealth unit tests to avoid failing in environments where an Azure CLI default subscription (or other default subscription source) is available, by conditionally skipping validation cases that expect missing --subscription to fail.

Changes:

• Added conditional Assert.SkipWhen(...) logic to subscription-missing validation scenarios.
• Introduced CommandHelper.GetDefaultSubscription() checks in ResourceHealth unit tests to detect presence of a default subscription.

Reviewed changes

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

File	Description
tools/Azure.Mcp.Tools.ResourceHealth/tests/Azure.Mcp.Tools.ResourceHealth.UnitTests/ServiceHealthEvents/ServiceHealthEventsListCommandTests.cs	Skips the “missing subscription” validation when a default subscription is available.
tools/Azure.Mcp.Tools.ResourceHealth/tests/Azure.Mcp.Tools.ResourceHealth.UnitTests/AvailabilityStatus/AvailabilityStatusGetCommandTests.cs	Skips the “missing subscription” validation when a default subscription is available; adds related usings.

Comments suppressed due to low confidence (1)

tools/Azure.Mcp.Tools.ResourceHealth/tests/Azure.Mcp.Tools.ResourceHealth.UnitTests/AvailabilityStatus/AvailabilityStatusGetCommandTests.cs:11

• using Microsoft.Mcp.Tests.Helpers; is not used anywhere in this test file. With warnings treated as errors in this repo, this will fail the build—please remove the unused using (or use the type you intended to reference).

using Microsoft.Mcp.Core.Helpers;
using Microsoft.Mcp.Core.Options;
using Microsoft.Mcp.Tests.Client;
using NSubstitute;
using NSubstitute.ExceptionExtensions;

[jongio]

Straightforward fix. The Assert.SkipWhen usage aligns with existing test patterns in the repo. The skip condition correctly fires only when CommandHelper.GetDefaultSubscription() returns a value, meaning the missing-subscription validation path is unreachable.

In ServiceHealthEventsListCommandTests, the !shouldSucceed && string.IsNullOrWhiteSpace(args) guard correctly targets only the empty-args case - the ("--subscription sub123", false) path tests missing --filter, not missing subscription, so it isn't affected.

No issues found. CI is still running.

[alzimmermsft]

Not the biggest fan of this change as it's just hiding a larger problem where we can't inject and substitute environment subscription retrieval in tests.

If we are going to make a change to skip these in this circumstance for now, can we make this a shared method in Microsot.Mcp.Tests so that when we do fix the larger problem we can delete / update the handling in one central spot.

[jongio]

Rebased cleanly. The refactoring to TestEnvironment.SkipIfDefaultSubscriptionConfigured() is a good improvement over inline Assert.SkipWhen - centralizes the logic and provides a clear skip message. No issues.