The Hypothesis example 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.
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.
database setting creates a
DirectoryBasedExampleDatabase in your current working directory,
.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
Hypothesis provides the following
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.
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
DirectoryBasedExampleDatabasecan be shared by checking the directory into version control, for example with the following
# 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
A wrapper to make the given database read-only.
The implementation passes through
fetch, and turns
moveinto 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.
A wrapper around multiple databases.
deleteoperation will be run against all of the wrapped databases.
fetchdoes 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.
RedisExampleDatabase(redis, *, expire_after=datetime.timedelta(days=8), key_prefix=b'hypothesis-example:')¶
Store Hypothesis examples as sets in the given
This is particularly useful for shared databases, as per the recipe for a
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:
An abstract base class for storing examples in Hypothesis’ internal format.
An ExampleDatabase maps each
byteskey to many distinct
bytesvalues, like a
If this value is already present for this key, silently do nothing.
Return an iterable over all values matching this key.
Remove this value from this key.
If this value is not present, silently do nothing.
move(src, dest, value)¶
dest. Equivalent to
delete(src, value)followed by
save(src, value), but may have a more efficient implementation.
valuewill be inserted at
destregardless of whether it is currently present at