[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FKXN5CAZXVPAS7T03AHZQC":3,"skill-same:01M6FKXN5CAZXVPAS7T03AHZQC":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6FKXN5CAZXVPAS7T03AHZQC","dashboard-testing",null,"Guide for writing tests for the Aspire Dashboard. Use this when asked to create, modify, or debug dashboard unit tests or Blazor component tests.","microsoft\u002Faspire","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6FKTZ7ND1S9JN6JTVK7A7MD",6426,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdashboard-testing\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"dashboard","dashboard testing","testing","blazor","when","component tests","debug dashboard","for","unit","tests","use","guide","writing tests","create","aspire dashboard","aspire","debug","unit tests","component","writing","2026-11-10 10:12:30",false,"---\nname: dashboard-testing\ndescription: Guide for writing tests for the Aspire Dashboard. Use this when asked to create, modify, or debug dashboard unit tests or Blazor component tests.\n---\n\n# Aspire Dashboard Testing\n\nThis skill provides patterns and practices for writing tests for the Aspire Dashboard. There are two test projects depending on whether the code under test uses Blazor types.\n\n## Test Project Selection\n\n| Project | Location | Use When |\n|---------|----------|----------|\n| **Aspire.Dashboard.Tests** | `tests\u002FAspire.Dashboard.Tests\u002F` | Testing code that does **not** use Blazor types (models, helpers, utils, OTLP services, middleware) |\n| **Aspire.Dashboard.Components.Tests** | `tests\u002FAspire.Dashboard.Components.Tests\u002F` | Testing code that **does** use Blazor types (pages, components, controls). Uses bUnit for in-memory rendering |\n\n### Dashboard Source Code\n\nThe dashboard source code is in `src\u002FAspire.Dashboard\u002F`. Key subdirectories:\n\n- `Components\u002F` — Blazor components (pages, controls, layout) → test in **Components.Tests**\n- `Model\u002F` — View models, data models, helpers → test in **Dashboard.Tests**\n- `Otlp\u002F` — OpenTelemetry protocol handling → test in **Dashboard.Tests**\n- `Utils\u002F` — Utility and helper classes → test in **Dashboard.Tests**\n\n## Aspire.Dashboard.Tests (Non-Blazor)\n\nStandard xUnit tests for models, helpers, utilities, middleware, and services that don't depend on Blazor rendering.\n\n### Project Structure\n\n```\ntests\u002FAspire.Dashboard.Tests\u002F\n├── Model\u002F                    # ViewModel and model tests\n├── Telemetry\u002F                # Telemetry repository tests\n├── ConsoleLogsTests\u002F         # Console log parsing tests\n├── Integration\u002F              # Integration tests (auth, OTLP, startup)\n├── Markdown\u002F                 # Markdown rendering tests\n├── Mcp\u002F                      # MCP service tests\n├── Middleware\u002F                # HTTP middleware tests\n├── FormatHelpersTests.cs     # Utility function tests\n├── DashboardOptionsTests.cs  # Configuration tests\n└── ...\n```\n\n### Test Pattern\n\n```csharp\nusing Xunit;\n\nnamespace Aspire.Dashboard.Tests;\n\npublic class FormatHelpersTests\n{\n    [Theory]\n    [InlineData(\"9\", 9d)]\n    [InlineData(\"9.9\", 9.9d)]\n    [InlineData(\"0.9\", 0.9d)]\n    public void FormatNumberWithOptionalDecimalPlaces_InvariantCulture(string expected, double value)\n    {\n        Assert.Equal(expected, FormatHelpers.FormatNumberWithOptionalDecimalPlaces(value, maxDecimalPlaces: 6, CultureInfo.InvariantCulture));\n    }\n}\n```\n\nKey points:\n- No bUnit, no DI container — direct construction and assertions\n- Use `[Fact]` for single test cases, `[Theory]` with `[InlineData]` for parameterized tests\n- Use `ModelTestHelpers.CreateResource(...)` from shared test utilities to build `ResourceViewModel` instances\n- Use hand-rolled fakes (e.g., `MockKnownPropertyLookup`) instead of mocking frameworks\n\n## Aspire.Dashboard.Components.Tests (Blazor\u002FbUnit)\n\nUses [bUnit](https:\u002F\u002Fbunit.dev) to render and test Blazor components in-memory without a browser.\n\n### Project Structure\n\n```\ntests\u002FAspire.Dashboard.Components.Tests\u002F\n├── Pages\u002F                    # Full page component tests\n│   ├── ResourcesTests.cs\n│   ├── ConsoleLogsTests.cs\n│   ├── MetricsTests.cs\n│   ├── StructuredLogsTests.cs\n│   ├── TraceDetailsTests.cs\n│   └── LoginTests.cs\n├── Controls\u002F                 # Individual control tests\n│   ├── ResourceDetailsTests.cs\n│   ├── PlotlyChartTests.cs\n│   ├── ChartFiltersTests.cs\n│   └── ...\n├── Interactions\u002F             # Interaction provider tests\n├── Layout\u002F                   # Layout component tests\n├── Model\u002F                    # Component model tests\n├── Shared\u002F                   # Setup helpers and test utilities\n│   ├── DashboardPageTestContext.cs\n│   ├── FluentUISetupHelpers.cs\n│   ├── ResourceSetupHelpers.cs\n│   ├── MetricsSetupHelpers.cs\n│   ├── StructuredLogsSetupHelpers.cs\n│   ├── IntegrationTestHelpers.cs\n│   ├── TestLocalStorage.cs\n│   ├── TestTimeProvider.cs\n│   └── ...\n└── GridColumnManagerTests.cs\n```\n\n### Base Test Class\n\nAll bUnit component tests must extend `DashboardTestContext`:\n\n```csharp\nusing Bunit;\n\nnamespace Aspire.Dashboard.Components.Tests.Shared;\n\npublic abstract class DashboardTestContext : TestContext\n{\n    public DashboardTestContext()\n    {\n        \u002F\u002F Increase from default 1 second as Helix\u002FGitHub Actions can be slow.\n        DefaultWaitTimeout = TimeSpan.FromSeconds(10);\n    }\n}\n```\n\n### Basic Component Test Pattern\n\n```csharp\nusing Aspire.Dashboard.Components.Tests.Shared;\nusing Aspire.Tests.Shared.DashboardModel;\nusing Aspire.Dashboard.Model;\nusing Bunit;\nusing Xunit;\n\nnamespace Aspire.Dashboard.Components.Tests.Controls;\n\n[UseCulture(\"en-US\")]\npublic class ResourceDetailsTests : DashboardTestContext\n{\n    [Fact]\n    public void Render_BasicResource_DisplaysProperties()\n    {\n        \u002F\u002F Arrange — register services using shared setup helpers\n        ResourceSetupHelpers.SetupResourceDetails(this);\n\n        var resource = ModelTestHelpers.CreateResource(\n            resourceName: \"myapp\",\n            state: KnownResourceState.Running);\n\n        \u002F\u002F Act — render the component\n        var cut = RenderComponent\u003CResourceDetails>(builder =>\n        {\n            builder.Add(p => p.Resource, resource);\n            builder.Add(p => p.ShowSpecOnlyToggle, true);\n        });\n\n        \u002F\u002F Assert — query the rendered DOM\n        var rows = cut.FindAll(\".resource-detail-row\");\n        Assert.NotEmpty(rows);\n    }\n}\n```\n\n### Page-Level Test Pattern\n\n```csharp\nusing System.Threading.Channels;\nusing Aspire.Dashboard.Components.Resize;\nusing Aspire.Dashboard.Components.Tests.Shared;\nusing Aspire.Dashboard.Model;\nusing Aspire.Dashboard.Tests.Shared;\nusing Bunit;\nusing Microsoft.Extensions.DependencyInjection;\nusing Xunit;\n\nnamespace Aspire.Dashboard.Components.Tests.Pages;\n\n[UseCulture(\"en-US\")]\npublic partial class ResourcesTests : DashboardTestContext\n{\n    [Fact]\n    public void UpdateResources_FiltersUpdated()\n    {\n        \u002F\u002F Arrange\n        var viewport = new ViewportInformation(IsDesktop: true, IsUltraLowHeight: false, IsUltraLowWidth: false);\n        var initialResources = new List\u003CResourceViewModel>\n        {\n            ModelTestHelpers.CreateResource(resourceName: \"Resource1\", resourceType: \"Type1\", state: KnownResourceState.Running),\n        };\n        var channel = Channel.CreateUnbounded\u003CIReadOnlyList\u003CResourceViewModelChange>>();\n        var dashboardClient = new TestDashboardClient(\n            isEnabled: true,\n            initialResources: initialResources,\n            resourceChannelProvider: () => channel);\n\n        ResourceSetupHelpers.SetupResourcesPage(this, viewport, dashboardClient);\n\n        \u002F\u002F Act\n        var cut = RenderComponent\u003CComponents.Pages.Resources>(builder =>\n        {\n            builder.AddCascadingValue(viewport);\n        });\n\n        \u002F\u002F Assert\n        Assert.Collection(cut.Instance.PageViewModel.ResourceTypesToVisibility.OrderBy(kvp => kvp.Key),\n            kvp => Assert.Equal(\"Type1\", kvp.Key));\n    }\n}\n```\n\n## Shared Setup Helpers\n\nDashboard services require extensive DI setup (telemetry, storage, localization, FluentUI JS interop mocks, etc.). Reuse existing shared setup methods to avoid duplicate registration logic. **When adding tests for a new area, add a new setup helper rather than duplicating setup across test classes.**\n\n### Setup Helper Index\n\n| Helper | Location | Purpose |\n|--------|----------|---------|\n| `FluentUISetupHelpers.AddCommonDashboardServices()` | `Shared\u002FFluentUISetupHelpers.cs` | Registers core DI services shared by all dashboard pages (localization, storage, telemetry, theme, dialog, shortcuts, etc.) |\n| `FluentUISetupHelpers.SetupFluentUIComponents()` | `Shared\u002FFluentUISetupHelpers.cs` | Calls `AddFluentUIComponents()` and configures the menu provider for tests |\n| `FluentUISetupHelpers.SetupDialogInfrastructure()` | `Shared\u002FFluentUISetupHelpers.cs` | Combines common services + FluentUI components + dialog provider JS mocks |\n| `FluentUISetupHelpers.SetupFluentDataGrid()` | `Shared\u002FFluentUISetupHelpers.cs` | Mocks FluentDataGrid JS interop |\n| `FluentUISetupHelpers.SetupFluentSearch()` | `Shared\u002FFluentUISetupHelpers.cs` | Mocks FluentSearch JS interop |\n| `FluentUISetupHelpers.SetupFluentMenu()` | `Shared\u002FFluentUISetupHelpers.cs` | Mocks FluentMenu JS interop |\n| `ResourceSetupHelpers.SetupResourcesPage()` | `Shared\u002FResourceSetupHelpers.cs` | Full setup for the Resources page |\n| `ResourceSetupHelpers.SetupResourceDetails()` | `Shared\u002FResourceSetupHelpers.cs` | Setup for ResourceDetails control |\n| `MetricsSetupHelpers.SetupMetricsPage()` | `Shared\u002FMetricsSetupHelpers.cs` | Full setup for the Metrics page |\n| `MetricsSetupHelpers.SetupChartContainer()` | `Shared\u002FMetricsSetupHelpers.cs` | Setup for chart container and Plotly |\n| `StructuredLogsSetupHelpers.SetupStructuredLogsDetails()` | `Shared\u002FStructuredLogsSetupHelpers.cs` | Setup for structured log details |\n| `IntegrationTestHelpers.CreateLoggerFactory()` | `Shared\u002FIntegrationTestHelpers.cs` | Creates `ILoggerFactory` wired to xUnit test output |\n\n### FluentUI JS Interop Mocks\n\nFluentUI Blazor components require JavaScript interop. bUnit runs without a browser, so all JS calls must be mocked. Use the helpers from `FluentUISetupHelpers`:\n\n```csharp\n\u002F\u002F Each FluentUI component has a corresponding setup method\nFluentUISetupHelpers.SetupFluentDataGrid(context);\nFluentUISetupHelpers.SetupFluentSearch(context);\nFluentUISetupHelpers.SetupFluentMenu(context);\nFluentUISetupHelpers.SetupFluentDivider(context);\nFluentUISetupHelpers.SetupFluentAnchor(context);\nFluentUISetupHelpers.SetupFluentKeyCode(context);\nFluentUISetupHelpers.SetupFluentToolbar(context);\nFluentUISetupHelpers.SetupFluentOverflow(context);\nFluentUISetupHelpers.SetupFluentTab(context);\nFluentUISetupHelpers.SetupFluentList(context);\nFluentUISetupHelpers.SetupFluentCheckbox(context);\nFluentUISetupHelpers.SetupFluentTextField(context);\nFluentUISetupHelpers.SetupFluentInputLabel(context);\nFluentUISetupHelpers.SetupFluentAnchoredRegion(context);\nFluentUISetupHelpers.SetupFluentDialogProvider(context);\n```\n\n### Adding a New Setup Helper\n\nWhen testing a new component area, create a dedicated setup helper in `Shared\u002F`:\n\n```csharp\n\u002F\u002F Shared\u002FMyFeatureSetupHelpers.cs\nusing Bunit;\nusing Microsoft.Extensions.DependencyInjection;\n\nnamespace Aspire.Dashboard.Components.Tests.Shared;\n\ninternal static class MyFeatureSetupHelpers\n{\n    public static void SetupMyFeaturePage(TestContext context, IDashboardClient? dashboardClient = null)\n    {\n        \u002F\u002F 1. Register common dashboard services\n        FluentUISetupHelpers.AddCommonDashboardServices(context);\n\n        \u002F\u002F 2. Setup FluentUI JS mocks for components used by the page\n        FluentUISetupHelpers.SetupFluentDataGrid(context);\n        FluentUISetupHelpers.SetupFluentSearch(context);\n        FluentUISetupHelpers.SetupFluentMenu(context);\n\n        \u002F\u002F 3. Register page-specific services\n        context.Services.AddSingleton\u003CIDashboardClient>(dashboardClient ?? new TestDashboardClient());\n        context.Services.AddSingleton\u003CIconResolver>();\n    }\n}\n```\n\n## Shared Test Fakes\n\nBoth test projects use hand-rolled fakes — no mocking framework is used. Cross-project fakes live in `tests\u002FShared\u002F` (e.g., `TestDashboardClient`, `ModelTestHelpers`), while bUnit-specific fakes live in `tests\u002FAspire.Dashboard.Components.Tests\u002FShared\u002F` (e.g., `TestLocalStorage`, `TestTimeProvider`).\n\n| Fake | Purpose |\n|------|---------|\n| `TestDashboardClient` | Configurable `IDashboardClient` with channel providers for resources, console logs, interactions, and commands |\n| `TestDialogService` | Fake dialog service |\n| `TestSessionStorage` | In-memory session storage |\n| `TestStringLocalizer` | Pass-through string localizer |\n| `TestDashboardTelemetrySender` | No-op telemetry sender |\n| `ModelTestHelpers.CreateResource()` | Factory for building `ResourceViewModel` instances with sensible defaults |\n\n### Using TestDashboardClient\n\n`TestDashboardClient` is constructor-configurable with channel providers:\n\n```csharp\nvar resourceChannel = Channel.CreateUnbounded\u003CIReadOnlyList\u003CResourceViewModelChange>>();\nvar consoleLogsChannel = Channel.CreateUnbounded\u003CIReadOnlyList\u003CResourceLogLine>>();\n\nvar dashboardClient = new TestDashboardClient(\n    isEnabled: true,\n    initialResources: [testResource],\n    resourceChannelProvider: () => resourceChannel,\n    consoleLogsChannelProvider: name => consoleLogsChannel);\n```\n\n### Using ModelTestHelpers\n\nCreate test resource view models with keyword arguments:\n\n```csharp\nusing Aspire.Tests.Shared.DashboardModel;\n\nvar resource = ModelTestHelpers.CreateResource(\n    resourceName: \"myapp\",\n    resourceType: \"Project\",\n    state: KnownResourceState.Running);\n```\n\n## Stock\u002Fbaseline dashboard verification\n\nUse this when verifying the installed\u002Freleased dashboard instead of the repo-local one.\n\n- In-repo playground AppHosts can add `Projects.Aspire_Dashboard` for local dashboard development. Running an installed `aspire` CLI is not enough when the AppHost model already contains that local project.\n- Use `SkipDashboardProjectReference=true` to opt out of the shared playground dashboard project reference, and point `AspireDashboardPath` at the installed bundle.\n\nRun `aspire doctor --format json --non-interactive` and use the first installation row, which represents the running CLI. Use `canonicalPath` together with `route` to locate its bundle root. If `canonicalPath` is absent, stop rather than guessing from `path`, which can be an unresolved package-manager symlink.\n\n| Installation route | Bundle root |\n| --- | --- |\n| `script`, `pr`, `localhive` | Parent of the directory containing `canonicalPath` |\n| `winget`, `brew`, `dotnet-tool` | Directory containing `canonicalPath` |\n| `nix`, other, or no sidecar | `ASPIRE_HOME` when set; otherwise `~\u002F.aspire` |\n\n```powershell\n$appHost = \"\u003Cpath-to-AppHost.csproj>\"\n$bundleRoot = \"\u003Cbundle-root-from-the-table>\"\n$managedExecutable = if ($env:OS -eq \"Windows_NT\") { \"aspire-managed.exe\" } else { \"aspire-managed\" }\n$dashboard = Join-Path $bundleRoot \"bundle\u002Fmanaged\u002F$managedExecutable\"\nif (-not (Test-Path $dashboard))\n{\n    throw \"Could not find the installed dashboard at '$dashboard'.\"\n}\n\ndotnet build $appHost \u002Fp:SkipDashboardProjectReference=true \"\u002Fp:AspireDashboardPath=$dashboard\"\n$env:ASPIRE_DASHBOARD_PATH = $dashboard\naspire run --no-build --apphost $appHost\nRemove-Item Env:ASPIRE_DASHBOARD_PATH\n```\n\n- Verify the dashboard resource in Aspire metadata\u002Flogs before treating the run as a stock baseline. Its resolved executable path must equal `$dashboard`, and its source must be `aspire-managed` (`aspire-managed.exe` on Windows), not `Aspire.Dashboard.csproj`.\n\n## Test Conventions\n\n### DO: Use `[UseCulture(\"en-US\")]` for Culture-Sensitive Component Tests\n\nApply `[UseCulture(\"en-US\")]` to bUnit test classes that assert culture-sensitive formatting (for example, numbers or dates) so those tests run deterministically across environments:\n\n```csharp\n[UseCulture(\"en-US\")]\npublic partial class ResourcesTests : DashboardTestContext\n```\n\n### DO: Reuse Shared Setup Methods\n\nCall existing helpers instead of duplicating DI registrations:\n\n```csharp\n\u002F\u002F DO: Use the shared helper\nResourceSetupHelpers.SetupResourcesPage(this, viewport, dashboardClient);\n\n\u002F\u002F DON'T: Duplicate service registration in every test class\nServices.AddSingleton\u003CTelemetryRepository>();\nServices.AddSingleton\u003CPauseManager>();\nServices.AddSingleton\u003CIDialogService, DialogService>();\n\u002F\u002F ... 20 more lines\n```\n\n### DO: Create New Setup Helpers for New Areas\n\nIf testing a new page or component area, add a setup helper in `Shared\u002F` to consolidate the setup:\n\n```csharp\n\u002F\u002F DO: Create a helper when multiple tests need the same setup\ninternal static class NewFeatureSetupHelpers\n{\n    public static void SetupNewFeaturePage(TestContext context) { ... }\n}\n\n\u002F\u002F DON'T: Copy-paste setup across test methods\n```\n\n### DO: Use `WaitForAssertion` for Async State Changes\n\nWhen component state updates happen asynchronously, use bUnit's `WaitForAssertion`:\n\n```csharp\ncut.WaitForAssertion(() =>\n{\n    var items = cut.FindAll(\".resource-row\");\n    Assert.Equal(3, items.Count);\n});\n```\n\n### DO: Use Channels to Simulate Real-Time Updates\n\nPush changes through channels to simulate dashboard data updates:\n\n```csharp\nvar channel = Channel.CreateUnbounded\u003CIReadOnlyList\u003CResourceViewModelChange>>();\nvar dashboardClient = new TestDashboardClient(\n    isEnabled: true,\n    initialResources: [],\n    resourceChannelProvider: () => channel);\n\n\u002F\u002F Render the component...\n\n\u002F\u002F Simulate an update\nchannel.Writer.TryWrite([\n    new ResourceViewModelChange(\n        ResourceViewModelChangeType.Upsert,\n        ModelTestHelpers.CreateResource(\"newResource\"))\n]);\n\n\u002F\u002F Wait for the UI to update\ncut.WaitForAssertion(() =>\n{\n    Assert.Equal(1, cut.FindAll(\".resource-row\").Count);\n});\n```\n\n### DO: Provide ViewportInformation for Responsive Components\n\nMany dashboard pages require viewport information:\n\n```csharp\nvar viewport = new ViewportInformation(IsDesktop: true, IsUltraLowHeight: false, IsUltraLowWidth: false);\n\n\u002F\u002F Set on DimensionManager\nvar dimensionManager = Services.GetRequiredService\u003CDimensionManager>();\ndimensionManager.InvokeOnViewportInformationChanged(viewport);\n\n\u002F\u002F Pass as cascading parameter\nvar cut = RenderComponent\u003CComponents.Pages.Resources>(builder =>\n{\n    builder.AddCascadingValue(viewport);\n});\n```\n\n### DON'T: Use Mocking Frameworks\n\nThe project uses hand-rolled fakes:\n\n```csharp\n\u002F\u002F DON'T: No mocking frameworks\nvar mock = new Mock\u003CIDashboardClient>();\n\n\u002F\u002F DO: Use the provided test fakes\nvar client = new TestDashboardClient(isEnabled: true, initialResources: resources);\n```\n\n### DON'T: Register Services Manually When a Helper Exists\n\n```csharp\n\u002F\u002F DON'T: Manual FluentUI setup\nvar module = JSInterop.SetupModule(\".\u002F_content\u002FMicrosoft.FluentUI...\u002FFluentDataGrid.razor.js\");\nmodule.SetupVoid(\"enableColumnResizing\", _ => true);\n\n\u002F\u002F DO: Use the helper\nFluentUISetupHelpers.SetupFluentDataGrid(this);\n```\n\n## Running Dashboard Tests\n\n```bash\n# Run non-Blazor dashboard tests\ndotnet test tests\u002FAspire.Dashboard.Tests\u002FAspire.Dashboard.Tests.csproj -- --filter-not-trait \"quarantined=true\" --filter-not-trait \"outerloop=true\"\n\n# Run Blazor component tests\ndotnet test tests\u002FAspire.Dashboard.Components.Tests\u002FAspire.Dashboard.Components.Tests.csproj -- --filter-not-trait \"quarantined=true\" --filter-not-trait \"outerloop=true\"\n\n# Run a specific test\ndotnet test tests\u002FAspire.Dashboard.Components.Tests\u002FAspire.Dashboard.Components.Tests.csproj -- --filter-method \"*.UpdateResources_FiltersUpdated\" --filter-not-trait \"quarantined=true\" --filter-not-trait \"outerloop=true\"\n```\n","# Aspire Dashboard Testing\n\nThis skill provides patterns and practices for writing tests for the Aspire Dashboard. There are two test projects depending on whether the code under test uses Blazor types.\n\n## Test Project Selection\n\n| Project | Location | Use When |\n|---------|----------|----------|\n| **Aspire.Dashboard.Tests** | `tests\u002FAspire.Dashboard.Tests\u002F` | Testing code that does **not** use Blazor types (models, helpers, utils, OTLP services, middleware) |\n| **Aspire.Dashboard.Components.Tests** | `tests\u002FAspire.Dashboard.Components.Tests\u002F` | Testing code that **does** use Blazor types (pages, components, controls). Uses bUnit for in-memory rendering |\n\n### Dashboard Source Code\n\nThe dashboard source code is in `src\u002FAspire.Dashboard\u002F`. Key subdirectories:\n\n- `Components\u002F` — Blazor components (pages, controls, layout) → test in **Components.Tests**\n- `Model\u002F` — View models, data models, helpers → test in **Dashboard.Tests**\n- `Otlp\u002F` — OpenTelemetry protocol handling → test in **Dashboard.Tests**\n- `Utils\u002F` — Utility and helper classes → test in **Dashboard.Tests**\n\n## Aspire.Dashboard.Tests (Non-Blazor)\n\nStandard xUnit tests for models, helpers, utilities, middleware, and services that don't depend on Blazor rendering.\n\n### Project Structure\n\n```\ntests\u002FAspire.Dashboard.Tests\u002F\n├── Model\u002F                    # ViewModel and model tests\n├── Telemetry\u002F                # Telemetry repository tests\n├── ConsoleLogsTests\u002F         # Console log parsing tests\n├── Integration\u002F              # Integration tests (auth, OTLP, startup)\n├── Markdown\u002F                 # Markdown rendering tests\n├── Mcp\u002F                      # MCP service tests\n├── Middleware\u002F                # HTTP middleware tests\n├── FormatHelpersTests.cs     # Utility function tests\n├── DashboardOptionsTests.cs  # Configuration tests\n└── ...\n```\n\n### Test Pattern\n\n```csharp\nusing Xunit;\n\nnamespace Aspire.Dashboard.Tests;\n\npublic class FormatHelpersTests\n{\n    [Theory]\n    [InlineData(\"9\", 9d)]\n    [InlineData(\"9.9\", 9.9d)]\n    [InlineData(\"0.9\", 0.9d)]\n    public void FormatNumberWithOptionalDecimalPlaces_InvariantCulture(string expected, double value)\n    {\n        Assert.Equal(expected, FormatHelpers.FormatNumberWithOptionalDecimalPlaces(value, maxDecimalPlaces: 6, CultureInfo.InvariantCulture));\n    }\n}\n```\n\nKey points:\n- No bUnit, no DI container — direct construction and assertions\n- Use `[Fact]` for single test cases, `[Theory]` with `[InlineData]` for parameterized tests\n- Use `ModelTestHelpers.CreateResource(...)` from shared test utilities to build `ResourceViewModel` instances\n- Use hand-rolled fakes (e.g., `MockKnownPropertyLookup`) instead of mocking frameworks\n\n## Aspire.Dashboard.Components.Tests (Blazor\u002FbUnit)\n\nUses [bUnit](https:\u002F\u002Fbunit.dev) to render and test Blazor components in-memory without a browser.\n\n### Project Structure\n\n```\ntests\u002FAspire.Dashboard.Components.Tests\u002F\n├── Pages\u002F                    # Full page component tests\n│   ├── ResourcesTests.cs\n│   ├── ConsoleLogsTests.cs\n│   ├── MetricsTests.cs\n│   ├── StructuredLogsTests.cs\n│   ├── TraceDetailsTests.cs\n│   └── LoginTests.cs\n├── Controls\u002F                 # Individual control tests\n│   ├── ResourceDetailsTests.cs\n│   ├── PlotlyChartTests.cs\n│   ├── ChartFiltersTests.cs\n│   └── ...\n├── Interactions\u002F             # Interaction provider tests\n├── Layout\u002F                   # Layout component tests\n├── Model\u002F                    # Component model tests\n├── Shared\u002F                   # Setup helpers and test utilities\n│   ├── DashboardPageTestContext.cs\n│   ├── FluentUISetupHelpers.cs\n│   ├── ResourceSetupHelpers.cs\n│   ├── MetricsSetupHelpers.cs\n│   ├── StructuredLogsSetupHelpers.cs\n│   ├── IntegrationTestHelpers.cs\n│   ├── TestLocalStorage.cs\n│   ├── TestTimeProvider.cs\n│   └── ...\n└── GridColumnManagerTests.cs\n```\n\n### Base Test Class\n\nAll bUnit component tests must extend `DashboardTestContext`:\n\n```csharp\nusing Bunit;\n\nnamespace Aspire.Dashboard.Components.Tests.Shared;\n\npublic abstract class DashboardTestContext : TestContext\n{\n    public DashboardTestContext()\n    {\n        \u002F\u002F Increase from default 1 second as Helix\u002FGitHub Actions can be slow.\n        DefaultWaitTimeout = TimeSpan.FromSeconds(10);\n    }\n}\n```\n\n### Basic Component Test Pattern\n\n```csharp\nusing Aspire.Dashboard.Components.Tests.Shared;\nusing Aspire.Tests.Shared.DashboardModel;\nusing Aspire.Dashboard.Model;\nusing Bunit;\nusing Xunit;\n\nnamespace Aspire.Dashboard.Components.Tests.Controls;\n\n[UseCulture(\"en-US\")]\npublic class ResourceDetailsTests : DashboardTestContext\n{\n    [Fact]\n    public void Render_BasicResource_DisplaysProperties()\n    {\n        \u002F\u002F Arrange — register services using shared setup helpers\n        ResourceSetupHelpers.SetupResourceDetails(this);\n\n        var resource = ModelTestHelpers.CreateResource(\n            resourceName: \"myapp\",\n            state: KnownResourceState.Running);\n\n        \u002F\u002F Act — render the component\n        var cut = RenderComponent\u003CResourceDetails>(builder =>\n        {\n            builder.Add(p => p.Resource, resource);\n            builder.Add(p => p.ShowSpecOnlyToggle, true);\n        });\n\n        \u002F\u002F Assert — query the rendered DOM\n        var rows = cut.FindAll(\".resource-detail-row\");\n        Assert.NotEmpty(rows);\n    }\n}\n```\n\n### Page-Level Test Pattern\n\n```csharp\nusing System.Threading.Channels;\nusing Aspire.Dashboard.Components.Resize;\nusing Aspire.Dashboard.Components.Tests.Shared;\nusing Aspire.Dashboard.Model;\nusing Aspire.Dashboard.Tests.Shared;\nusing Bunit;\nusing Microsoft.Extensions.DependencyInjection;\nusing Xunit;\n\nnamespace Aspire.Dashboard.Components.Tests.Pages;\n\n[UseCulture(\"en-US\")]\npublic partial class ResourcesTests : DashboardTestContext\n{\n    [Fact]\n    public void UpdateResources_FiltersUpdated()\n    {\n        \u002F\u002F Arrange\n        var viewport = new ViewportInformation(IsDesktop: true, IsUltraLowHeight: false, IsUltraLowWidth: false);\n        var initialResources = new List\u003CResourceViewModel>\n        {\n            ModelTestHelpers.CreateResource(resourceName: \"Resource1\", resourceType: \"Type1\", state: KnownResourceState.Running),\n        };\n        var channel = Channel.CreateUnbounded\u003CIReadOnlyList\u003CResourceViewModelChange>>();\n        var dashboardClient = new TestDashboardClient(\n            isEnabled: true,\n            initialResources: initialResources,\n            resourceChannelProvider: () => channel);\n\n        ResourceSetupHelpers.SetupResourcesPage(this, viewport, dashboardClient);\n\n        \u002F\u002F Act\n        var cut = RenderComponent\u003CComponents.Pages.Resources>(builder =>\n        {\n            builder.AddCascadingValue(viewport);\n        });\n\n        \u002F\u002F Assert\n        Assert.Collection(cut.Instance.PageViewModel.ResourceTypesToVisibility.OrderBy(kvp => kvp.Key),\n            kvp => Assert.Equal(\"Type1\", kvp.Key));\n    }\n}\n```\n\n## Shared Setup Helpers\n\nDashboard services require extensive DI setup (telemetry, storage, localization, FluentUI JS interop mocks, etc.). Reuse existing shared setup methods to avoid duplicate registration logic. **When adding tests for a new area, add a new setup helper rather than duplicating setup across test classes.**\n\n### Setup Helper Index\n\n| Helper | Location | Purpose |\n|--------|----------|---------|\n| `FluentUISetupHelpers.AddCommonDashboardServices()` | `Shared\u002FFluentUISetupHelpers.cs` | Registers core DI services shared by all dashboard pages (localization, storage, telemetry, theme, dialog, shortcuts, etc.) |\n| `FluentUISetupHelpers.SetupFluentUIComponents()` | `Shared\u002FFluentUISetupHelpers.cs` | Calls `AddFluentUIComponents()` and configures the menu provider for tests |\n| `FluentUISetupHelpers.SetupDialogInfrastructure()` | `Shared\u002FFluentUISetupHelpers.cs` | Combines common services + FluentUI components + dialog provider JS mocks |\n| `FluentUISetupHelpers.SetupFluentDataGrid()` | `Shared\u002FFluentUISetupHelpers.cs` | Mocks FluentDataGrid JS interop |\n| `FluentUISetupHelpers.SetupFluentSearch()` | `Shared\u002FFluentUISetupHelpers.cs` | Mocks FluentSearch JS interop |\n| `FluentUISetupHelpers.SetupFluentMenu()` | `Shared\u002FFluentUISetupHelpers.cs` | Mocks FluentMenu JS interop |\n| `ResourceSetupHelpers.SetupResourcesPage()` | `Shared\u002FResourceSetupHelpers.cs` | Full setup for the Resources page |\n| `ResourceSetupHelpers.SetupResourceDetails()` | `Shared\u002FResourceSetupHelpers.cs` | Setup for ResourceDetails control |\n| `MetricsSetupHelpers.SetupMetricsPage()` | `Shared\u002FMetricsSetupHelpers.cs` | Full setup for the Metrics page |\n| `MetricsSetupHelpers.SetupChartContainer()` | `Shared\u002FMetricsSetupHelpers.cs` | Setup for chart container and Plotly |\n| `StructuredLogsSetupHelpers.SetupStructuredLogsDetails()` | `Shared\u002FStructuredLogsSetupHelpers.cs` | Setup for structured log details |\n| `IntegrationTestHelpers.CreateLoggerFactory()` | `Shared\u002FIntegrationTestHelpers.cs` | Creates `ILoggerFactory` wired to xUnit test output |\n\n### FluentUI JS Interop Mocks\n\nFluentUI Blazor components require JavaScript interop. bUnit runs without a browser, so all JS calls must be mocked. Use the helpers from `FluentUISetupHelpers`:\n\n```csharp\n\u002F\u002F Each FluentUI component has a corresponding setup method\nFluentUISetupHelpers.SetupFluentDataGrid(context);\nFluentUISetupHelpers.SetupFluentSearch(context);\nFluentUISetupHelpers.SetupFluentMenu(context);\nFluentUISetupHelpers.SetupFluentDivider(context);\nFluentUISetupHelpers.SetupFluentAnchor(context);\nFluentUISetupHelpers.SetupFluentKeyCode(context);\nFluentUISetupHelpers.SetupFluentToolbar(context);\nFluentUISetupHelpers.SetupFluentOverflow(context);\nFluentUISetupHelpers.SetupFluentTab(context);\nFluentUISetupHelpers.SetupFluentList(context);\nFluentUISetupHelpers.SetupFluentCheckbox(context);\nFluentUISetupHelpers.SetupFluentTextField(context);\nFluentUISetupHelpers.SetupFluentInputLabel(context);\nFluentUISetupHelpers.SetupFluentAnchoredRegion(context);\nFluentUISetupHelpers.SetupFluentDialogProvider(context);\n```\n\n### Adding a New Setup Helper\n\nWhen testing a new component area, create a dedicated setup helper in `Shared\u002F`:\n\n```csharp\n\u002F\u002F Shared\u002FMyFeatureSetupHelpers.cs\nusing Bunit;\nusing Microsoft.Extensions.DependencyInjection;\n\nnamespace Aspire.Dashboard.Components.Tests.Shared;\n\ninternal static class MyFeatureSetupHelpers\n{\n    public static void SetupMyFeaturePage(TestContext context, IDashboardClient? dashboardClient = null)\n    {\n        \u002F\u002F 1. Register common dashboard services\n        FluentUISetupHelpers.AddCommonDashboardServices(context);\n\n        \u002F\u002F 2. Setup FluentUI JS mocks for components used by the page\n        FluentUISetupHelpers.SetupFluentDataGrid(context);\n        FluentUISetupHelpers.SetupFluentSearch(context);\n        FluentUISetupHelpers.SetupFluentMenu(context);\n\n        \u002F\u002F 3. Register page-specific services\n        context.Services.AddSingleton\u003CIDashboardClient>(dashboardClient ?? new TestDashboardClient());\n        context.Services.AddSingleton\u003CIconResolver>();\n    }\n}\n```\n\n## Shared Test Fakes\n\nBoth test projects use hand-rolled fakes — no mocking framework is used. Cross-project fakes live in `tests\u002FShared\u002F` (e.g., `TestDashboardClient`, `ModelTestHelpers`), while bUnit-specific fakes live in `tests\u002FAspire.Dashboard.Components.Tests\u002FShared\u002F` (e.g., `TestLocalStorage`, `TestTimeProvider`).\n\n| Fake | Purpose |\n|------|---------|\n| `TestDashboardClient` | Configurable `IDashboardClient` with channel providers for resources, console logs, interactions, and commands |\n| `TestDialogService` | Fake dialog service |\n| `TestSessionStorage` | In-memory session storage |\n| `TestStringLocalizer` | Pass-through string localizer |\n| `TestDashboardTelemetrySender` | No-op telemetry sender |\n| `ModelTestHelpers.CreateResource()` | Factory for building `ResourceViewModel` instances with sensible defaults |\n\n### Using TestDashboardClient\n\n`TestDashboardClient` is constructor-configurable with channel providers:\n\n```csharp\nvar resourceChannel = Channel.CreateUnbounded\u003CIReadOnlyList\u003CResourceViewModelChange>>();\nvar consoleLogsChannel = Channel.CreateUnbounded\u003CIReadOnlyList\u003CResourceLogLine>>();\n\nvar dashboardClient = new TestDashboardClient(\n    isEnabled: true,\n    initialResources: [testResource],\n    resourceChannelProvider: () => resourceChannel,\n    consoleLogsChannelProvider: name => consoleLogsChannel);\n```\n\n### Using ModelTestHelpers\n\nCreate test resource view models with keyword arguments:\n\n```csharp\nusing Aspire.Tests.Shared.DashboardModel;\n\nvar resource = ModelTestHelpers.CreateResource(\n    resourceName: \"myapp\",\n    resourceType: \"Project\",\n    state: KnownResourceState.Running);\n```\n\n## Stock\u002Fbaseline dashboard verification\n\nUse this when verifying the installed\u002Freleased dashboard instead of the repo-local one.\n\n- In-repo playground AppHosts can add `Projects.Aspire_Dashboard` for local dashboard development. Running an installed `aspire` CLI is not enough when the AppHost model already contains that local project.\n- Use `SkipDashboardProjectReference=true` to opt out of the shared playground dashboard project reference, and point `AspireDashboardPath` at the installed bundle.\n\nRun `aspire doctor --format json --non-interactive` and use the first installation row, which represents the running CLI. Use `canonicalPath` together with `route` to locate its bundle root. If `canonicalPath` is absent, stop rather than guessing from `path`, which can be an unresolved package-manager symlink.\n\n| Installation route | Bundle root |\n| --- | --- |\n| `script`, `pr`, `localhive` | Parent of the directory containing `canonicalPath` |\n| `winget`, `brew`, `dotnet-tool` | Directory containing `canonicalPath` |\n| `nix`, other, or no sidecar | `ASPIRE_HOME` when set; otherwise `~\u002F.aspire` |\n\n```powershell\n$appHost = \"\u003Cpath-to-AppHost.csproj>\"\n$bundleRoot = \"\u003Cbundle-root-from-the-table>\"\n$managedExecutable = if ($env:OS -eq \"Windows_NT\") { \"aspire-managed.exe\" } else { \"aspire-managed\" }\n$dashboard = Join-Path $bundleRoot \"bundle\u002Fmanaged\u002F$managedExecutable\"\nif (-not (Test-Path $dashboard))\n{\n    throw \"Could not find the installed dashboard at '$dashboard'.\"\n}\n\ndotnet build $appHost \u002Fp:SkipDashboardProjectReference=true \"\u002Fp:AspireDashboardPath=$dashboard\"\n$env:ASPIRE_DASHBOARD_PATH = $dashboard\naspire run --no-build --apphost $appHost\nRemove-Item Env:ASPIRE_DASHBOARD_PATH\n```\n\n- Verify the dashboard resource in Aspire metadata\u002Flogs before treating the run as a stock baseline. Its resolved executable path must equal `$dashboard`, and its source must be `aspire-managed` (`aspire-managed.exe` on Windows), not `Aspire.Dashboard.csproj`.\n\n## Test Conventions\n\n### DO: Use `[UseCulture(\"en-US\")]` for Culture-Sensitive Component Tests\n\nApply `[UseCulture(\"en-US\")]` to bUnit test classes that assert culture-sensitive formatting (for example, numbers or dates) so those tests run deterministically across environments:\n\n```csharp\n[UseCulture(\"en-US\")]\npublic partial class ResourcesTests : DashboardTestContext\n```\n\n### DO: Reuse Shared Setup Methods\n\nCall existing helpers instead of duplicating DI registrations:\n\n```csharp\n\u002F\u002F DO: Use the shared helper\nResourceSetupHelpers.SetupResourcesPage(this, viewport, dashboardClient);\n\n\u002F\u002F DON'T: Duplicate service registration in every test class\nServices.AddSingleton\u003CTelemetryRepository>();\nServices.AddSingleton\u003CPauseManager>();\nServices.AddSingleton\u003CIDialogService, DialogService>();\n\u002F\u002F ... 20 more lines\n```\n\n### DO: Create New Setup Helpers for New Areas\n\nIf testing a new page or component area, add a setup helper in `Shared\u002F` to consolidate the setup:\n\n```csharp\n\u002F\u002F DO: Create a helper when multiple tests need the same setup\ninternal static class NewFeatureSetupHelpers\n{\n    public static void SetupNewFeaturePage(TestContext context) { ... }\n}\n\n\u002F\u002F DON'T: Copy-paste setup across test methods\n```\n\n### DO: Use `WaitForAssertion` for Async State Changes\n\nWhen component state updates happen asynchronously, use bUnit's `WaitForAssertion`:\n\n```csharp\ncut.WaitForAssertion(() =>\n{\n    var items = cut.FindAll(\".resource-row\");\n    Assert.Equal(3, items.Count);\n});\n```\n\n### DO: Use Channels to Simulate Real-Time Updates\n\nPush changes through channels to simulate dashboard data updates:\n\n```csharp\nvar channel = Channel.CreateUnbounded\u003CIReadOnlyList\u003CResourceViewModelChange>>();\nvar dashboardClient = new TestDashboardClient(\n    isEnabled: true,\n    initialResources: [],\n    resourceChannelProvider: () => channel);\n\n\u002F\u002F Render the component...\n\n\u002F\u002F Simulate an update\nchannel.Writer.TryWrite([\n    new ResourceViewModelChange(\n        ResourceViewModelChangeType.Upsert,\n        ModelTestHelpers.CreateResource(\"newResource\"))\n]);\n\n\u002F\u002F Wait for the UI to update\ncut.WaitForAssertion(() =>\n{\n    Assert.Equal(1, cut.FindAll(\".resource-row\").Count);\n});\n```\n\n### DO: Provide ViewportInformation for Responsive Components\n\nMany dashboard pages require viewport information:\n\n```csharp\nvar viewport = new ViewportInformation(IsDesktop: true, IsUltraLowHeight: false, IsUltraLowWidth: false);\n\n\u002F\u002F Set on DimensionManager\nvar dimensionManager = Services.GetRequiredService\u003CDimensionManager>();\ndimensionManager.InvokeOnViewportInformationChanged(viewport);\n\n\u002F\u002F Pass as cascading parameter\nvar cut = RenderComponent\u003CComponents.Pages.Resources>(builder =>\n{\n    builder.AddCascadingValue(viewport);\n});\n```\n\n### DON'T: Use Mocking Frameworks\n\nThe project uses hand-rolled fakes:\n\n```csharp\n\u002F\u002F DON'T: No mocking frameworks\nvar mock = new Mock\u003CIDashboardClient>();\n\n\u002F\u002F DO: Use the provided test fakes\nvar client = new TestDashboardClient(isEnabled: true, initialResources: resources);\n```\n\n### DON'T: Register Services Manually When a Helper Exists\n\n```csharp\n\u002F\u002F DON'T: Manual FluentUI setup\nvar module = JSInterop.SetupModule(\".\u002F_content\u002FMicrosoft.FluentUI...\u002FFluentDataGrid.razor.js\");\nmodule.SetupVoid(\"enableColumnResizing\", _ => true);\n\n\u002F\u002F DO: Use the helper\nFluentUISetupHelpers.SetupFluentDataGrid(this);\n```\n\n## Running Dashboard Tests\n\n```bash\n# Run non-Blazor dashboard tests\ndotnet test tests\u002FAspire.Dashboard.Tests\u002FAspire.Dashboard.Tests.csproj -- --filter-not-trait \"quarantined=true\" --filter-not-trait \"outerloop=true\"\n\n# Run Blazor component tests\ndotnet test tests\u002FAspire.Dashboard.Components.Tests\u002FAspire.Dashboard.Components.Tests.csproj -- --filter-not-trait \"quarantined=true\" --filter-not-trait \"outerloop=true\"\n\n# Run a specific test\ndotnet test tests\u002FAspire.Dashboard.Components.Tests\u002FAspire.Dashboard.Components.Tests.csproj -- --filter-method \"*.UpdateResources_FiltersUpdated\" --filter-not-trait \"quarantined=true\" --filter-not-trait \"outerloop=true\"\n```\n",{"name":5,"description":7},"main","cec61ac9b795bbfd9913f0c7196689b0d7a215d7",".agents\u002Fskills\u002Fdashboard-testing",1039,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire","https:\u002F\u002Faspire.dev","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-15 00:32:23",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add microsoft\u002Faspire --skill dashboard-testing",{"tool":73,"command":74},"bunx","bunx skills add microsoft\u002Faspire --skill dashboard-testing",{"tool":76,"command":77},"pnpm","pnpm dlx skills add microsoft\u002Faspire --skill dashboard-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdashboard-testing\u002FSKILL.md",true,[],[82,111,135,147,164,190],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":95,"publishedAt":52},"01M6FKZQPMA7VRA0PRBZRDFJTX","vscode-extension","Use when investigating, developing, debugging, testing, or reviewing Aspire VS Code extension behavior under extension\u002F, including extension UI, command, debugger, RPC, DCP, MCP, and CLI-integration issues or features.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvscode-extension\u002FSKILL.md",[88,89,92],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":93,"categoryName":94,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",[96,97,98,34,99,100,47,101,102,103,104,105,106,107,108,109,42,110,36],"vscode","vscode extension","extension","MCP","cli","debugging","code","issues","rpc","ui","integration","debugger","command","behavior","features",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":120,"publishedAt":52},"01M6FKZJG81XP80SVWFBJVMDWN","update-container-images","Updates Docker container image tags used by Aspire hosting integrations. Queries registries for newer tags, uses LLM to determine version-compatible updates, and applies changes. Use this when asked to update container image versions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fupdate-container-images\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[121,122,123,124,125,126,127,47,128,42,129,130,131,132,133,39,134,36],"container images","update","container","images","update container images","image","docker","integrations","version","hosting","queries","tags","updates","changes",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":142,"publishedAt":52},"01M6FKZDY1MY0QA62EYSDG5NHW","test-management","Quarantines or disables flaky\u002Fproblematic tests using the QuarantineTools utility","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftest-management\u002FSKILL.md",[141],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[143,144,145,41,146],"test","management","test management","utility",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":52},"01M6FKZAQ428JX8F6NSA19XBQJ","startup-perf","Measures Aspire startup profiling with CLI self-profile capture and dashboard export traces.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstartup-perf\u002FSKILL.md",[],[154,155,156,100,32,47,157,158,159,160,161,162,163],"perf","startup","startup perf","profiling","capture","profile","export","self","with","traces",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":52},"01M6FKZ4W4J0ET0Q0C2Z30HYRV","reviewing-aspire-architecture","Use only when the user explicitly requests a deep Aspire architectural or pattern review of an existing PR or diff, or when a generic reviewer escalates a named Aspire-domain question it cannot resolve. Do not use for ordinary review, implementation, debugging, explanation, or design discussion—even when a PR is referenced—and never select it from changed file paths alone.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freviewing-aspire-architecture\u002FSKILL.md",[],[171,47,172,173,174,175,101,176,177,178,179,42,180,181,182,183,184,185,186,187,39,188,189,36],"architecture","reviewing aspire architecture","design","review","pr","file","select","reviewer","question","diff","never","only","do","domain","pattern","deep","paths","Existing","generic",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":197,"publishedAt":52},"01M6FKYZ44BEPJNV8VQ0X73CZR","pr-testing","Use when asked to test a microsoft\u002Faspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github\u002F and eng\u002F) and Azure DevOps pipelines (eng\u002Fpipelines, eng\u002Fcommon).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faspire\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpr-testing\u002FSKILL.md",[196],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[34,175,198,100,199,200,32,201,202,50,203,204,47,205,102,206,207,208,209,210,42,211,130,212,98,213,134,214],"pr testing","github","agentic","workflows","change","agentic workflows","azure devops","infrastructure","actions","ci","github actions","template","common","devops","pipelines","scripts","prs"]