Tell about your experience setting up end-to-end testing with Playwright and covering 80% of tests.

To set up end-to-end testing with Playwright, I usually start with installing and configuring Playwright itself in the project using the command npm install -D @playwright/test.

Then, I create a basic test structure, for example, a folder tests/e2e, and write tests that cover main user scenarios: login, navigation, forms, UI interactions.

To achieve about 80% test coverage, it is important to:

• Analyze the most critical user paths and business logic.
• Write tests for different application states (success, errors, edge cases).
• Use Playwright features for parallel test execution and API mocking to speed up tests and make them more stable.

An example of a simple Playwright test:

const { test, expect } = require('@playwright/test');

test('Login verification', async ({ page }) => {
  await page.goto('https://example.com/login');
  await page.fill('#username', 'user1');
  await page.fill('#password', 'password123');
  await page.click('button[type=submit]');
  await expect(page).toHaveURL('https://example.com/dashboard');
});

It is also important to integrate tests into CI/CD so they run automatically on each code change. For coverage assessment, Playwright reports can be used, and additional code coverage analysis can be done with tools like Istanbul, although for e2e tests, this is not always straightforward.

In conclusion, setting up and maintaining e2e tests with Playwright requires a systematic approach, focusing on business value, and regularly updating tests as the application evolves.