2016-10-19 14:45:00 by Thomas Klausner | Files touched by this commit (1) |
Log message:
Add a comment about possible dependencies.
|
2016-10-19 14:42:56 by Thomas Klausner | Files touched by this commit (3) |
Log message:
Updated py-hypothesis to 3.5.3.
3.5.3 - 2016-10-05
This is a bug fix release.
Bugs fixed:
If the same test was running concurrently in two processes and there were \
examples already in the test database which no longer failed, Hypothesis would \
sometimes fail with a FileNotFoundError (IOError on Python 2) because an example \
it was trying to read was deleted before it was read. (Issue #372).
Drawing from an integers() strategy with both a min_value and a max_value \
would reject too many examples needlessly. Now it repeatedly redraws until \
satisfied. (Pull request #366. Thanks to Calen Pennington for the contribution).
3.5.2 - 2016-09-24
This is a bug fix release.
The Hypothesis pytest plugin broke pytest support for doctests. Now it \
doesnât.
3.5.1 - 2016-09-23
This is a bug fix release.
Hypothesis now runs cleanly in -B and -BB modes, avoiding mixing bytes and \
unicode.
unittest.TestCase tests would now have shown up in the new statistics mode. \
Now they do.
Similarly, stateful tests would not have shown up in statistics and now they do.
Statistics now print with pytest node IDs (the names youâd get in \
pytest verbose mode).
3.5.0 - 2016-09-22
This is a feature release.
fractions() and decimals() strategies now support min_value and max_value \
parameters. Thanks go to Anne Mulhern for the development of this feature.
The Hypothesis pytest plugin now supports a âhypothesis-show-statistics \
parameter that gives detailed statistics about the tests that were run. Huge \
thanks to Jean-Louis Fuchs and Adfinis-SyGroup for funding the development of \
this feature.
There is a new event() function that can be used to add custom statistics.
Additionally there have been some minor bug fixes:
In some cases Hypothesis should produce fewer duplicate examples (this will \
mostly only affect cases with a single parameter).
py.test command line parameters are now under an option group for Hypothesis \
(thanks to David Keijser for fixing this)
Hypothesis would previously error if you used function annotations on your \
tests under Python 3.4.
The repr of many strategies using lambdas has been improved to include the \
lambda body (this was previously supported in many but not all cases).
|
2016-08-24 12:20:35 by Thomas Klausner | Files touched by this commit (3) | |
Log message:
Updated py-hypothesis to 3.4.2.
3.4.2 - 2016-07-13
This is a bug fix release, fixing a number of problems with the settings system:
Test functions defined using @given can now be called from other threads \
(Issue #337)
Attempting to delete a settings property would previously have silently done \
the wrong thing. Now it raises an AttributeError.
Creating a settings object with a custom database_file parameter was \
silently getting ignored and the default was being used instead. Now itâs \
not.
3.4.1 - 2016-07-07
This is a bug fix release for a single bug:
On Windows when running two Hypothesis processes in parallel (e.g. using \
pytest-xdist) they could race with each other and one would raise an exception \
due to the non-atomic nature of file renaming on Windows and the fact that you \
canât rename over an existing file. This is now fixed.
3.4.0 - 2016-05-27
This release is entirely provided by Lucas Wiman:
models() strategies from hypothesis.extra.django will now respect much more of \
Djangoâs validations out of the box. Wherever possible full_clean() should \
succeed.
In particular:
The max_length, blank and choices kwargs are now respected.
Add support for DecimalField.
If a field includes validators, the list of validators are used to filter \
the field strategy.
3.3.0 - 2016-05-27
This release went wrong and is functionally equivalent to 3.2.0. Ignore it.
3.2.0 - 2016-05-19
This is a small single-feature release:
All tests using @given now fix the global random seed. This removes the \
health check for that. If a non-zero seed is required for the final falsifying \
example, it will be reported. Otherwise Hypothesis will assume randomization was \
not a significant factor for the test and be silent on the subject. If you use \
the random_module() strategy this will continue to work and will always display \
the seed.
3.1.3 - 2016-05-01
Single bug fix release
Another charmap problem. In 3.1.2 text/characters would break on systems \
which had /tmp/ mounted on a different partition than the Hypothesis storage \
directory (usually in home). This fixes that.
3.1.2 - 2016-04-30
Single bug fix release:
Anything which used a text() or characters() strategy was broken on Windows \
and I hadnât updated appveyor to use the new repository location so I \
didnât notice. This is now fixed and windows support should work correctly.
3.1.1 - 2016-04-29
Minor bug fix release.
Fix concurrency issue when running tests that use text() from multiple \
processes at once (Bug #302, thanks to Alex Chan).
Improve performance of code using lists with max_size (thanks to Cristi \
Cobzarenco).
Fix install on Python 2 with ancient versions of pip so that it installs the \
enum34 backport (thanks to Donald Stufft for telling me how to do this).
Remove duplicated __all__ exports from hypothesis.strategies (thanks to \
Piët Delport).
Update headers to point to new repository location.
Allow use of strategies that canât be used in find() (e.g. choices) in \
stateful testing.
|
2016-08-22 15:16:16 by Thomas Klausner | Files touched by this commit (1) |
Log message:
Add missing py-sqlite3 dependency. Bump PKGREVISION.
|
2016-06-08 19:49:20 by Thomas Klausner | Files touched by this commit (15) |
Log message:
Switch to MASTER_SITE_PYPI.
|
2016-04-24 11:44:35 by Thomas Klausner | Files touched by this commit (4) |
Log message:
Import py-hypothesis-3.1.0 as devel/py-hypothesis.
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.
|