[FEATURE]: E2E Tests Vitality frontend and frontend BO applications

[helabenkhalfallah]

✨ Description

Implement comprehensive end-to-end (E2E) tests for the Vitality frontend and frontend BO applications.

🚀 Motivation

E2E tests simulate real user interactions with the frontend, providing valuable feedback on the application's functionality, user experience, and overall stability. These tests help identify issues that might not be caught by unit or integration tests, such as UI inconsistencies, integration problems, and browser compatibility issues.

📝 Proposed Solution

• Framework Choice: Cypress vs Playwright
• Configuration
• Identify and prioritize critical user flows to test
• Tests Implementation
• Update WIKI documentation if needed

🔗 Relevant Links (if any)

• https://www.cypress.io/
• https://playwright.dev/
• https://www.lambdatest.com/blog/cypress-vs-playwright/

[maelaubert56]

🆚 Comparison between Cypress and Playwright

Criteria	Cypress	Playwright
Installation	Very easy, simple configuration	A bit more complex
Performance	Fast but limited to one browser per test	Very fast, cross-browser testing
Debugging	Excellent with time-travel, videos, and screenshots	Good, but with fewer debugging tools
Browser Support	Primarily Chrome, Electron (basic support)	Chrome, Firefox, Safari, and mobile browsers
Scenario Complexity	Less suited for multi-page or multi-domain scenarios	Highly suited for complex scenarios
Parallel Testing	Limited parallelization, requires external tools	Native parallelization, better performance
Ecosystem	More mature with lots of plugins	Younger, but rapidly growing

• Cypress seems to be a great choice for a simple and powerful solution for testing in a single browser environment. Playwright is better to test across multiple browser or execute more complex scenarios (multiple tabs and domains).
• Cypress only support Chrome while Playwright support many different browsers and mobile browsers