The Test Runner is expected to open in a new browser window when you select “Run for web application.”
If nothing opens, I would check these items first:
Allow pop-ups for dev.azure.com in Chrome. A blocked pop-up is a common reason the Test Runner window does not appear.
Make sure JavaScript is enabled in Chrome.
Try Microsoft Edge as a comparison test. Azure DevOps supports the browser-based Test Runner in supported browsers.
Sign out of Azure DevOps, close all browser windows, sign in again, and retry.
Try an InPrivate/Incognito window with extensions disabled. This helps identify whether another Chrome extension is interfering.
Verify the user has the required Azure DevOps access. Manual test execution requires Basic access, and appropriate project/test permissions are also required.
Check that the test case is selected from the Test Plans → Execute tab and that the user is selecting “Run for web application.”
If it still fails, check Chrome DevTools (F12) → Console and Network immediately after clicking the button and look for errors or blocked requests.
Also note that the Test & Feedback extension is separate from the browser-based Test Runner. The extension is primarily used for exploratory testing, while Test Runner is launched directly from Test Plans.
If the same test launches successfully in Edge but not Chrome, the next focus should be Chrome pop-up/extension/browser settings. If it fails in both browsers, provide the exact error from the browser console and confirm the user's Azure DevOps access level and project permissions.