Apa saé jenis-jenis lan tingkat-tingkat testing sing béda-béda?

Question

Accepted Answer

Software testing nduwé sawetara **tingkat** (miturut scope) lan **jenis** (miturut tujuan). Ngerti babagan unit, integration, end-to-end; functional versus non-functional — membantu bangun pendekatan testing sing lengkap lan ngliputi aspek-aspek béda saka kualitas.

## Tingkat-tingkat testing (miturut scope)

```text
UNIT → individual functions/methods in isolation (smallest, fastest, most numerous)
INTEGRATION → multiple units/components working TOGETHER (e.g. code + database, services)
END-TO-END (E2E) → the WHOLE application from the user's perspective (full flows,
  through the real UI/system) — broadest, slowest
SYSTEM → the complete integrated system; ACCEPTANCE → meets business requirements
```

## Functional versus non-functional

```text
FUNCTIONAL → does it do the RIGHT thing? (correct behavior, features work)
  → unit, integration, e2e, smoke, regression, sanity tests
NON-FUNCTIONAL → HOW WELL does it work? (qualities beyond correctness):
  PERFORMANCE (speed, load), SECURITY, USABILITY, RELIABILITY, COMPATIBILITY, etc.
```

## Kategori test umum liyane

```text
REGRESSION → verify changes didn't break existing functionality (run after changes)
SMOKE → quick check that core functionality works (before deeper testing)
MANUAL → a human tests; AUTOMATED → code tests code (repeatable, fast)
WHITE-BOX (know the internals) vs BLACK-BOX (test behavior, not internals)
```

## Kenapa iku penting

Ngerti jenis-jenis lan tingkat-tingkat testing sing béda-béda iku istiméwa amarga menehi **kerangka kerja kanggo pendekatan testing sing lengkap**, dadi pengetahuan dasar kanggo kualitas software.

Testing ora siji-sijine — nyakup **tingkat** (miturut scope: **unit** kanggo bagian individual, **integration** kanggo komponen-komponen sing bekerja bareng, **end-to-end** kanggo aplikasi lengkap saka pandangan pengguna, plus system lan acceptance) lan **jenis** (miturut tujuan: testing **functional** yen software nglakoni bab sing bener, lan testing **non-functional** babagan kualitas kayata performance, security, usability, lan reliability).

Ngerti kategori-kategori iki penting amarga strategi testing sing lengkap nganggo tingkat lan jenis sing akeh — ora bisa njamin kualitas mung nganggo siji-sijine jenis test (unit tests piyé kabeh ora ketok masalah integration; functional tests piyé kabeh ora ketok performance lan security).

Ngerti tingkat-tingkate (lan yen iku trade-off antara scope versus kecepatan — unit tests cepet lan akeh, e2e tests luwes nanging alon) njlantarake konsep test pyramid.

Ngerti **kategori umum liyane** — regression (verifika manawa owah-owahan ora busuké bab), smoke (mriksa fungsi inti cepet), manual versus automated, lan white-box versus black-box — nglengkapi kosakata testing.

Ngerti béda-bédan iki tumutu kanggo padha mikir bab apa jenis testing sing diperlu proyek lan komunikasi babagan testing kanthi tepat.

Amarga kualitas software sing efektif butuh tingkat lan jenis testing sing akeh (ngliputi kebenaran ing scope béda-béda lan kualitas non-functional sing anyar), lan amarga ngerti taxonomi testing iku dasar kanggo bangun pendekatan testing sing lengkap lan diskusi babagan testing, ngerti jenis-jenis lan tingkat-tingkat testing sing béda-béda iku pengetahuan dasar sing istiméwa — kerangka kerja konseptual kanggo bidang testing, perlu kanggo mikir babab quality assurance sing lengkap lan kanggo ngerti endi saben jenis test cocog, bagian kunci saka testing literacy kanggo pembuat kode.