Green

23 June 2017

- Green now supports unittest's `load_test` protocol. Contributed by Martin
Larralde in 160. Resolves 87.

- Add support for a `[green]` configuration section inside of `setup.cfg` in
the current working directory. See the `CONFIG FILES` section of `green
--help` for a list of relative configuration file priority and how to use them.
Contributed by Martin Larralde in 161.

- Minor grammar/spelling fixes.

7 May 2017

- Work around Python's failure to skip tests in a consistent way -- in
particular, if SkipTest was raised in setUpClass(), then different versions
of Python did different things, none of them very sensible. We take the
approach that Python _should have_ taken and skip each test as the SkipTest
exception is raised. This results in one skip entry per test in the class
that was skipped. Resolves 159.

- Fixed the warning in Python 3.6 due to an inadvertent double-import issue.

- Fixed crash that could occur running self-tests on newer versions of Python
2.7 which expect to use an iterator with a next() function.

29 April 2017

- An unexpectedSuccess does not count as a failure for the test run as a whole,
so `-f, --failfast` has been updated so that an unexpectedSuccess no longer
triggers early termination. Using expectedFailure is discouraged.

27 April 2017

- Green now also searches the current working directory for a .green config
file. This can be used as per-project configuration -- just place the .green
config file for your project in the same directory you would run your tests
from (usually the root of the project). See `green --help` for the
resolution order of the various config files. Resolves 116.

26 April 2017

- Added a page about the Udemy course
[Python Testing with Green](https://github.com/CleanCut/green/blob/main/PythonTestingWithGreen.md),
with lots of nice coupons and discount codes just for finding the Github
page. Check it out!

- PyPy support is now best-effort for all versions of PyPy. TravisCI's PyPy
installations are just...flaky. They seem to work everywhere else, we just
don't fail due to failing PyPy builds anymore, because we just can't take the
weirdness.

- Fixed a condition where green could return failure to the calling shell if
only a small number of skips, expectedFailures, and unexpectedSuccesses were
run (and no passes, fails, or errors).

- Improved the help message for `-l, --logging`

24 March 2017

- Fixed a green crash that could occur when dealing with unicode literals in
raised exceptions under Python 2.