[Feature] Playwright codegen plugin system

[viktor-silakov]

Is it possible to create a plugin system so that you can add your own features? Specifically, I need to add a couple of buttons to this panel with an overlay to integrate with my visual testing tool:

I studied the sources and managed to do this in the playwright fork by changing several files:

But this solution is not very good because it is not extensible and in the future when updating I will not be able to use it.

What are the prospects for creating plugin features?

[TroubleZjb]

Same situation here. My team is seeking more sustainability of testing maintenance, as one way, we plan to use a locator function with fallback logic (for example, nth-child selector -> class selector -> by position -> byText).

For now, one solution is to fork playwright and patch the recorder code, whitch is not good for its stability over long term.

A plugin system maybe a better way to do that

[jan-molak]

It would be great if Playwright Codegen allowed external frameworks building on top of Playwright, like Serenity/JS, to generate code using framework-specific syntax.

This should be possible to accomplish if external frameworks were able to register their custom language generators.

I'd be happy to collaborate on this.

[kotosha-real]

My pain over the lack of a plugin system is based on two issues I need to address in my project:

1. Ability to take screenshots during codgen
2. Adding some stability improvements like waitForEvent() after the page is opened

This issue is now 6 months old, can you please tell me if this is something you will be working on in the near (2-3 months) future? Max Schmitt (@mxschmitt) tagging you as you placed the badge on my issue above

[jiwon-mun]

absolutely necessary 🥲🥲

[bhreinb]

Yeah I would be like to have the plugin system so to add support for other languages/frameworks that have an integration with Playwright but isn't necessarily supported by Playwright Codegen out of the box.

[ShaMan123]

I also have been interested in this for over a year.
I had to support canvas recording and a snapshot action

Currently I am using a fork.
That is very hard to maintain.

Playwright is great, IMO this is what is missing to make it the best.

[ShaMan123]

After some thought I believe this feature should follow the globalSetup scheme:
The consumer can specify a file that exports some convention for playwright to execute/use.
The consumer has access to the playwright package with codegen bindings that they can subclass/override and expose in the file back to playwright giving full control to the consumer and full responsibility as well, avoiding the need to design something that fits all cases.

I believe this makes a plugin system redundant and may expedite this feature into acceptance.
Hopefully it will reduce the scope to refactoring and exporting the necessary bindings.
IMO it sounds as an incremental and maintainable change after which it will be easier to navigate this feature.
I am willing to contribute.

Feedback is appreciated.

[autonomobil]

any updates here?

[UttamAaseri]

any plan to support this