Thanks, @Aklapper. Much appreciated.

Yeah, seems so.

Thanks @srodlund 😊. Your comment made me elated! 😊😊

Hi @srodlund @apaskulin, I made some updates to my proposal. I would appreciate it if you could kindly review it once again.

Hi @srodlund, Thanks a lot for the feedback. It was really helpful.
I would work on improving the documentation as highlighted.

Thanks a lot for the feedbacks you gave, they were extremely helpful.

Hi @Aklapper, thanks a lot for the feedback.

Hi @zeljkofilipin, I would like to take up some of these tasks.

Perhaps the CI needs some cypress specific config? @Soham

In T250727#6072812, @AlQaholic007 wrote:

This issue can be resolved using the --no-sandbox flag. I am aware. What I am trying to understand is why doesn't it work without that flag?

In T250132#6068328, @AlQaholic007 wrote:

Im sorry I was bouncing around in incognito. I dont remember where I bumped into this or would have specified. However I feel before filling a ticket with Playwright, it would be worthwhile to first try what they have recommended. I dont think its an issue with Node.js version because Erbium release is for Node 12.x. A glance at their Docker repository would reveal so

This link here should be more relevant

https://github.com/microsoft/playwright/issues/1140

Additionally, I dug deeper to find this answer on stack overflow

I dug deeper to find this on stack overflow
@ThomasDondorf just a quick note for others, I resolved this, the problem was I was running playwright in a docker container build from node:Erbium and I did not have all the required dependencies

In T250132#6068009, @AlQaholic007 wrote:

In T250132#6057985, @Gbahdeyboh wrote:

I'm trying to run tests using playwright here.

All tests pass locally but fails on CI. I think there is something wrong with my configuration but don't seem to know what's wrong

Hey @Gbahdeyboh. It is most likely an issue with missing dependencies. @Jpita has had a discussion stating that if it were dependency issues on the CI, it would require another task. Let us see if it works once the dependencies are in place. If not then I plan to file a ticket on their Github

Same thing happened here.

I've tried both options, the first passes on my machine but fails on CI.

I'm trying to run tests using playwright here.

In T249450#6057931, @Jpita wrote:

try without using the same instance.
write different tests without clearing browser and cookies.

In T249450#6057927, @Jpita wrote:

are you quitting the browser between tests or using the same instance?

I've tried to make some changes but still get the same error.

In T249450#6053190, @AlQaholic007 wrote:

I guess try to insert a delay see if that works?

In T249450#6053168, @AlQaholic007 wrote:

Sometimes cypress runs too fast. Can you try to add an await between the tests and see if they work?

Hhhmmm, session hijacking seems more like we're trying to create a new session while one session hasn't ended.

In T249450#6053079, @AlQaholic007 wrote:

Hey @Gbahdeyboh this seems to be an issue with an environment variable on the CI. I had encountered a similar issue as well and maybe it has got to do with us clearing browser cookies....though not sure

So I didn't do anything to fix this earlier. I moved my cypress folder to the MediaWiki/tests folder and I didn't get the error anymore.

Yes, resolved!

In T249900#6046165, @zeljkofilipin wrote:

You can record video of test runs. That will show the problem. Also, if a test fails, the screenshot will be taken and saved in tests/selenium/log folder. Please upload a screenshot or a video of a failed test reproducing the problem.

• Selenium/How-to/Record videos of test runs
• Selenium/How-to/Run tests targeting Quibble

In T249900#6045511, @Ammarpad wrote:

The prompt is skipped if the logout request has token, otherwise, the user must confirm they wish to log out. It's a security measure.

https://phabricator.wikimedia.org/P10890

Oh, thanks @AlQaholic007

Also, I think the Micro tasks under T247843 are meant to get us prepared for the main task(T247843) itself right? So the main task requires a separate solution?

Task T247843 has Micro tasks. On completion, usually what I do is mention it in the comment under the same task.

@Aklapper This Is a solution to T247843 and not it's duplicate.

I have been able to complete this task here.