[Feature] codegen: choose between multiple generated selectors

[Meir017]

In some cases the generated selector isn't stable enough for rerunning the code.

Having multiple selectors per element could solve this, similar to how testim.io does this - https://help.testim.io/docs/working-with-locators#:~:text=Testim%20Smart%20Locators%20are%20a,application%20to%20write%20the%20tests.

[pavelfeldman]

The main goal of the codegen tool is to help users learn the Playwright API. We don't aim at creating re-runnable scripts that are production-ready. That's why we emit them into terminal rather than write into the live IDE. Having said that, it should be relatively easy for us to offer several version of the selector, preferring one aspect or the other for user to pick from.

The QA world is split on the self-healing topic (some prefer to assert behavior, others to keep test running in a best effort manner). We don't have an opinion on this matter, we consider this to be a higher-up-the-stack decision.

[rmallof]

Maybe another cool approach for this would be: https://playwright.dev/docs/selectors#selecting-elements-based-on-layout

[dgozman]

In v1.10, generated selectors overall work pretty good. If there are any specific instances where the selector is really bad, please file a separate issue with repro steps.

I am renaming this issue to be about generating multiple selectors and choosing one of them (as suggested in the original request).