Unable to run playwright test cases in Microsoft edge in Incognito/private mode after Plywright Service Integration

[Dinesh2703]

In my local machine i set up palywright service and ran test case with persistent browser and test url without authentication.
But in Azure pipeline i cannot run test cases with persistent browser so i had to modify code and ran my test cases in incognito/private mode using edge browser. But its not able to open the test url for which i wrote test cases. Its giving timeout error.
The url is http and not https. I am trying to run in my local as well as in azure pipeline. Its giving same error i.e. timeout for test url.

Below is the screenshot of the error.

AB#1919606

[puagarwa]

HI @Dinesh2703 I am able to repro the issue. It seems like our browser infra is not able to load this DNS/IP. While I am working on fix for it. I have short term workaround to unblock you.

You can make this change in playwright.service.config.ts file, set exposeNetwork param to '' from current value of
exposeNetwork: ''

[Dinesh2703]

HI @Dinesh2703 I am able to repro the issue. It seems like our browser infra is not able to load this DNS/IP. While I am working on fix for it. I have short term workaround to unblock you.

You can make this change in playwright.service.config.ts file, set exposeNetwork param to '' from current value of exposeNetwork: ''

Hi @puagarwa
exposeNetwork:'_' did not work... but setting it to '*' worked.
there is one more issue.. after setting headless = false, its working but browser is not opening. Its still working on headless mode

[puagarwa]

HI @Dinesh2703 I am able to repro the issue. It seems like our browser infra is not able to load this DNS/IP. While I am working on fix for it. I have short term workaround to unblock you.
You can make this change in playwright.service.config.ts file, set exposeNetwork param to '' from current value of exposeNetwork: ''

Hi @puagarwa exposeNetwork:'_' did not work... but setting it to '*' worked. there is one more issue.. after setting headless = false, its working but browser is not opening. Its still working on headless mode

Sorry, i missed putting '*' thats correct. I looked into it further and actually the reason its not working from browser without exposeNetwork is because your endpoint is not opened to all public but it has network restriction. So either you stay with with exposeNetwork solution or we could provide you our IP range which you can whitelist if possible.

Coming back to headfull mode, thats expected that you wont see browser being opened in your machine since its remote browser. Hence using headful mode is not that meaningful if idea is to look at execution but rather trace and logs are more useful.

[Dinesh2703]

HI @Dinesh2703 I am able to repro the issue. It seems like our browser infra is not able to load this DNS/IP. While I am working on fix for it. I have short term workaround to unblock you.
You can make this change in playwright.service.config.ts file, set exposeNetwork param to '' from current value of exposeNetwork: ''

Hi @puagarwa exposeNetwork:'_' did not work... but setting it to '*' worked. there is one more issue.. after setting headless = false, its working but browser is not opening. Its still working on headless mode

Sorry, i missed putting '*' thats correct. I looked into it further and actually the reason its not working from browser without exposeNetwork is because your endpoint is not opened to all public but it has network restriction. So either you stay with with exposeNetwork solution or we could provide you our IP range which you can whitelist if possible.

Coming back to headfull mode, thats expected that you wont see browser being opened in your machine since its remote browser. Hence using headful mode is not that meaningful if idea is to look at execution but rather trace and logs are more useful.

ok @puagarwa if putting '*' is fine according to you then i will keep it like that. and i dont hv any problem with headless mode. i just wondered so i asked to confirm. Thanks @puagarwa

[puagarwa]

@Dinesh2703 Regarding exposeNetwork , its fine to use from feature standpoint when you have private endpoint not exposed publicly however, it does have some perf impact on test latency so we can evaluate and if we found its impacting your test latency then we can explore whitelisting service IP range. BTW, i am wondering you would have already whitelisted ADO IP range as this is accessible from ADO agents.

[puagarwa]

Closing this for now, let me know if you have more queries.