Move /e2e -> /e2e-tests

e2e-tests/playwright/README.md

@@ -0,0 +1,61 @@
+## Local development
+
+#### 1. Start local server in a separate terminal.
+
+#### 2. Install dependencies and run the test.
+
+```
+# Install npm packages
+npm i
+
+# Install browser binaries as prompted if Playwright is just installed or updated
+# See https://playwright.dev/docs/browsers
+npx playwright install
+
+# Run specific test of all projects -- chrome, firefox, iphone and ipad.
+# See https://playwright.dev/docs/test-cli.
+npm run test -- login
+
+# Run specific test of a project
+npm run test -- login --project=chrome
+
+# Or run all tests
+npm run test
+```
+
+#### 3. Inspect test results at `/test-results` folder when something failed unexpectedly.
+
+## Updating screenshots is strictly via Playwright's docker container for consistency
+
+#### 1. Run docker container using latest focal version
+
+Change to root directory, run docker container
+
+```
+docker run -it --rm -v "$(pwd):/mattermost/" --ipc=host mcr.microsoft.com/playwright:v1.30.0-focal /bin/bash
+```
+
+#### 2. Inside the docker container
+
+```
+export PW_BASE_URL=http://host.docker.internal:8065
+cd mattermost/e2e/playwright
+
+# Install npm packages. Use "npm ci" to match the automated environment
+npm ci
+
+# Run specific test. See https://playwright.dev/docs/test-cli.
+npm run test -- login --project=chrome
+
+# Or run all tests
+npm run test
+
+# Update snapshots
+npm run test -- login --update-snapshots
+```
+
+## Page/Component Object Model
+
+See https://playwright.dev/docs/test-pom.
+
+Page and component abstractions are located at `./support/ui`. It should be first class before writing a spec file so that any future change in DOM structure will be done in one place only. No static UI text and fixed locator should be written in the spec file.