Apa iku snapshot testing?

Question

Accepted Answer

**Snapshot testing** nangkep "snapshot" saka sawetara output (umume output UI component sing direnderisasi utawa struktur data) lan mbandhingake running berikute karo iku — nandhai nalika output owah. Iki berguna kanggo ndeteksi owah-owahan sing ora dikarepake, nanging duwe keterbatasan sing perlu dimangerteni.

## Carane snapshot testing gumana

```text
1. First run → the test RECORDS the output (e.g. a rendered component) as a SNAPSHOT file
2. Later runs → COMPARE the current output to the saved snapshot:
   → MATCHES → pass; DIFFERS → fail (the output changed)
3. If the change is INTENTIONAL → UPDATE the snapshot (review the diff, then accept)
```

```js
// Jest snapshot test (e.g. a React component)
test('renders correctly', () => {
  const tree = render(<Button label="Click" />).toJSON();
  expect(tree).toMatchSnapshot();    // compares to the stored snapshot
});
```

## Panggunaan lan manfaat

```text
✓ Detect UNINTENDED CHANGES — flags when output changes unexpectedly (UI, serialized data)
✓ FAST to write — no manual assertions for complex output; auto-captures the expected result
✓ Good for UI components (catch unexpected rendering changes), config, large data structures
```

## Keterbatasan (gunakake kanthi ati-ati)

```text
⚠️ Snapshots don't verify CORRECTNESS — they capture whatever output exists (even if WRONG);
   they only detect CHANGE, not that the output is RIGHT
⚠️ BLINDLY UPDATING snapshots (jest -u without reviewing) → defeats the purpose (accepting
   broken output) — a common bad habit
⚠️ Large/brittle snapshots → change often, get rubber-stamped, low value
→ Use for change detection; keep snapshots small/focused; REVIEW snapshot diffs;
  don't rely on them alone (combine with real assertions for behavior).
```

## Sebabe penting

Pamahaman babagan snapshot testing iku berharga amarga iku **teknik sing asring digunakake** (utamane kanggo UI) sing berguna nalika diterapake kanthi apik nanging problematik nalika disalahgunakake, mula mangerteni kapindahan lan keterbatasane iku pengetahuan praktis sing penting.

Snapshot testing — nangkep output (umume UI component sing direnderisasi utawa struktur data) lan mbandhingake running berikute karo snapshot sing disimpen — **berguna kanggo ndeteksi owah-owahan sing ora dikarepake**: iku nandhai nalika output owah ora kapesthi (nyekel owah-owahan rendering UI utawa owah-owahan struktur data sing kebetulan), **cepet ditulis** (auto-nangkep output sing dikarepake tanpa manual asserting saben detail output kompleks), lan cocok kanggo UI components, konfigurasi, lan struktur data sing gedhé.

Pamahaman manfaat iki njlasake populeritate, utamane ing UI testing.

Namun, pamahaman tentang **keterbatasan iku sangat penting** kanggo nggunakake kanthi apik: snapshots **ora verifikasi kahanan** — mung nangkep output apa wae sing ana (mula apa wae sing salah), mung ndeteksi *owah* dudu *kabenaran* — mula snapshot bisa ngunci output sing bug.

**Pitfall paling gedhe iku nang-update snapshots kanthi buta** (jalanake update command tanpa ndeleng diff), sing ngrusak tujuan kanthi nampa output sing bisa-bisa rusak — kebiasaan sing ala lan umum.

Snapshots gedhé lan brittle sing asring owah entuk approval stamp lan menehi nilai sethithik.

Pamahaman babagan panggunaan sing tepat — kanggo ndeteksi owah, njaga snapshots cilik lan fokus, **ndeleng diffs snapshot** kanthi teliti, lan ora gumantung mung ing dheweke (nggabung karo real behavior assertions) — ngrefleksikake pangertian sing matang sing ngelak panggunaan salah sing umum.

Amarga snapshot testing asring digunakake (utamane kanggo UI) lan berguna kanggo ndeteksi owah nanging gampang disalahgunakake (ngunci output sing salah, blindly nang-update), lan amarga pamahaman babagan kapindahan lan keterbatasan pentinge ngaktifake nggunakake kanthi apik, pamahaman babagan snapshot testing iku pengetahuan praktis sing berharga — teknik umum kanggo dimangerteni kanthi bener, ing ngendi ngapresiasi keterbatasane (ndeteksi owah, dudu kabenaran) lan panggunaan sing tepat (ndeleng diffs, ora blindly nang-update) iku sama pentinge karo teknik dhéwé, ngrefleksikake penilaian testing sing suci.