microsoft / microsoft/playwright

[Feature]: Save code output file when launching recorder App

Open
#41,564 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

feature-codegen P3-collecting-feedback
Dominant language
TypeScript
Stars
96.3k
Forks
6.5k
Avg merge
1d 6h
Merged PRs (30d)
180

Description

### 🚀 Feature Request

Playwright.ps1 codegen allows for an -output param to specify an automatic output file without user interaction on tha inspector UI save button.

Can we exend this function to the Recorder App and through page.PauseAsync() in Playwright-dotnet

### Example

Primarily in playwright-dotnet allow page.PauseAsync() to be overloaded with output parameter like so:

page.PauseAsync("./folderLocation/output.cs")

### Motivation

The functionality already exists n the recorder App this and is available in tools like playwright.ps1, the parameters just need to be extended out to the protocol validator to allow consuming tools to pass the param.

I currently have a need to pass this output via the Playwright .net libraries page.PauseAsync() method to enable automatic codegen file saving, which programatically inaccessable currently.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing page.PauseAsync() in the Playwright .NET API and the protocol validator used by the Recorder App. Check how the existing Playwright.ps1 -output parameter reaches codegen, then determine the corresponding path for an output parameter passed through page.PauseAsync(). Done means the Recorder App can save generated code automatically when launched through the .NET library, without using the inspector save button.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, typescript
Domain
api, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.