[BUG] No Option to use local Browser for debugging .NET/NUnit
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- csharp
- Domain
- testing-qa
Research direction
Start by inspecting the Azure.Developer.Playwright.NUnit package configuration and the TestRunParameters handling around UseCloudHostedBrowsers. Compare the GA behavior with the linked preview documentation and the existing local-debugging workaround. Done means a documented configuration path lets NUnit debugging use a locally installed Playwright browser without preprocessor directives.
Written by the indexing model from the issue text.
Description
🐞 Describe the bug
The new .NET/NUnit package Azure.Developer.Playwright.NUnit (v 1.0.0) does not provide any option to override the browser configuration to use a local browser for debugging. It always uses cloud hosted browsers even when debugging locally, which worked by default in the MPT platform.
As per the documentation, there was a configurable option available in the preview version of the library, to override this behavior via UseCloudHostedBrowsers setting in TestRunParameters, but for some reason it was removed in the GA release.
Can you please suggest/provide a configurable option to debug tests using a locally installed playwright browser? Currently we have to workaround it with preprocessor directive in the C#, but that's not a clean approach.
✅ Expected behavior
Should allow configurable setting to use Local Browser instead of a Cloud Browser for test debugging.
🔁 To reproduce
Steps to reproduce the behavior:
- Configure the app as per the sample provided for .NET/NUnit.
- Try debugging a test, the test starts execution in a cloud browser.
- There is no way to change this behavior without updating the code.
- Dominant language
- No language data
- Stars
- 14
- Forks
- 19
- Avg merge
- 1h 18m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/playwright-workspaces
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Azure/playwright-workspaces#43 · 1 comment ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/playwright-workspaces#34 · 2 comments ·
-
[FEATURE] Provide the option to update RUN-Status in Reporting APIMay be free again @puagarwa claimed this 300 days ago, and no pull request is open. Openenhancement
Azure/playwright-workspaces#33 · 2 reactions · 1 assignee ·
All issues in Azure/playwright-workspaces
Similar issues
-
agent-canvas bug priority:low ready-for-dev
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area:frontend bug FE P3
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
klasolsson81/jobbliggaren#2010 ·
Maintainers usually reply within 1 day
-
enhancement P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Toloka/tolokaforge#1776 ·
Maintainers usually reply within 1 day
-
from:ci priority:P0
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
spec-kitty/spec-kitty#5699 ·
Maintainers usually reply within 1 day