How deeply does Automating API Delivery cover property-based testing?

Explains CLI execution, data generation, request recording, examples, and interpreting schema failures.

Property-based testing

Property-based testing is a technique that generates many test cases from specified data properties or input strategies.

Property-based testing generates and runs many API cases from an API definition, using data-generation strategies to fuzz requests while checking schema conformance. section 7.4.1

A Schemathesis workflow can:

Use explicit OpenAPI examples as request values, making realistic examples useful to both consumers and automated tests. section 7.4.1

Finding a response-schema defect

Testing the Product Catalog API can expose a response that violates its schema because numberOfReviews and reviewRating are unexpected additional properties. The recorded cassette.yaml preserves the request used to reproduce the finding.

How Automating API Delivery covers it

liveBook manning.com

Read Automating API Delivery on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Functional Programming in Scala, Second EditionProperty-based testing checks general behavioral properties against automatically generated input values rather than relying only on hand-written examples.
liveBook manning.com

Functional Design and Architecture: Examples in HaskellProperty-based testing evaluates software by checking general behavioral properties across automatically generated inputs rather than relying only on hand-written example cases.
liveBook manning.com

Learn Haskell by ExampleProperty testing checks whether program behavior satisfies general properties across automatically generated or varied inputs.
liveBook manning.com

Functional Programming in JavaScriptA testing approach that checks whether a program satisfies general properties across many generated inputs rather than only fixed example cases.
liveBook manning.com

100 Java Mistakes and How to Avoid ThemProperty-based testing verifies general behavioral properties by running tests against many generated inputs, often including randomized inputs.
liveBook manning.com

F# in Action: A Revised Edition of Get Programming with F#A property-based test is an individual automated test that evaluates one or more stated properties over generated inputs.
liveBook manning.com

Code Like a Pro in RustProperty-based testing is a software-testing technique that generates many inputs to check whether general properties hold.

Compare how 8 books explain property-based testing →

Related concepts

QuickCheckused by · QuickCheck is a property-based testing library that generates test inputs from specifications, checks their properties, and may minimize failing counterexamples.
forallused by · forall is a property-testing combinator that constructs a property by applying a predicate to values generated from specified generators.
invariantuses · An invariant is a property or condition that remains true across the valid states, operations, or specified transformations of a system or computation.
testcontrasts with · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
attributeuses · An attribute is a named property, value, or piece of information associated with an entity, object, or program element.
fuzzingcontrasts with · Fuzzing is an automated testing technique that supplies varied, malformed, unexpected, or mutated inputs to software to reveal failures, vulnerabilities, or other defects.

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.