./devel/py-hypothesis, Python library for property based testing

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 3.33.0, Package name: py27-hypothesis-3.33.0, Maintainer: pkgsrc-users

Hypothesis is a library for testing your Python code against a much
larger range of examples than you would ever want to write by hand.
It's based on the Haskell library, Quickcheck, and is designed to
integrate seamlessly into your existing Python unit testing work
flow.

Hypothesis is both extremely practical and also advances the state
of the art of unit testing by some way. It's easy to use, stable,
and extremely powerful. If you're not using Hypothesis to test your
project then you're missing out.


Required to run:
[devel/py-setuptools] [databases/py-sqlite3] [devel/py-coverage] [lang/python27] [devel/py-enum34] [devel/py-attrs]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: 2349b06a6f2c094bdc5c76b6ec8c40c7d212a3db
RMD160: a8ff3bca8e5afc5901b3a8bc26c7022f6b7f92ae
Filesize: 125.535 KB

Version history: (Expand)


CVS history: (Expand)


   2017-10-16 20:35:19 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: update to 3.33.0

3.33.0:
This release supports strategy inference for more field types in Django models() \ 
- you can now omit an argument for Date, Time, Duration, Slug, IP Address, and \ 
UUID fields.

Strategy generation for fields with grouped choices now selects choices from \ 
each group, instead of selecting from the group names.
   2017-10-05 08:48:38 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-hypothesis: update to 3.31.2:

This release fixes some formatting and small typos/grammar issues in the \ 
documentation, specifically the page docs/settings.rst, and the inline docs for \ 
the various settings.
   2017-09-30 15:12:04 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: update to 3.31.1

3.31.1:

This release improves the handling of deadlines so that they act better with the \ 
shrinking process. This fixes :issue:`892`.

This involves two changes:

1. The deadline is raised during the initial generation and shrinking, and then \ 
lowered to the set value for final replay. This restricts our attention to \ 
examples which exceed the deadline by a more significant margin, which increases \ 
their reliability.

2. When despite the above a test still becomes flaky because it is significantly \ 
faster on rerun than it was on its first run, the error message is now more \ 
explicit about the nature of this problem, and includes both the initial test \ 
run time and the new test run time.

In addition, this release also clarifies the documentation of the deadline \ 
setting slightly to be more explicit about where it applies.
   2017-09-13 08:26:55 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-hypothesis: update to 3.26.0

3.26.0:
Hypothesis now emits deprecation warnings if you are using the legacy SQLite \ 
example database format, or the tool for merging them. These were already \ 
documented as deprecated, so this doesn't change their deprecation status, only \ 
that we warn about it.
   2017-09-08 13:03:28 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
3.24.1:
This release improves the reduction of examples involving floating point numbers \ 
to produce more human readable examples.
It also has some general purpose changes to the way the minimizer works \ 
internally, which may see some improvement in quality and slow down of test case \ 
reduction in cases that have nothing to do with floating point numbers.

3.24.0:
Hypothesis now emits deprecation warnings if you use example() inside a test \ 
function or strategy definition (this was never intended to be supported, but is \ 
sufficiently widespread that it warrants a deprecation path).
   2017-09-04 19:28:45 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
3.23.2:
This is a small refactoring release that removes a now-unused parameter to an \ 
internal API. It shouldn’t have any user visible effect.

3.23.1:
Hypothesis no longer propagates the dynamic scope of settings into strategy \ 
definitions.

This release is a small change to something that was never part of the public \ 
API and you will almost certainly not notice any effect unless you’re doing \ 
something surprising, but for example the following code will now give a \ 
different answer in some circumstances:

import hypothesis.strategies as st
from hypothesis import settings

CURRENT_SETTINGS = st.builds(lambda: settings.default)
(We don’t actually encourage you writing code like this)

Previously this would have generated the settings that were in effect at the \ 
point of definition of CURRENT_SETTINGS. Now it will generate the settings that \ 
are used for the current test.

It is very unlikely to be significant enough to be visible, but you may also \ 
notice a small performance improvement.
   2017-08-27 14:16:07 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
3.22.0:
This release provides what should be a substantial performance improvement to \ 
numpy arrays generated using provided numpy support, and adds a new fill_value \ 
argument to arrays() to control this behaviour.
   2017-08-19 14:16:20 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
3.18.5:
This is a bugfix release for ~hypothesis.strategies.integers. Previously the \ 
strategy would hit an internal assertion if passed non-integer bounds for \ 
min_value and max_value that had no integers between them. The strategy now \ 
raises InvalidArgument instead.