fixup! fix(@angular/build): resolve test files correctly on Windows when using non-C drives

Author: clydin

tests/e2e/tests/vitest/windows-subst-drive.ts

@@ -1,7 +1,7 @@
 import assert from 'node:assert/strict';
 import * as fs from 'node:fs';
 import * as path from 'node:path';
-import { exec, silentExec } from '../../utils/process';
+import { execAndCaptureError, silentExec } from '../../utils/process';
 import { applyVitestBuilder } from '../../utils/vitest';
 
 export default async function (): Promise<void> {
@@ -33,9 +33,18 @@ export default async function (): Promise<void> {
     assert(fs.existsSync('angular.json'), 'angular.json should exist on the subst drive');
 
     // 3. Run `ng test`.
-    const { stdout } = await exec('ng', 'test', '--watch=false');
-
-    assert.match(stdout, /passed/, 'Expected tests to pass when running from a subst drive.');
+    // We expect this to fail with NG0203 in the subst environment due to dual-package hazards
+    // (Angular loading from both X: and D:). However, the failure proves that the test file
+    // was discovered and loaded.
+    const error = await execAndCaptureError('ng', ['test', '--watch=false']);
+    const output = error.message;
+
+    // Verify that Vitest found the test file and identified the tests within it.
+    assert.match(
+      output,
+      /src\/app\/app\.spec\.ts \(2 tests/,
+      'Expected tests to be discovered and loaded, even if execution fails due to subst aliasing.',
+    );
   } finally {
     // Teardown: Restore CWD and remove the virtual drive mapping.
     try {