Mai - E2E

[MathieuLamiot]

See main issue

[Mai-Saad]

• [x] Create your access to the remote desktop and access it with VNC: https://www.notion.so/wpmedia/Remote-desktop-on-OVH-0b03ec9321524c8facdbdb714443126e?pvs=4

• [x] Generate an SSH key for your remote desktop user and retrieve it locally: https://www.notion.so/wpmedia/Remote-desktop-on-OVH-0b03ec9321524c8facdbdb714443126e?pvs=4#126ed22a22f080689565ecfbff8fe30f

• [x] Add it to the E2E Wordpress server: ssh ubuntu@51.91.147.85 (to connect to E2E server) sudo nano .ssh/authorized_keys (to manage the list of authorized keys on this server).

• [x] Git clone Rocket-E2E repository on your remote desktop user in "Documents". cd Documents git clone https://github.com/wp-media/wp-rocket-e2e

• [x] Configure Rocket-E2E (config file + plugin zips). I recommend uploading your local conf and zips to the server via FTP and then, with SSH or VNC, copy those files into your rocket-e2e install on the remote desktop.

• [x] You might need to change the wp.config.ts for the SSH key location.

• [x] You might need to change ownership of the files. It is described on Notion as well. ==>using rocketftp so no need for this

• [x] Set up the installation with npm install and npx playwright (as explained here)

• [x] Connect to the remote desktop via VNC, open a terminal there and run npm run test:e2e (it takes ~1 hour)

• [x] Compare your HTML report with the reference one provided here. Once you are confident your E2E remote environment is set up properly; share the HTML report in the thread as well to allow the team to compare all of them later on and identify flaky tests.

[Mai-Saad]

Most of tests are failing https://wp-media.slack.com/archives/C05NH7JU4S2/p1730293029989699?thread_ts=1729513024.781269&cid=C05NH7JU4S2 @MathieuLamiot what do you think could be the problem here?

[MathieuLamiot]

@Mai-Saad, here is what I did:

• I checked using my remote desktop account + my e2e website that I did not face the same issue. So I confirm I don't have the issue.
• Then, I used my remote desktop account + mai.e2e website. I was able to reproduce the issue. It means the issue is from mai.e2e website.
• I checked that the steps here were done correctly and found out that this step (the chmod thing) was not done for mai.e2e as the permissions on the folder did not match those of other website folders. So I applied it.
• I restarted the test run from my remote desktop account with mai.e2e and I don't have the issue anymore.

I'll let you confirm.

[Mai-Saad]

@MathieuLamiot Thanks for the feedback, smoke test is all green now🎉