You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Synthetics agent offers various configs, one of them is playwightOptions. This option is also relevant to the recorder and can be useful for users to emulate the browser in a certain way. For example, you'd like to script a mobile version of a website or want to emulate the locale. With the playwrightOptions being available in the recorder, users can set the viewport or set the locale to script the webpage with the target language(e.g. ko-KR).
Why is this feature important?
This is important as it will align the two products(synthetics agent & recorder) well so we can offer users a better experience when working with the two. We've had several feedback where the scripts generated by the synthetics recorder work well on the local machine, but when running it as a monitor the result is not the same as there are several factors that make the result different(for example, user-agent, or location). These discrepancies can be reduced if we have the ability to emulate certain options as the scripts will be running in more controlled settings.
Do we know how we'd apply the Playwright Options in the running browser (for the recording)? It's fine if we don't yet, I just wondered if there was an approach we had in mind here?
(Adding to the test feature is probably the easier part as it at least runs the script back through the Synthetics Agent so could apply the Playwright Options)
Oops, sorry I missed this. Most of the Playwright option seems to be used when launching chromium at first glance, so I thought we could do that when recorder launching the browsers when recording, and when running tests. I will take a closer look at it and leave my findings here.
Feature summary
Synthetics agent offers various configs, one of them is
playwightOptions
. This option is also relevant to the recorder and can be useful for users to emulate the browser in a certain way. For example, you'd like to script a mobile version of a website or want to emulate the locale. With theplaywrightOptions
being available in the recorder, users can set the viewport or set the locale to script the webpage with the target language(e.g. ko-KR).Why is this feature important?
This is important as it will align the two products(synthetics agent & recorder) well so we can offer users a better experience when working with the two. We've had several feedback where the scripts generated by the synthetics recorder work well on the local machine, but when running it as a monitor the result is not the same as there are several factors that make the result different(for example, user-agent, or location). These discrepancies can be reduced if we have the ability to emulate certain options as the scripts will be running in more controlled settings.
Linked resources
Elastic/Synthetics
suffix to user-agent string #350Additional information
No response
The text was updated successfully, but these errors were encountered: