Add Playwright E2E Tests for Core Chatwoot User Flows 🧪

[ajith-k-v]

Summary

Introduce Playwright-based E2E tests to validate critical user flows.

---

Current State

• No E2E test suite in place
• API tests exist, but UI flows are not covered

---

Problems to Solve

• No automated coverage for critical UI workflows
• Manual testing overhead for core user flows

---

Proposed Solution

• Add Playwright as the E2E test runner
• Start with core user flows only
• Local execution initially

---

Phase 1

• Playwright setup
• Login flow automation

---

Phase 2

• Core UI flows (inbox, conversation, reply)

---

Phase 3

• External channel / social integrations

[sojan-official]

Thanks for putting this together.

As discussed on the call, let’s aim to ship this in the smallest possible units instead of bundling everything together.

Please use #13067 as a reference branch for structure and setup.

Let’s start with Phase 1:

• Playwright setup
• Login flow automation

For the PRs:

• Keep changes as small and focused as possible so they’re easy to review and test.
• Avoid mixing setup, refactors, and new flows in the same PR.
• Ensure each PR is independently testable.

It would also be helpful to add a short Loom video or screen recording for the team to fast-track reviews. The video can walk through:

• The setup process
• How to run the tests locally
• Your thought process behind the changes

We’ll follow up with more specific guidance directly on the respective PRs.