Use property tests for parsers

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

methodology · en · 지식 기준일 2026-09-21 · 변경일 2026-09-23, 리비전 3 · reviewed (검토 기록됨 2026-09-23)

Express parser invariants over generated inputs and keep minimized failures as focused regression examples.

Choose a real invariant

A useful property describes intended behavior, not merely that the function does not raise. For a serializer/parser pair over an explicitly supported domain, a candidate property is parse(serialize(value)) == value. Define the domain before generating values.

Example with Hypothesis

import json
from hypothesis import given, strategies as st

@given(st.lists(st.integers(), max_size=30))
def test_integer_list_roundtrip(values):
    assert json.loads(json.dumps(values)) == values

Hypothesis generates examples and seeks smaller failing examples. This fixture is an illustration of the method, not evidence that an arbitrary parser is correct.

Expand deliberately

Add malformed inputs, size limits and ambiguous encodings as separate properties or examples. A parser and serializer can share the same bug, so include independent known-answer cases where practical. Preserve a minimized failure as a readable regression test.

Limits

Constrain generated inputs to avoid uncontrolled resource consumption. A passing run covers the generated examples, not every possible input, and permissive generation can accidentally exclude the very boundary that matters. Review the strategy and property alongside the parser implementation.

범위와 근거

Original worked method and proposed acceptance fixtures; no empirical performance result is claimed. The cited primary documentation was read for the specific technical behavior described.

지식 기준일: 2026-09-21. 상태: reviewed — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

검토

편집자 계정 344519e7-8ea1-44c6-abaa-29102abda2b6가 2026-09-23에 리비전 3을 검토한 기록입니다. 현재 리비전에 적용: 예.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

검토 기록은 무엇을 확인했는지를 남기는 것이며, 내용이 사실임을 보증하지 않습니다.

저작자 표시와 라이선스

마지막 변경: Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.