[FEATURE] Provide Direct Azure Portal URL to Specific Playwright Test Run #35
Description
🌟 Is your feature request related to a problem?
The Azure Playwright reporting service generates a Report URL that always navigates to the list of test runs for a Playwright Workspace, rather than directly to the specific test run that produced the report.
When this URL is surfaced via CI/CD pipelines (for example in build logs, summaries, or notifications), users must manually locate the relevant test run in the Azure Portal. This adds friction and slows down investigation and troubleshooting.
Although a runId is available, the Azure Portal URL for an individual test run appears to rely on a long, opaque fragment (including encoded JSON state), making it impractical to construct or share a clean, stable direct link.
✅ Describe the solution you’d like
Provide a Report URL that deep-links directly to the specific Playwright test run associated with the report.
Ideally, this would be:
- A stable, supported Azure Portal URL format that includes a test run identifier (e.g.
runId), or - An alternative, documented mechanism for generating a direct link to a specific test run from CI/CD output.
This would allow users to click the Report URL and immediately view the relevant test run without additional navigation.
🔄 Describe alternatives you’ve considered
- Manually navigating from the test run list to the correct run in the Azure Portal.
- Attempting to reverse-engineer or capture the full Azure Portal URL for a specific run, which currently appears to depend on encoded portal state and is not suitable for reuse or automation.
Neither approach scales well for automated pipelines or shared reporting links.