From a9ac7f87d7fc4b3c53e27edbbabab5d77eaba030 Mon Sep 17 00:00:00 2001
From: Matthieu Riegler <kyro38@gmail.com>
Date: Mon, 23 Feb 2026 17:41:40 +0100
Subject: [PATCH] docs: mention browser mode debugging

---
 adev/src/content/guide/testing/debugging.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/adev/src/content/guide/testing/debugging.md b/adev/src/content/guide/testing/debugging.md
index 49012648e75..c40d0d463e8 100644
--- a/adev/src/content/guide/testing/debugging.md
+++ b/adev/src/content/guide/testing/debugging.md
@@ -15,6 +15,6 @@ Debugging in the default Node.js environment is often the quickest way to diagno
 
 ## Debugging in a browser
 
-Debugging with Vitest and [browser mode](/guide/testing/migrating-to-vitest#5-configure-browser-mode-optional) is not supported today.
+The same way you start a debugging session with in Node, you can use `ng test` with the `--debug` flag with Vitest and [browser mode](/guide/testing/migrating-to-vitest#5-configure-browser-mode-optional).
 
-<!-- Update this section when https://github.com/angular/angular-cli/issues/31652 is fixed>
+The test runner will start in debug mode and wait for you to open the browser devtools to debug the tests.