[BUG]:Test Run Not Generating in Playwright Workspace

[Sathiyanarayanan-Rajamanickam]

When creating a Playwright instance or browser programmatically in the [Hooks] file of the C# BDD framework, the test run is not being generated in the Playwright Workspace. This issue occurs despite the connection to the Playwright service being established successfully.

Steps to reproduce the behavior
1 .Configure the Playwright Workspace with the required environment variables:
PLAYWRIGHT_SERVICE_URL
PLAYWRIGHT_SERVICE_ACCESS_TOKEN
2. Implement the BeforeScenario hook in the PlaywrightHooks.cs file to create a Playwright instance and browser programmatically.
Execute the test suite using the following command:
dotnet test .\Sample.csproj --settings .runsettings

Expected behavior
A test run should be created in the Playwright Workspace for each test execution.
The test run should include metadata such as the runId, test status, and timestamp

Actual Behavior
No test run is generated in the Playwright Workspace.
The Playwright service connection is established, and tests execute successfully, but the test run entry is missing.

Note
Framework Technology: C#, ReqNRoll, Nunit and Playwright

[puagarwa]

@Sathiyanarayanan-Rajamanickam Just to confirm that this behavior is happening on new Playwright workspace resource and not on old Microsoft playwright testing.

This is expected behavior if you are not using our package, since you are using c#, Nunit then we have package available which you can use, package will also help you use Entra Token auth instead of AccessToken.

Package: Azure.Developer.Playwright.NUnit
How to Guide: https://learn.microsoft.com/en-us/azure/app-testing/playwright-workspaces/quickstart-run-end-to-end-tests?tabs=playwrightcli&pivots=nunit-test-runner

Note: TestRun entry will be available in azure portal and not in old portal https://playwright.microsoft.com/

PS: If you have any reason not to use package and still wants to see testrun entry in portal, then you could manually integrate create test run API in your test project something like this https://github.com/Azure/playwright-workspaces/blob/main/samples/playwright-lib/src/example.ts#L29

Note: https://github.com/Azure/playwright-workspaces/issues is correct repo to track playwright workspace issues.

[Sathiyanarayanan-Rajamanickam]

Thanks, @puagarwa, for the quick response.

Yes, I am referring to Azure App Testing.

I want to use NUnit because of its BDD support, and I clearly understand why NUnit is not creating the test run automatically.

However, the Reporting API below works like magic—Thank you so much!

https://${region}.reporting.api.playwright.microsoft.com/playwrightworkspaces/${workspaceId}/test-runs/${runId}?api-version=${apiVersion}

[puagarwa]

@Sathiyanarayanan-Rajamanickam Glad it worked for you. We will improve our documentation for it.