attest
attest copied to clipboard
dag
Modern, Pythonic test automation
Hi Dag, I'm going to use Attest==0.5.3 instead of Unittest for [my project focused on Korean language](https://github.com/sublee/korean). So my test suites contain many Hangul characters (non-ASCII) and are hinted encoding...
Release 0.6
0.5 is now properly broken, with progressbar-2.3-dev being removed from pypi, Attest 0.5 does not even install. Could we _please_ have 0.6 released onto pypi.
When a test is decorated and wrapped in a function that takes `*args, **kwargs` using `functools.wraps`, yielded values from contexts are not passed. The situation that exposed this was using...
The documentation currently says that as long as you import attest before your tests, and your tests import assert_hook, everything will work. This is no longer the case with 0.6,...
Would it be difficult to somehow collect tests from doctest/unittest and build Attest collections from, such that their running is controlled by Attest and its reporters? Optimally, doctests would use...
There is a preferred way to run parametrized texts? For example I'm testing a scientific code on a series of molecules, something like: ``` def calc_energy(molecule, expected_energy): .... ``` I've...
run() should do something more programmatic such as raise different exceptions depending on the outcome of the test run, if it had failures. It should not explicitly exit or raise...
This can shadow bugs where a module is accessed as an attribute of a package. Is there a way to "unport" modules? Deleting them from sys.modules leaves the attributes intact.
- How 'scanning' works - How key=value pairs map to reporter kwargs