Bug#1040009: ITP: python-pytest-trio -- Pytest plugin for trio
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer <fladi@debian.org>
X-Debbugs-Cc: debian-devel@lists.debian.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
* Package name : python-pytest-trio
Version : 0.8.0
Upstream Contact: Emmanuel Leblond <emmanuel.leblond@gmail.com>
* URL : https://github.com/python-trio/pytest-trio
* License : Apache-2 or Expat
Programming Lang: Python
Description : Pytest plugin for trio
This is a pytest plugin to help you test projects that use Trio, a friendly
library for concurrency and async I/O in Python.
.
Features include:
* Async tests without the boilerplate: just write
async def test_whatever(): ....
* Useful fixtures included: use autojump_clock for easy testing of code with
timeouts, or nursery to easily set up background tasks.
* Write your own async fixtures: set up an async database connection or start
a server inside a fixture, and then use it in your tests.
* If you have multiple async fixtures, pytest-trio will even do setup/teardown
concurrently whenever possible. (Though honestly, we’re not sure whether this
is a good idea or not and might remove it in the future. If it makes your
tests harder to debug, or conversely provides you with big speedups, please
let us know.)
* Integration with the fabulous Hypothesis library, so your async tests can
use property-based testing: just use @given like you’re used to.
* Support for testing projects that use Trio exclusively and want to use
pytest-trio everywhere, and also for testing projects that support multiple
async libraries and only want to enable pytest-trio’s features for a subset
of their test suite.
I intend to maintain this as part of DPT.
-----BEGIN PGP SIGNATURE-----
iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmSfWT8RHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90Wof5Af/aSsk4H4lC/krkrH4g0jq70eXUQJsbRAF
35oBmDJ55+9ttlhDO20epFZ+58bB57aJnDBHs+EgoFpsEBLAcErPGu4tZS5zEbyG
Fiy90PYRDpvSQV2zNT4IkR2Dko5dyQkDP8vanwOPe0i/jy3Ec9zYJlvCN7E/YyDL
qgw8VwDaNkVR7W02/NGqccOax3TmZw2FNOSkxkwABYii46gSFwgdgxLAv3VtlNTA
f1xcHoOpAKB9DX8kFHquciRdFuiTKWiVA3200A1z4LtIyYQl9o/K0E7KIFsL4niG
8utjegs+x4onxt3La/q2aboqSCZlFqQOG2nsc7JtEuYdVAiCoX7Jiw==
=p6Jq
-----END PGP SIGNATURE-----
Reply to: