E2E Deployment Test Failure: Aspire.Deployment.EndToEnd.Tests.TypeScriptJavaScriptHostingDeploymentTests.DeployTypeScriptStaticWebsiteWithNodeApiToAzureContainerApps

[mitchdenny]

Failing Test

Aspire.Deployment.EndToEnd.Tests.TypeScriptJavaScriptHostingDeploymentTests.DeployTypeScriptStaticWebsiteWithNodeApiToAzureContainerApps

Symptom

The test fails with:

System.InvalidOperationException : Command failed with non-zero exit code (detected ERR prompt at sequence 10).

The recorded terminal shows aspire deploy succeeding instantly (4/4 steps succeeded • Total time: 97ms) and then the verification step printing:

ERROR: (ResourceGroupNotFound) Resource group 'e2e-ts-js-hosting-<runid>-1' could not be found.
[ERR:1] $

Root Cause

After aspire init --language typescript --non-interactive, the test writes its custom AppHost content to apphost.ts in the workspace root:

https://github.com/microsoft/aspire/blob/main/tests/Aspire.Deployment.EndToEnd.Tests/TypeScriptJavaScriptHostingDeploymentTests.cs#L164

Since PR #16984 ("Use mts for TypeScript AppHosts"), aspire init --language typescript creates an apphost.mts in the workspace root. The custom apphost.ts written by the test is ignored; aspire deploy deploys the empty default apphost.mts, no resources are created, and the verification step fails because the resource group does not exist.

Fix

Write the custom AppHost content to apphost.mts instead of apphost.ts (overwriting the empty init file).

Affected Runs

• https://github.com/microsoft/aspire/actions/runs/26323258106 (2026-05-23)

This issue was created automatically by a workflow analyzing Deployment E2E test failures on main.

[joperezr]

🤖 Aspire triage pass — 2026-05-24 04:13 UTC

Area: area-polyglot, area-testing, area-deployment
Kind: test-failure
Repro: yes-minimal — root cause + fix identified in body; test source linked, suspected regressing PR #16984 cited
Affected version(s): main / 13.4-dev (latest: 13.3.x in market)
Severity: S3 — test-only break; production aspire init + apphost.mts path is working as intended, the test simply still writes apphost.ts.

Urgency: 🟡 vNext — recommend milestone 13.4
Reason: Clean test-only fix with a one-line code change ("write to apphost.mts instead of apphost.ts"), needs to land before 13.4 nightly E2E goes green. Not servicing-track: 13.3.x ships from a different branch where apphost.ts is still the convention, so this is not a regression vs. 13.2 in shipping bits.

Suggested owner(s): @sebastienros (score 5)
Evidence:

• sebastienros merged Unify ATS withReference exports #15238 in area-polyglot (only merged PR in the area in last 90d).
• CODEOWNERS lists @sebastienros for src/Aspire.Hosting.RemoteHost/** (polyglot host) and tests/Aspire.Hosting.Testing.Tests/**.
• Issue author (top area-deployment committer) is excluded per Rule S4.

Confidence: high
Needs human?: no

Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.