Hide navigation sidebar
Hide table of contents sidebar
Skip to content
Back to top
View this page
Toggle table of contents sidebar

# API Reference

Reference for non-strategy objects that are part of the Hypothesis API. For documentation on strategies, see the strategies reference.

## `@given`

hypothesis.given(*_given_arguments, **_given_kwargs)

  A decorator for turning a test function that accepts arguments into a randomized test.

  This is the main entry point to Hypothesis.

hypothesis.infer

### Arguments to `@given`

The `@given` decorator may be used to specify which arguments of a function should be parametrized over. You can use either positional or keyword arguments, but not a mixture of both.

For example, all of the following are valid uses:

    @given(integers(), integers())
    def a(x, y):
        pass

    @given(integers())
    def b(x, y):
        pass

    @given(y=integers())
    def c(x, y):
        pass

    @given(x=integers())
    def d(x, y):
        pass

    @given(x=integers(), y=integers())
    def e(x, **kwargs):
        pass

    @given(x=integers(), y=integers())
    def f(x, *args, **kwargs):
        pass

    class SomeTest(TestCase):
        @given(integers())
        def test_a_thing(self, x):
            pass

The following are not:

    @given(integers(), integers(), integers())
    def g(x, y):
        pass

    @given(integers())
    def h(x, *args):
        pass

    @given(integers(), x=integers())
    def i(x, y):
        pass

    @given()
    def j(x, y):
        pass

The rules for determining what are valid uses of `given` are as follows:

1. You may pass any keyword argument to `given`.

2. Positional arguments to `given` are equivalent to the rightmost named arguments for the test function.

3. Positional arguments may not be used if the underlying test function has `*args`, `**kwargs`, or keyword-only arguments.

4. Functions tested with `given` may not have any defaults.

The reason for the “rightmost named arguments” behaviour is so that using `@given` with instance methods works: `self` will be passed to the function as normal and not be parametrized over.

The function returned by given has all the same arguments as the original test, minus those that are filled in by `@given`. Check the notes on framework compatibility to see how this affects other testing libraries you may be using.

### Inferred strategies

In some cases, Hypothesis can work out what to do when you omit arguments. This is based on introspection, not magic, and therefore has well-defined limits.

`builds()` will check the signature of the `target` (using `python:inspect.signature()`). If there are required arguments with type annotations and no strategy was passed to `builds()`, `from_type()` is used to fill them in. You can also pass the value `...` (`Ellipsis`) as a keyword argument, to force this inference for arguments with a default value.

    >>> def func(a: int, b: str):
    ...     return [a, b]
    ...
    >>> builds(func).example()
    [-6993, '']

`@given` does not perform any implicit inference for required arguments, as this would break compatibility with pytest fixtures. `...` (`python:Ellipsis`), can be used as a keyword argument to explicitly fill in an argument from its type annotation. You can also use the `hypothesis.infer` alias if writing a literal `...` seems too weird.

    @given(a=...)  # or @given(a=infer)
    def test(a: int):
        pass

    # is equivalent to
    @given(a=from_type(int))
    def test(a):
        pass

`@given(...)` can also be specified to fill all arguments from their type annotations.

    @given(...)
    def test(a: int, b: str):
        pass

    # is equivalent to
    @given(a=..., b=...)
    def test(a, b):
        pass

#### Limitations

Hypothesis does not inspect PEP 484 type comments at runtime. While `from_type()` will work as usual, inference in `builds()` and `@given` will only work if you manually create the `__annotations__` attribute (e.g. by using `@annotations(...)` and `@returns(...)` decorators).

The `python:typing` module changes between different Python releases, including at minor versions. These are all supported on a best-effort basis, but you may encounter problems. Please report them to us, and consider updating to a newer version of Python as a workaround.

## `@example`

The simplest way to reproduce a failed test is to ask Hypothesis to run the failing example it printed. For example, if `Falsifying example: test(n=1)` was printed you can decorate `test` with `@example(n=1)`.

`@example` can also be used to ensure a specific example is always executed as a regression test or to cover some edge case - basically combining a Hypothesis test and a traditional parametrized test.

class hypothesis.example(*args, **kwargs)

  A decorator which ensures a specific example is always tested.

Hypothesis will run all examples you’ve asked for first. If any of them fail it will not go on to look for more examples.

It doesn’t matter whether you put the example decorator before or after given. Any permutation of the decorators in the above will do the same thing.

Note that examples can be positional or keyword based. If they’re positional then they will be filled in from the right when calling, so either of the following styles will work as expected:

    @given(text())
    @example("Hello world")
    @example(x="Some very long string")
    def test_some_code(x):
        pass

    from unittest import TestCase

    class TestThings(TestCase):
        @given(text())
        @example("Hello world")
        @example(x="Some very long string")
        def test_some_code(self, x):
            pass

As with `@given`, it is not permitted for a single example to be a mix of positional and keyword arguments.

example.xfail(

  condition=True,
  *,
  reason='',
  raises=<class 'BaseException'>,

)

  Mark this example as an expected failure, similarly to `pytest.mark.xfail(strict=True)`.

  Expected-failing examples allow you to check that your test does fail on some examples, and therefore build confidence that passing tests are because your code is working, not because the test is missing something.

      @example(...).xfail()
      @example(...).xfail(reason="Prices must be non-negative")
      @example(...).xfail(raises=(KeyError, ValueError))
      @example(...).xfail(sys.version_info[:2] >= (3, 12), reason="needs py 3.12")
      @example(...).xfail(condition=sys.platform != "linux", raises=OSError)
      def test(x):
          pass

  Note

  Expected-failing examples are handled separately from those generated by strategies, so you should usually ensure that there is no overlap.

      @example(x=1, y=0).xfail(raises=ZeroDivisionError)
      @given(x=st.just(1), y=st.integers())  # Missing `.filter(bool)`!
      def test_fraction(x, y):
          # This test will try the explicit example and see it fail as
          # expected, then go on to generate more examples from the
          # strategy.  If we happen to generate y=0, the test will fail
          # because only the explicit example is treated as xfailing.
          x / y

example.via(whence, /)

  Attach a machine-readable label noting whence this example came.

  The idea is that tools will be able to add `@example()` cases for you, e.g. to maintain a high-coverage set of explicit examples, but also remove them if they become redundant - without ever deleting manually-added examples:

      # You can choose to annotate examples, or not, as you prefer
      @example(...)
      @example(...).via("regression test for issue #42")

      # The `hy-` prefix is reserved for automated tooling
      @example(...).via("hy-failing")
      @example(...).via("hy-coverage")
      @example(...).via("hy-target-$label")
      def test(x):
          pass

## Control

Functions that can be called from anywhere inside a test, to either modify how Hypothesis treats the current test case, or to give Hypothesis more information about the current test case.

hypothesis.assume(condition)

  Calling `assume` is like an assert that marks the example as bad, rather than failing the test.

  This allows you to specify properties that you assume will be true, and let Hypothesis try to avoid similar examples in future.

hypothesis.note(value)

  Report this value for the minimal failing example.

hypothesis.event(value, payload='')

  Record an event that occurred during this test. Statistics on the number of test runs with each event will be reported at the end if you run Hypothesis in statistics reporting mode.

  Event values should be strings or convertible to them. If an optional payload is given, it will be included in the string for Test statistics.

You can mark custom events in a test using `event()`:

    from hypothesis import event, given, strategies as st

    @given(st.integers().filter(lambda x: x % 2 == 0))
    def test_even_integers(i):
        event(f"i mod 3 = {i%3}")

These events appear in observability output, as well as the output of our pytest plugin when run with `--hypothesis-show-statistics`.

For instance, in the latter case, you would see output like:

    test_even_integers:

      - during generate phase (0.09 seconds):
          - Typical runtimes: < 1ms, ~ 59% in data generation
          - 100 passing examples, 0 failing examples, 32 invalid examples
          - Events:
            * 54.55%, Retried draw from integers().filter(lambda x: x % 2 == 0) to satisfy filter
            * 31.06%, i mod 3 = 2
            * 28.79%, i mod 3 = 0
            * 24.24%, Aborted test because unable to satisfy integers().filter(lambda x: x % 2 == 0)
            * 15.91%, i mod 3 = 1
      - Stopped because settings.max_examples=100

Arguments to `event` can be any hashable type, but two events will be considered the same if they are the same when converted to a string with `python:str`.

### Targeted property-based testing

Targeted property-based testing combines the advantages of both search-based and property-based testing. Instead of being completely random, targeted PBT uses a search-based component to guide the input generation towards values that have a higher probability of falsifying a property. This explores the input space more effectively and requires fewer tests to find a bug or achieve a high confidence in the system being tested than random PBT. (Löscher and Sagonas)

This is not always a good idea - for example calculating the search metric might take time better spent running more uniformly-random test cases, or your target metric might accidentally lead Hypothesis away from bugs - but if there is a natural metric like “floating-point error”, “load factor” or “queue length”, we encourage you to experiment with targeted testing.

    from hypothesis import given, strategies as st, target

    @given(st.floats(0, 1e100), st.floats(0, 1e100), st.floats(0, 1e100))
    def test_associativity_with_target(a, b, c):
        ab_c = (a + b) + c
        a_bc = a + (b + c)
        difference = abs(ab_c - a_bc)
        target(difference)  # Without this, the test almost always passes
        assert difference < 2.0

hypothesis.target(observation, *, label='')

  Calling this function with an `int` or `float` observation gives it feedback with which to guide our search for inputs that will cause an error, in addition to all the usual heuristics. Observations must always be finite.

  Hypothesis will try to maximize the observed value over several examples; almost any metric will work so long as it makes sense to increase it. For example, `-abs(error)` is a metric that increases as `error` approaches zero.

  Example metrics:

  - Number of elements in a collection, or tasks in a queue

  - Mean or maximum runtime of a task (or both, if you use `label`)

  - Compression ratio for data (perhaps per-algorithm or per-level)

  - Number of steps taken by a state machine

  The optional `label` argument can be used to distinguish between and therefore separately optimise distinct observations, such as the mean and standard deviation of a dataset. It is an error to call `target()` with any label more than once per test case.

  Note

  The more examples you run, the better this technique works.

  As a rule of thumb, the targeting effect is noticeable above `max_examples=1000`, and immediately obvious by around ten thousand examples per label used by your test.

  Test statistics include the best score seen for each label, which can help avoid the threshold problem when the minimal example shrinks right down to the threshold of failure (issue #2180).

We recommend that users also skim the papers introducing targeted PBT; from ISSTA 2017 and ICST 2018. For the curious, the initial implementation in Hypothesis uses hill-climbing search via a mutating fuzzer, with some tactics inspired by simulated annealing to avoid getting stuck and endlessly mutating a local maximum.

## Settings

class hypothesis.settings(

  parent=None,
  *,
  max_examples=not_set,
  derandomize=not_set,
  database=not_set,
  verbosity=not_set,
  phases=not_set,
  stateful_step_count=not_set,
  report_multiple_bugs=not_set,
  suppress_health_check=not_set,
  deadline=not_set,
  print_blob=not_set,
  backend=not_set,

)

  A settings object configures options including verbosity, runtime controls, persistence, determinism, and more.

  Default values are picked up from the settings.default object and changes made there will be picked up in newly created settings.

  backend

    EXPERIMENTAL AND UNSTABLE - see Alternative backends for Hypothesis. The importable name of a backend which Hypothesis should use to generate primitive types. We aim to support heuristic-random, solver-based, and fuzzing-based backends.

    default value: `(dynamically calculated)`

  database

    An instance of `ExampleDatabase` that will be used to save examples to and load previous examples from. May be `None` in which case no storage will be used.

    See the example database documentation for a list of built-in example database implementations, and how to define custom implementations.

    default value: `(dynamically calculated)`

  deadline

    If set, a duration (as timedelta, or integer or float number of milliseconds) that each individual example (i.e. each time your test function is called, not the whole decorated test) within a test is not allowed to exceed. Tests which take longer than that may be converted into errors (but will not necessarily be if close to the deadline, to allow some variability in test run time).

    Set this to `None` to disable this behaviour entirely.

    By default when running on CI, this will be set to None.

    default value: `timedelta(milliseconds=200)`

  derandomize

    If True, seed Hypothesis’ random number generator using a hash of the test function, so that every run will test the same set of examples until you update Hypothesis, Python, or the test function.

    This allows you to check for regressions and look for bugs using separate settings profiles - for example running quick deterministic tests on every commit, and a longer non-deterministic nightly testing run.

    By default when running on CI, this will be set to True.

    default value: `False`

  max_examples

    Once this many satisfying examples have been considered without finding any counter-example, Hypothesis will stop looking.

    Note that we might call your test function fewer times if we find a bug early or can tell that we’ve exhausted the search space; or more if we discard some examples due to use of .filter(), assume(), or a few other things that can prevent the test case from completing successfully.

    The default value is chosen to suit a workflow where the test will be part of a suite that is regularly executed locally or on a CI server, balancing total running time against the chance of missing a bug.

    If you are writing one-off tests, running tens of thousands of examples is quite reasonable as Hypothesis may miss uncommon bugs with default settings. For very complex code, we have observed Hypothesis finding novel bugs after several million examples while testing SymPy. If you are running more than 100k examples for a test, consider using our integration for coverage-guided fuzzing - it really shines when given minutes or hours to run.

    default value: `100`

  phases

    Control which phases should be run. See the full documentation for more details

    default value: `(Phase.explicit, Phase.reuse, Phase.generate, Phase.target, Phase.shrink, Phase.explain)`

  print_blob

    If set to `True`, Hypothesis will print code for failing examples that can be used with `@reproduce_failure` to reproduce the failing example.

    default value: `False`

  report_multiple_bugs

    Because Hypothesis runs the test many times, it can sometimes find multiple bugs in a single run. Reporting all of them at once is usually very useful, but replacing the exceptions can occasionally clash with debuggers. If disabled, only the exception with the smallest minimal example is raised.

    default value: `True`

  stateful_step_count

    Number of steps to run a stateful program for before giving up on it breaking.

    default value: `50`

  suppress_health_check

    A list of `HealthCheck` items to disable.

    default value: `()`

  verbosity

    Control the verbosity level of Hypothesis messages

    default value: `Verbosity.normal`

### Controlling what runs

Hypothesis divides tests into logically distinct phases.

- `Phase.explicit`: Running explicit examples from `@example`.

- `Phase.reuse`: Running examples from the database which previously failed.

- `Phase.generate`: Generating new random examples.

- `Phase.target`: Mutating examples for targeted property-based testing.

  - Requires `Phase.generate`.

- `Phase.shrink`: Shrinking failing examples.

- `Phase.explain`: Attempting to explain why a failure occurred.

  - Requires `Phase.shrink`.

Note

The explain phase has two parts, each of which is best-effort - if Hypothesis can’t find a useful explanation, we’ll just print the minimal failing example.

Following the first failure, Hypothesis will (usually) track which lines of code are always run on failing but never on passing inputs. On 3.12+, this uses `sys.monitoring`, while 3.11 and earlier uses `python:sys.settrace()`. For python 3.11 and earlier, we therefore automatically disable the explain phase on PyPy, or if you are using coverage or a debugger. If there are no clearly suspicious lines of code, we refuse the temptation to guess.

After shrinking to a minimal failing example, Hypothesis will try to find parts of the example – e.g. separate args to `@given()` – which can vary freely without changing the result of that minimal failing example. If the automated experiments run without finding a passing variation, we leave a comment in the final report:

    test_x_divided_by_y(
        x=0,  # or any other generated value
        y=0,
    )

Just remember that the lack of an explanation sometimes just means that Hypothesis couldn’t efficiently find one, not that no explanation (or simpler failing example) exists.

The phases setting provides you with fine grained control over which of these run, with each phase corresponding to a value on the `Phase` enum:

class hypothesis.Phase(*values)
  explicit = 0

    controls whether explicit examples are run.

  reuse = 1

    controls whether previous examples will be reused.

  generate = 2

    controls whether new examples will be generated.

  target = 3

    controls whether examples will be mutated for targeting.

  shrink = 4

    controls whether examples will be shrunk.

  explain = 5

    controls whether Hypothesis attempts to explain test failures.

The phases argument accepts a collection with any subset of these. e.g. `settings(phases=[Phase.generate, Phase.shrink])` will generate new examples and shrink them, but will not run explicit examples or reuse previous failures, while `settings(phases=[Phase.explicit])` will only run the explicit examples.

### Seeing intermediate result

To see what’s going on while Hypothesis runs your tests, you can turn up the verbosity setting.

    >>> from hypothesis import find, settings, Verbosity
    >>> from hypothesis.strategies import lists, integers
    >>> @given(lists(integers()))
    ... @settings(verbosity=Verbosity.verbose)
    ... def f(x):
    ...     assert not any(x)
    ... f()
    Trying example: []
    Falsifying example: [-1198601713, -67, 116, -29578]
    Shrunk example to [-1198601713]
    Shrunk example to [-1198601600]
    Shrunk example to [-1191228800]
    Shrunk example to [-8421504]
    Shrunk example to [-32896]
    Shrunk example to [-128]
    Shrunk example to [64]
    Shrunk example to [32]
    Shrunk example to [16]
    Shrunk example to [8]
    Shrunk example to [4]
    Shrunk example to [3]
    Shrunk example to [2]
    Shrunk example to [1]
    [1]

The four levels are quiet, normal, verbose and debug. normal is the default, while in quiet mode Hypothesis will not print anything out, not even the final falsifying example. debug is basically verbose but a bit more so. You probably don’t want it.

If you are using pytest, you may also need to disable output capturing for passing tests.

### Building settings objects

Settings can be created by calling `settings` with any of the available settings values. Any absent ones will be set to defaults:

    >>> from hypothesis import settings
    >>> settings().max_examples
    100
    >>> settings(max_examples=10).max_examples
    10

You can also pass a ‘parent’ settings object as the first argument, and any settings you do not specify as keyword arguments will be copied from the parent settings:

    >>> parent = settings(max_examples=10)
    >>> child = settings(parent, deadline=None)
    >>> parent.max_examples == child.max_examples == 10
    True
    >>> parent.deadline
    200
    >>> child.deadline is None
    True

### Default settings

At any given point in your program there is a current default settings, available as `settings.default`. As well as being a settings object in its own right, all newly created settings objects which are not explicitly based off another settings are based off the default, so will inherit any values that are not explicitly set from it.

You can change the defaults by using profiles.

### Settings profiles

Depending on your environment you may want different default settings. For example: during development you may want to lower the number of examples to speed up the tests. However, in a CI environment you may want more examples so you are more likely to find bugs.

Hypothesis allows you to define different settings profiles. These profiles can be loaded at any time.

static settings.register_profile(name, parent=None, **kwargs)

  Registers a collection of values to be used as a settings profile.

  Settings profiles can be loaded by name - for example, you might create a ‘fast’ profile which runs fewer examples, keep the ‘default’ profile, and create a ‘ci’ profile that increases the number of examples and uses a different database to store failures.

  The arguments to this method are exactly as for `settings`: optional `parent` settings, and keyword arguments for each setting that will be set differently to parent (or settings.default, if parent is None).

  If you register a profile that has already been defined and that profile is the currently loaded profile, the new changes will take effect immediately, and do not require reloading the profile.

static settings.get_profile(name)

  Return the profile with the given name.

static settings.load_profile(name)

  Loads in the settings defined in the profile provided.

  If the profile does not exist, InvalidArgument will be raised. Any setting not defined in the profile will be the library defined default for that setting.

Loading a profile changes the default settings but will not change the behaviour of tests that explicitly change the settings.

    >>> from hypothesis import settings
    >>> settings.register_profile("ci", max_examples=1000)
    >>> settings().max_examples
    100
    >>> settings.load_profile("ci")
    >>> settings().max_examples
    1000

Instead of loading the profile and overriding the defaults you can retrieve profiles for specific tests.

    >>> settings.get_profile("ci").max_examples
    1000

Optionally, you may define the environment variable to load a profile for you. This is the suggested pattern for running your tests on CI. The code below should run in a `conftest.py` or any setup/initialization section of your test suite. If this variable is not defined the Hypothesis defined defaults will be loaded.

    >>> import os
    >>> from hypothesis import settings, Verbosity
    >>> settings.register_profile("ci", max_examples=1000)
    >>> settings.register_profile("dev", max_examples=10)
    >>> settings.register_profile("debug", max_examples=10, verbosity=Verbosity.verbose)
    >>> settings.load_profile(os.getenv("HYPOTHESIS_PROFILE", "default"))

If you are using the hypothesis pytest plugin and your profiles are registered by your conftest you can load one with the command line option `--hypothesis-profile`.

    $ pytest tests --hypothesis-profile <profile-name>

Hypothesis comes with two built-in profiles, `ci` and `default`. `ci` is set up to have good defaults for running in a CI environment, so emphasizes determinism, while the `default` settings are picked to be more likely to find bugs and to have a good workflow when used for local development.

Hypothesis will automatically detect certain common CI environments and use the ci profile automatically when running in them. In particular, if you wish to use the `ci` profile, setting the `CI` environment variable will do this.

This will still be the case if you register your own ci profile. For example, if you wanted to run more examples in CI, you might configure it as follows:

    settings.register_profile(
        "ci",
        settings(
            settings.get_profile("ci"),
            max_examples=1000,
        ),
    )

This will configure your CI to run 1000 examples per test rather than the default of 100, and this change will automatically be picked up when running on a CI server.

### Health checks

Hypothesis’ health checks are designed to detect and warn you about performance problems where your tests are slow, inefficient, or generating very large examples.

If this is expected, e.g. when generating large arrays or dataframes, you can selectively disable them with the `suppress_health_check` setting. The argument for this parameter is a list with elements drawn from any of the class-level attributes of the HealthCheck class. Using a value of `list(HealthCheck)` will disable all health checks.

class hypothesis.HealthCheck(*values)

  Arguments for `suppress_health_check`.

  Each member of this enum is a type of health check to suppress.

  data_too_large = 1

    Checks if too many examples are aborted for being too large.

    This is measured by the number of random choices that Hypothesis makes in order to generate something, not the size of the generated object. For example, choosing a 100MB object from a predefined list would take only a few bits, while generating 10KB of JSON from scratch might trigger this health check.

  filter_too_much = 2

    Check for when the test is filtering out too many examples, either through use of `assume()` or `.filter()`, or occasionally for Hypothesis internal reasons.

  too_slow = 3

    Check for when your data generation is extremely slow and likely to hurt testing.

  return_value = 5

    Deprecated; we always error if a test returns a non-None value.

  large_base_example = 7

    Checks if the natural example to shrink towards is very large.

  not_a_test_method = 8

    Deprecated; we always error if `@given` is applied to a method defined by `python:unittest.TestCase` (i.e. not a test).

  function_scoped_fixture = 9

    Checks if `@given` has been applied to a test with a pytest function-scoped fixture. Function-scoped fixtures run once for the whole function, not once per example, and this is usually not what you want.

    Because of this limitation, tests that need to set up or reset state for every example need to do so manually within the test itself, typically using an appropriate context manager.

    Suppress this health check only in the rare case that you are using a function-scoped fixture that does not need to be reset between individual examples, but for some reason you cannot use a wider fixture scope (e.g. session scope, module scope, class scope).

    This check requires the Hypothesis pytest plugin, which is enabled by default when running Hypothesis inside pytest.

  differing_executors = 10

    Checks if `@given` has been applied to a test which is executed by different executors. If your test function is defined as a method on a class, that class will be your executor, and subclasses executing an inherited test is a common way for things to go wrong.

    The correct fix is often to bring the executor instance under the control of hypothesis by explicit parametrization over, or sampling from, subclasses, or to refactor so that `@given` is specified on leaf subclasses.

  nested_given = 11

    Checks if `@given` is used inside another `@given`. This results in quadratic generation and shrinking behavior, and can usually be expressed more cleanly by using `data()` to replace the inner `@given`.

    Nesting @given can be appropriate if you set appropriate limits for the quadratic behavior and cannot easily reexpress the inner function with `data()`. To suppress this health check, set `suppress_health_check=[HealthCheck.nested_given]` on the outer `@given`. Setting it on the inner `@given` has no effect. If you have more than one level of nesting, add a suppression for this health check to every `@given` except the innermost one.

## Database

When Hypothesis finds a bug it stores enough information in its database to reproduce it. This enables you to have a classic testing workflow of find a bug, fix a bug, and be confident that this is actually doing the right thing because Hypothesis will start by retrying the examples that broke things last time.

### Limitations

The database is best thought of as a cache that you never need to invalidate: Information may be lost when you upgrade a Hypothesis version or change your test, so you shouldn’t rely on it for correctness - if there’s an example you want to ensure occurs each time then there’s a feature for including them in your source code - but it helps the development workflow considerably by making sure that the examples you’ve just found are reproduced.

The database also records examples that exercise less-used parts of your code, so the database may update even when no failing examples were found.

### Upgrading Hypothesis and changing your tests

The design of the Hypothesis database is such that you can put arbitrary data in the database and not get wrong behaviour. When you upgrade Hypothesis, old data might be invalidated, but this should happen transparently. It can never be the case that e.g. changing the strategy that generates an argument gives you data from the old strategy.

### ExampleDatabase implementations

Hypothesis’ default `database` setting creates a `DirectoryBasedExampleDatabase` in your current working directory, under `.hypothesis/examples`. If this location is unusable, e.g. because you do not have read or write permissions, Hypothesis will emit a warning and fall back to an `InMemoryExampleDatabase`.

Hypothesis provides the following `ExampleDatabase` implementations:

class hypothesis.database.InMemoryExampleDatabase(*args, **kwargs)

  A non-persistent example database, implemented in terms of a dict of sets.

  This can be useful if you call a test function several times in a single session, or for testing other database implementations, but because it does not persist between runs we do not recommend it for general use.

class hypothesis.database.DirectoryBasedExampleDatabase(*args, **kwargs)

  Use a directory to store Hypothesis examples as files.

  Each test corresponds to a directory, and each example to a file within that directory. While the contents are fairly opaque, a `DirectoryBasedExampleDatabase` can be shared by checking the directory into version control, for example with the following `.gitignore`:

      # Ignore files cached by Hypothesis...
      .hypothesis/*
      # except for the examples directory
      !.hypothesis/examples/

  Note however that this only makes sense if you also pin to an exact version of Hypothesis, and we would usually recommend implementing a shared database with a network datastore - see `ExampleDatabase`, and the `MultiplexedDatabase` helper.

class hypothesis.database.GitHubArtifactDatabase(*args, **kwargs)

  A file-based database loaded from a GitHub Actions artifact.

  You can use this for sharing example databases between CI runs and developers, allowing the latter to get read-only access to the former. This is particularly useful for continuous fuzzing (i.e. with HypoFuzz), where the CI system can help find new failing examples through fuzzing, and developers can reproduce them locally without any manual effort.

  Note

  You must provide `GITHUB_TOKEN` as an environment variable. In CI, Github Actions provides this automatically, but it needs to be set manually for local usage. In a developer machine, this would usually be a Personal Access Token. If the repository is private, it’s necessary for the token to have `repo` scope in the case of a classic token, or `actions:read` in the case of a fine-grained token.

  In most cases, this will be used through the `MultiplexedDatabase`, by combining a local directory-based database with this one. For example:

      local = DirectoryBasedExampleDatabase(".hypothesis/examples")
      shared = ReadOnlyDatabase(GitHubArtifactDatabase("user", "repo"))

      settings.register_profile("ci", database=local)
      settings.register_profile("dev", database=MultiplexedDatabase(local, shared))
      # We don't want to use the shared database in CI, only to populate its local one.
      # which the workflow should then upload as an artifact.
      settings.load_profile("ci" if os.environ.get("CI") else "dev")

  Note

  Because this database is read-only, you always need to wrap it with the `ReadOnlyDatabase`.

  A setup like this can be paired with a GitHub Actions workflow including something like the following:

      - name: Download example database
        uses: dawidd6/action-download-artifact@v9
        with:
          name: hypothesis-example-db
          path: .hypothesis/examples
          if_no_artifact_found: warn
          workflow_conclusion: completed

      - name: Run tests
        run: pytest

      - name: Upload example database
        uses: actions/upload-artifact@v3
        if: always()
        with:
          name: hypothesis-example-db
          path: .hypothesis/examples

  In this workflow, we use dawidd6/action-download-artifact to download the latest artifact given that the official actions/download-artifact does not support downloading artifacts from previous workflow runs.

  The database automatically implements a simple file-based cache with a default expiration period of 1 day. You can adjust this through the `cache_timeout` property.

  For mono-repo support, you can provide a unique `artifact_name` (e.g. `hypofuzz-example-db-frontend`).

class hypothesis.database.ReadOnlyDatabase(*args, **kwargs)

  A wrapper to make the given database read-only.

  The implementation passes through `fetch`, and turns `save`, `delete`, and `move` into silent no-ops.

  Note that this disables Hypothesis’ automatic discarding of stale examples. It is designed to allow local machines to access a shared database (e.g. from CI servers), without propagating changes back from a local or in-development branch.

class hypothesis.database.MultiplexedDatabase(*args, **kwargs)

  A wrapper around multiple databases.

  Each `save`, `fetch`, `move`, or `delete` operation will be run against all of the wrapped databases. `fetch` does not yield duplicate values, even if the same value is present in two or more of the wrapped databases.

  This combines well with a `ReadOnlyDatabase`, as follows:

      local = DirectoryBasedExampleDatabase("/tmp/hypothesis/examples/")
      shared = CustomNetworkDatabase()

      settings.register_profile("ci", database=shared)
      settings.register_profile(
          "dev", database=MultiplexedDatabase(local, ReadOnlyDatabase(shared))
      )
      settings.load_profile("ci" if os.environ.get("CI") else "dev")

  So your CI system or fuzzing runs can populate a central shared database; while local runs on development machines can reproduce any failures from CI but will only cache their own failures locally and cannot remove examples from the shared database.

class hypothesis.database.BackgroundWriteDatabase(*args, **kwargs)

  A wrapper which defers writes on the given database to a background thread.

  Calls to `fetch()` wait for any enqueued writes to finish before fetching from the database.

class hypothesis.extra.redis.RedisExampleDatabase(*args, **kwargs)

  Store Hypothesis examples as sets in the given `Redis` datastore.

  This is particularly useful for shared databases, as per the recipe for a `MultiplexedDatabase`.

  Note

  If a test has not been run for `expire_after`, those examples will be allowed to expire. The default time-to-live persists examples between weekly runs.

### Defining your own ExampleDatabase

You can define your `ExampleDatabase`, for example to use a shared datastore, with just a few methods:

class hypothesis.database.ExampleDatabase(*args, **kwargs)

  An abstract base class for storing examples in Hypothesis’ internal format.

  An ExampleDatabase maps each `bytes` key to many distinct `bytes` values, like a `Mapping[bytes, set[bytes]]`.

  abstractmethod save(key, value)

    Save `value` under `key`.

    If this value is already present for this key, silently do nothing.

  abstractmethod fetch(key)

    Return an iterable over all values matching this key.

  abstractmethod delete(key, value)

    Remove this value from this key.

    If this value is not present, silently do nothing.

  move(src, dest, value)

    Move `value` from key `src` to key `dest`. Equivalent to `delete(src, value)` followed by `save(src, value)`, but may have a more efficient implementation.

    Note that `value` will be inserted at `dest` regardless of whether it is currently present at `src`.

  add_listener(f, /)

    Add a change listener.

  remove_listener(f, /)

    Remove a change listener. If the listener is not present, silently do nothing.

  clear_listeners()

    Remove all change listeners.

## Stateful tests

class hypothesis.stateful.RuleBasedStateMachine

  A RuleBasedStateMachine gives you a structured way to define state machines.

  The idea is that a state machine carries the system under test and some supporting data. This data can be stored in instance variables or divided into Bundles. The state machine has a set of rules which may read data from bundles (or just from normal strategies), push data onto bundles, change the state of the machine, or verify properties. At any given point a random applicable rule will be executed.

### Rules

hypothesis.stateful.rule(*, targets=(), target=None, **kwargs)

  Decorator for RuleBasedStateMachine. Any Bundle present in `target` or `targets` will define where the end result of this function should go. If both are empty then the end result will be discarded.

  `target` must be a Bundle, or if the result should be replicated to multiple bundles you can pass a tuple of them as the `targets` argument. It is invalid to use both arguments for a single rule. If the result should go to exactly one of several bundles, define a separate rule for each case.

  kwargs then define the arguments that will be passed to the function invocation. If their value is a Bundle, or if it is `consumes(b)` where `b` is a Bundle, then values that have previously been produced for that bundle will be provided. If `consumes` is used, the value will also be removed from the bundle.

  Any other kwargs should be strategies and values from them will be provided.

hypothesis.stateful.consumes(bundle)

  When introducing a rule in a RuleBasedStateMachine, this function can be used to mark bundles from which each value used in a step with the given rule should be removed. This function returns a strategy object that can be manipulated and combined like any other.

  For example, a rule declared with

  `@rule(value1=b1, value2=consumes(b2), value3=lists(consumes(b3)))`

  will consume a value from Bundle `b2` and several values from Bundle `b3` to populate `value2` and `value3` each time it is executed.

hypothesis.stateful.multiple(*args)

  This function can be used to pass multiple results to the target(s) of a rule. Just use `return multiple(result1, result2, ...)` in your rule.

  It is also possible to use `return multiple()` with no arguments in order to end a rule without passing any result.

class hypothesis.stateful.Bundle(name, *, consume=False, draw_references=True)

  A collection of values for use in stateful testing.

  Bundles are a kind of strategy where values can be added by rules, and (like any strategy) used as inputs to future rules.

  The `name` argument they are passed is the they are referred to internally by the state machine; no two bundles may have the same name. It is idiomatic to use the attribute being assigned to as the name of the Bundle:

      class MyStateMachine(RuleBasedStateMachine):
          keys = Bundle("keys")

  Bundles can contain the same value more than once; this becomes relevant when using `consumes()` to remove values again.

  If the `consume` argument is set to True, then all values that are drawn from this bundle will be consumed (as above) when requested.

hypothesis.stateful.initialize(*, targets=(), target=None, **kwargs)

  Decorator for RuleBasedStateMachine.

  An initialize decorator behaves like a rule, but all `@initialize()` decorated methods will be called before any `@rule()` decorated methods, in an arbitrary order. Each `@initialize()` method will be called exactly once per run, unless one raises an exception - after which only the `.teardown()` method will be run. `@initialize()` methods may not have preconditions.

hypothesis.stateful.precondition(precond)

  Decorator to apply a precondition for rules in a RuleBasedStateMachine. Specifies a precondition for a rule to be considered as a valid step in the state machine, which is more efficient than using `assume()` within the rule. The `precond` function will be called with the instance of RuleBasedStateMachine and should return True or False. Usually it will need to look at attributes on that instance.

  For example:

      class MyTestMachine(RuleBasedStateMachine):
          state = 1

          @precondition(lambda self: self.state != 0)
          @rule(numerator=integers())
          def divide_with(self, numerator):
              self.state = numerator / self.state

  If multiple preconditions are applied to a single rule, it is only considered a valid step when all of them return True. Preconditions may be applied to invariants as well as rules.

hypothesis.stateful.invariant(*, check_during_init=False)

  Decorator to apply an invariant for rules in a RuleBasedStateMachine. The decorated function will be run after every rule and can raise an exception to indicate failed invariants.

  For example:

      class MyTestMachine(RuleBasedStateMachine):
          state = 1

          @invariant()
          def is_nonzero(self):
              assert self.state != 0

  By default, invariants are only checked after all `@initialize()` rules have been run. Pass `check_during_init=True` for invariants which can also be checked during initialization.

### Running state machines

hypothesis.stateful.run_state_machine_as_test(

  state_machine_factory,
  *,
  settings=None,
  _min_steps=0,

)

  Run a state machine definition as a test, either silently doing nothing or printing a minimal breaking program and raising an exception.

  state_machine_factory is anything which returns an instance of RuleBasedStateMachine when called with no arguments - it can be a class or a function. settings will be used to control the execution of the test.

If you want to bypass the TestCase infrastructure you can invoke these manually. The stateful module exposes the function `run_state_machine_as_test`, which takes an arbitrary function returning a RuleBasedStateMachine and an optional settings parameter and does the same as the class based runTest provided.

This is not recommended as it bypasses some important internal functions, including reporting of statistics such as runtimes and `event()` calls. It was originally added to support custom `__init__` methods, but you can now use `initialize()` rules instead.

## Reproducing failures

One of the things that is often concerning for people using randomized testing is the question of how to reproduce failing test cases. Hypothesis has a number of features to support this. The one you will use most commonly when developing locally is the example database, which means that you shouldn’t have to think about the problem at all for local use - test failures will just automatically reproduce without you having to do anything.

The example database is perfectly suitable for sharing between machines, but there currently aren’t very good work flows for that, so Hypothesis provides a number of ways to make examples reproducible by adding them to the source code of your tests. This is particularly useful when e.g. you are trying to run an example that has failed on your CI, or otherwise share them between machines.

### Reproducing a test run with `@seed`

hypothesis.seed(seed)

  seed: Start the test execution from a specific seed.

  May be any hashable object. No exact meaning for seed is provided other than that for a fixed seed value Hypothesis will try the same actions (insofar as it can given external sources of non- determinism. e.g. timing and hash randomization).

  Overrides the derandomize setting, which is designed to enable deterministic builds rather than reproducing observed failures.

When a test fails unexpectedly, usually due to a health check failure, Hypothesis will print out a seed that led to that failure, if the test is not already running with a fixed seed. You can then recreate that failure using either the `@seed` decorator or (if you are running pytest) with `--hypothesis-seed`. For example, the following test function and `RuleBasedStateMachine` will each check the same examples each time they are executed, thanks to `@seed()`:

    @seed(1234)
    @given(x=...)
    def test(x): ...

    @seed(6789)
    class MyModel(RuleBasedStateMachine): ...

The seed will not be printed if you could simply use `@example` instead.

### Reproducing an example with `@reproduce_failure`

Hypothesis has an opaque binary representation that it uses for all examples it generates. This representation is not intended to be stable across versions or with respect to changes in the test, but can be used to to reproduce failures with the `@reproduce_failure` decorator.

hypothesis.reproduce_failure(version, blob)

  Run the example that corresponds to this data blob in order to reproduce a failure.

  A test with this decorator always runs only one example and always fails. If the provided example does not cause a failure, or is in some way invalid for this test, then this will fail with a DidNotReproduce error.

  This decorator is not intended to be a permanent addition to your test suite. It’s simply some code you can add to ease reproduction of a problem in the event that you don’t have access to the test database. Because of this, no compatibility guarantees are made between different versions of Hypothesis - its API may change arbitrarily from version to version.

The intent is that you should never write this decorator by hand, but it is instead provided by Hypothesis. When a test fails with a falsifying example, Hypothesis may print out a suggestion to use `@reproduce_failure` on the test to recreate the problem as follows:

    >>> from hypothesis import settings, given, PrintSettings
    >>> import hypothesis.strategies as st
    >>> @given(st.floats())
    ... @settings(print_blob=True)
    ... def test(f):
    ...     assert f == f
    ...
    >>> try:
    ...     test()
    ... except AssertionError:
    ...     pass
    ...
    Falsifying example: test(f=nan)

    You can reproduce this example by temporarily adding @reproduce_failure(..., b'AAAA//AAAAAAAAEA') as a decorator on your test case

Adding the suggested decorator to the test should reproduce the failure (as long as everything else is the same - changing the versions of Python or anything else involved, might of course affect the behaviour of the test! Note that changing the version of Hypothesis will result in a different error - each `@reproduce_failure` invocation is specific to a Hypothesis version).

By default these messages are not printed. If you want to see these you can set the `print_blob` setting to `True`.

## Django

See also

See the Django strategies reference for documentation on strategies in the `hypothesis.extra.django` module.

Hypothesis offers a number of features specific for Django testing, available in the `hypothesis[django]` extra. This is tested against each supported series with mainstream or extended support - if you’re still getting security patches, you can test with Hypothesis.

class hypothesis.extra.django.TestCase(*args, **kwargs)

Using it is quite straightforward: All you need to do is subclass `hypothesis.extra.django.TestCase` or `hypothesis.extra.django.TransactionTestCase` or `LiveServerTestCase` or `StaticLiveServerTestCase` and you can use `@given` as normal, and the transactions will be per example rather than per test function as they would be if you used `@given` with a normal django test suite (this is important because your test function will be called multiple times and you don’t want them to interfere with each other). Test cases on these classes that do not use `@given` will be run as normal for `django:django.test.TestCase` or `django:django.test.TransactionTestCase`.

class hypothesis.extra.django.TransactionTestCase(*args, **kwargs)

class hypothesis.extra.django.LiveServerTestCase(*args, **kwargs)

class hypothesis.extra.django.StaticLiveServerTestCase(*args, **kwargs)

We recommend avoiding `TransactionTestCase` unless you really have to run each test case in a database transaction. Because Hypothesis runs this in a loop, the performance problems `django:django.test.TransactionTestCase` normally has are significantly exacerbated and your tests will be really slow. If you are using `TransactionTestCase`, you may need to use `@settings(suppress_health_check=[HealthCheck.too_slow])` to avoid errors due to slow example generation.

Having set up a test class, you can now pass `@given` a strategy for Django models with `from_model()`. For example, using the trivial django project we have for testing:

    >>> from hypothesis.extra.django import from_model
    >>> from toystore.models import Customer
    >>> c = from_model(Customer).example()
    >>> c
    <Customer: Customer object>
    >>> c.email
    'jaime.urbina@gmail.com'
    >>> c.name
    '\U00109d3d\U000e07be\U000165f8\U0003fabf\U000c12cd\U000f1910\U00059f12\U000519b0\U0003fabf\U000f1910\U000423fb\U000423fb\U00059f12\U000e07be\U000c12cd\U000e07be\U000519b0\U000165f8\U0003fabf\U0007bc31'
    >>> c.age
    -873375803

Hypothesis has just created this with whatever the relevant type of data is.

Obviously the customer’s age is implausible, which is only possible because we have not used (eg) `MinValueValidator` to set the valid range for this field (or used a `PositiveSmallIntegerField`, which would only need a maximum value validator).

If you do have validators attached, Hypothesis will only generate examples that pass validation. Sometimes that will mean that we fail a `HealthCheck` because of the filtering, so let’s explicitly pass a strategy to skip validation at the strategy level:

    >>> from hypothesis.strategies import integers
    >>> c = from_model(Customer, age=integers(min_value=0, max_value=120)).example()
    >>> c
    <Customer: Customer object>
    >>> c.age
    5

### Custom field types

If you have a custom Django field type you can register it with Hypothesis’s model deriving functionality by registering a default strategy for it:

    >>> from toystore.models import CustomishField, Customish
    >>> from_model(Customish).example()
    hypothesis.errors.InvalidArgument: Missing arguments for mandatory field
        customish for model Customish
    >>> from hypothesis.extra.django import register_field_strategy
    >>> from hypothesis.strategies import just
    >>> register_field_strategy(CustomishField, just("hi"))
    >>> x = from_model(Customish).example()
    >>> x.customish
    'hi'

Note that this mapping is on exact type. Subtypes will not inherit it.

### Generating child models

For the moment there’s no explicit support in hypothesis-django for generating dependent models. i.e. a Company model will generate no Shops. However if you want to generate some dependent models as well, you can emulate this by using the `.flatmap()` function as follows:

    from hypothesis.strategies import just, lists

    def generate_with_shops(company):
        return lists(from_model(Shop, company=just(company))).map(lambda _: company)

    company_with_shops_strategy = from_model(Company).flatmap(generate_with_shops)

Let’s unpack what this is doing:

The way flatmap works is that we draw a value from the original strategy, then apply a function to it which gives us a new strategy. We then draw a value from that strategy. So in this case we’re first drawing a company, and then we’re drawing a list of shops belonging to that company: The `just()` strategy is a strategy such that drawing it always produces the individual value, so `from_model(Shop, company=just(company))` is a strategy that generates a Shop belonging to the original company.

So the following code would give us a list of shops all belonging to the same company:

    from_model(Company).flatmap(lambda c: lists(from_model(Shop, company=just(c))))

The only difference from this and the above is that we want the company, not the shops. This is where the inner map comes in. We build the list of shops and then throw it away, instead returning the company we started for. This works because the models that Hypothesis generates are saved in the database, so we’re essentially running the inner strategy purely for the side effect of creating those children in the database.

### Generating primary key values

If your model includes a custom primary key that you want to generate using a strategy (rather than a default auto-increment primary key) then Hypothesis has to deal with the possibility of a duplicate primary key.

If a model strategy generates a value for the primary key field, Hypothesis will create the model instance with `update_or_create()`, overwriting any existing instance in the database for this test case with the same primary key.

### On the subject of `MultiValueField`

Django forms feature the `MultiValueField` which allows for several fields to be combined under a single named field, the default example of this is the `SplitDateTimeField`.

    class CustomerForm(forms.Form):
        name = forms.CharField()
        birth_date_time = forms.SplitDateTimeField()

`from_form()` supports `MultiValueField` subclasses directly, however if you want to define your own strategy be forewarned that Django binds data for a `MultiValueField` in a peculiar way. Specifically each sub-field is expected to have its own entry in `data` addressed by the field name (e.g. `birth_date_time`) and the index of the sub-field within the `MultiValueField`, so form `data` for the example above might look like this:

    {
        "name": "Samuel John",
        "birth_date_time_0": "2018-05-19",  # the date, as the first sub-field
        "birth_date_time_1": "15:18:00",  # the time, as the second sub-field
    }

Thus, if you want to define your own strategies for such a field you must address your sub-fields appropriately:

    from_form(CustomerForm, birth_date_time_0=just("2018-05-19"))

## Use with external fuzzers

Tip

Want an integrated workflow for your team’s local tests, CI, and continuous fuzzing?
Use HypoFuzz to fuzz your whole test suite, and find more bugs without more tests!

Sometimes, you might want to point a traditional fuzzer such as python-afl, pythonfuzz, or Google’s atheris (for Python and native extensions) at your code. Wouldn’t it be nice if you could use any of your `@given` tests as fuzz targets, instead of converting bytestrings into your objects by hand?

    @given(st.text())
    def test_foo(s): ...

    # This is a traditional fuzz target - call it with a bytestring,
    # or a binary IO object, and it runs the test once.
    fuzz_target = test_foo.hypothesis.fuzz_one_input

    # For example:
    fuzz_target(b"\x00\x00\x00\x00\x00\x00\x00\x00")
    fuzz_target(io.BytesIO(...))

Depending on the input to `fuzz_one_input`, one of three things will happen:

- If the bytestring was invalid, for example because it was too short or failed a filter or `assume()` too many times, `fuzz_one_input` returns `None`.

- If the bytestring was valid and the test passed, `fuzz_one_input` returns a canonicalised and pruned buffer which will replay that test case. This is provided as an option to improve the performance of mutating fuzzers, but can safely be ignored.

- If the test failed, i.e. raised an exception, `fuzz_one_input` will add the pruned buffer to the Hypothesis example database and then re-raise that exception. All you need to do to reproduce, minimize, and de-duplicate all the failures found via fuzzing is run your test suite!

Note that the interpretation of both input and output bytestrings is specific to the exact version of Hypothesis you are using and the strategies given to the test, just like the example database and `@reproduce_failure` decorator.

Tip

For usages of `fuzz_one_input` which expect to discover many failures, consider wrapping your database with `BackgroundWriteDatabase` for low-overhead writes of failures.

### Interaction with settings

`fuzz_one_input` uses just enough of Hypothesis’ internals to drive your test function with a fuzzer-provided bytestring, and most settings therefore have no effect in this mode. We recommend running your tests the usual way before fuzzing to get the benefits of healthchecks, as well as afterwards to replay, shrink, deduplicate, and report whatever errors were discovered.

- The `database` setting is used by fuzzing mode - adding failures to the database to be replayed when you next run your tests is our preferred reporting mechanism and response to the ‘fuzzer taming’ problem.

- The `verbosity` and `stateful_step_count` settings work as usual.

The `deadline`, `derandomize`, `max_examples`, `phases`, `print_blob`, `report_multiple_bugs`, and `suppress_health_check` settings do not affect fuzzing mode.

## Custom function execution

Hypothesis provides you with a hook that lets you control how it runs examples.

This lets you do things like set up and tear down around each example, run examples in a subprocess, transform coroutine tests into normal tests, etc. For example, `TransactionTestCase` in the Django extra runs each example in a separate database transaction.

The way this works is by introducing the concept of an executor. An executor is essentially a function that takes a block of code and run it. The default executor is:

    def default_executor(function):
        return function()

You define executors by defining a method `execute_example` on a class. Any test methods on that class with `@given` used on them will use `self.execute_example` as an executor with which to run tests. For example, the following executor runs all its code twice:

    from unittest import TestCase

    class TestTryReallyHard(TestCase):
        @given(integers())
        def test_something(self, i):
            perform_some_unreliable_operation(i)

        def execute_example(self, f):
            f()
            return f()

Note: The functions you use in map, etc. will run inside the executor. i.e. they will not be called until you invoke the function passed to `execute_example`.

An executor must be able to handle being passed a function which returns None, otherwise it won’t be able to run normal test cases. So for example the following executor is invalid:

    from unittest import TestCase

    class TestRunTwice(TestCase):
        def execute_example(self, f):
            return f()()

and should be rewritten as:

    from unittest import TestCase

    class TestRunTwice(TestCase):
        def execute_example(self, f):
            result = f()
            if callable(result):
                result = result()
            return result

An alternative hook is provided for use by test runner extensions such as pytest-trio, which cannot use the `execute_example` method. This is not recommended for end-users - it is better to write a complete test function directly, perhaps by using a decorator to perform the same transformation before applying `@given`.

    @given(x=integers())
    @pytest.mark.trio
    async def test(x): ...

    # Illustrative code, inside the pytest-trio plugin
    test.hypothesis.inner_test = lambda x: trio.run(test, x)

For authors of test runners however, assigning to the `inner_test` attribute of the `hypothesis` attribute of the test will replace the interior test.

Note

The new `inner_test` must accept and pass through all the `*args` and `**kwargs` expected by the original test.

If the end user has also specified a custom executor using the `execute_example` method, it - and all other execution-time logic - will be applied to the new inner test assigned by the test runner.