Apa iku pengujian end-to-end (E2E)?

Question

Accepted Answer

**End-to-end (E2E) testing** verififikasi **aplikasi lengkap saka perspektif pangguna** — ngetes alur kerja lengkap liwat sistem asli (UI, backend, database) kaya pengalaman pangguna. Iku menehi kapercayaan paling dhuwur yen kabeh sistem bisa manggon, nanging luwih alon lan luwih rapuh.

## Apa sing ditindakake E2E testing

```text
E2E tests verify COMPLETE user flows through the WHOLE system:
  → simulate a real USER: open the app, click/type, navigate, submit, verify results
  → exercise the FULL stack: UI → backend → database → and back (everything integrated)
  → e.g. "user logs in, adds an item to the cart, checks out, sees confirmation"
→ tests the app as users actually experience it.
```

## Conto (web, karo Playwright/Cypress)

```js
test('user can log in and see dashboard', async ({ page }) => {
  await page.goto('/login');
  await page.fill('#email', 'user@example.com');
  await page.fill('#password', 'password');
  await page.click('button[type=submit]');         // act like a user
  await expect(page.locator('h1')).toHaveText('Dashboard');  // verify the outcome
});
```

Alat E2E (Playwright, Cypress, Selenium kanggo web; Detox, Appium kanggo mobile) ngeterake UI asli kaya pangguna.

## Trade-offs (pucuk piramida)

```text
✓ HIGHEST CONFIDENCE — verifies the WHOLE system works together, as users see it
✗ SLOW (real browser/app, full stack); BRITTLE (UI changes, timing → FLAKY tests);
  EXPENSIVE to write/maintain; harder to debug failures
→ Have FEW E2E tests — cover CRITICAL user flows only (login, checkout, core paths);
  rely on unit/integration tests for the rest.
```

## Apa sing penting

Pamahaman pengujian end-to-end iku wigati amarga menehi **kapercayaan paling dhuwur yen sistem lengkap bisa manggon** kaya sing dialami pangguna, nanging duwe trade-offs penting sing mbentuk kepriye mestine digunakake, dadi kuwi pengetahuan pengujian sing penting.

E2E tests verififikasi **alur pangguna lengkap liwat kabeh sistem terpadu** (UI, backend, database) kanthi simulasi aksi pangguna asli — menehi nilai unik kanggo konfirmasi aplikasi kabeh bener-bener bisa manggon bareng saka perspektif pangguna (barang sing unit tests lan integration tests, sing ngest bagian, ora bisa nyukupi kabeh).

Iku nudake E2E tests wigati kanggo verififikasi fungsionalitas end-to-end kritis.

Nanging, paham **trade-offs** iku penting banget: E2E tests iku **alon** (mbukak browser/app asli lan full stack), **rapuh** (sensitif karo owah-owahan UI lan timing, dadine gampang rusak — masalah asli, abot hati), larang nulis lan mirengake, lan luwih susah untuk debug.

Trade-offs kasebut sebab E2E tests ana ing **pucuk piramida pengujian karo paling sithik tests** — mestine nutupi mung **alur pangguna kritis** (login, checkout, jalur inti) nalika unit lan integration tests nangani sing liyane.

Paham iki — kapercayaan E2E sing dhuwur nanging biaya sing dhuwur, lan panduan asile nggunakake kanthi ora muwah kanggo alur kritis — iku wawasan praktis kunci sing nyegah kesalahan umum saka terlalu ngandelake E2E tests sing alon lan rapuh.

Ngerti alat-alate (Playwright, Cypress, Selenium, Detox, Appium) menehi konteks praktis.

Amarga E2E testing menehi kapercayaan unik lan dhuwur yen kabeh sistem bisa manggon (wigati kanggo alur kritis) nanging duwe trade-offs signifikan (alon, rapuh, larang) sing ndikte nggunakake kanthi hati-hati, lan amarga paham baik nilai lan peran mbatesi asile penting kanggo strategi pengujian sing sehat, paham pengujian end-to-end iku pengetahuan wigati lan praktis — penting kanggo verififikasi alur pangguna kritis bisa manggon end-to-end nalika paham trade-offs sing tegese mestine digunakake kanthi ora muwah, bagian kunci saka pendekatan pengujian sing seimbang.