Suggest an edit

Improve this article

Refine the answer for “What does an E2E test look like at the code level?”. Your changes go to moderation before they’re published.

Approval required

Content

What you’re changing

Title (EN)

Short answer (EN)

Shown above the full answer for quick recall.

Answer (EN)

An E2E test at the code level is a script that programmatically performs a sequence of actions the way a real user would in a browser, and then checks that the interface and the system as a whole produced the expected result.

## The structure of such a test

It usually has three parts:

1. **Environment setup**
Launching the browser, navigating to the needed URL, preparing data or state.
2. **Step-by-step simulation of user actions**
For example: clicking a button, typing text, selecting an element, navigating the page.
3. **Checking the result (assertions)**
Checking that the needed element is displayed, the state changed, the needed text appeared, a new page opened, etc.

## A mini example in Playwright

Here's what it looks like in code:

```js
test('user can log in', async ({ page }) => {
  await page.goto('https://site.com/login');
  await page.fill('#email', 'test@mail.com');
  await page.fill('#password', '123456');
  await page.click('button[type=submit]');
  await expect(page.getByText('Welcome')).toBeVisible();
});
```

## What the example shows

- the test opens the page
- enters data
- clicks the button
- checks the expected result

In other words, an E2E test walks through **an entire business scenario** in code, not a single function or component.

Markdown · drag & drop images · ⌘B / ⌘I shortcuts193 words

For the reviewer

Note to the moderator (optional)

Visible only to the moderator. Helps review go faster.