All Versions
87
Latest Version
Avg Release Cycle
44 days
Latest Release
-

Changelog History
Page 7

  • v2.0.0 Changes

    24 July 2015

    • 💥 BREAKING CHANGE: Major overhaul of the multiprocessing system. Tests always run in a separate worker process, even when only one process is specified. The default number of processes is now the number of logical processors detected instead of 1. Entire modules are now run in the same worker process by default to avoid both the overhead of multiple processes loading the same module and the overhead of running module and class setUp/tearDown multiple times redundantly. Classes or methods specified individually on the command-line will still be run in their own worker process. A ton of credit for this feature needs to go to Sam Spilsbury, who put in considerable time and effort to actually code up the initial pull request. Fixes issues #68, #70.

    • 💥 BREAKING CHANGE: Due the fact that no one uses it that I can tell and I don't want to maintain it, the -m/--html option has been removed.

    • 💥 BREAKING CHANGE: -o/--omit-patterns now adds patterns to the default coverage omit list instead of replacing the default list.

    • 0️⃣ -O/--clear-omit was added to clear the default coverage omit list.

    • -k/--no-skip-report was added to suppress the skip report if desired.

    • ➕ Added a gitter chatroom link to the readme.

    • 👌 Support for acquiring and releasing arbitrary resources via the -i/--initializer and -z/--finalizer options. Use it to setup/teardown things that an individual worker process will need exclusive access to apart from the other worker processes.

    • ✅ We're back at 100% self-test coverage again. Yay!!!

    • Twisted's skip functionality is caught and recorded as skips instead of failures, if your TestCase subclasses twisted.trial.unittest.TestCase and sets the class attribute .skip to True, or a test raises twisted.trial.unittest.SkipTest.

    • 👍 Better handling of outside-of-test exceptions that occur inside worker processes.

    • ✅ We now capture stderr that is emitted during tests and present it after tests have run, just like we do with stdout.

    • 👷 Capturing stdout in worker processes more consistently works (no known bugs left).

    • 👍 The headers for stdout and stderr are now yellow, for better color scheme consistency (and so they don't get confused with skip headers).

    • ✅ Skip report headers now display the dotted test name in bold, just like other headers do. We are so consistent!

    • 🛠 Fixed the skip report so it goes to the stream instead of stdout.

    • ⚠ Disabled the annoying "Coverage.py warning: No data was collected." message that started happening a lot, even though coverage was working just fine.

    • 🏗 Colors now work on AppVeyor builds, all hail the pretty colors! (Ironically, they don't support Windows ansi colors, they wrote their own interpreters for posix-style color escape codes.)

    • We now "close" the process pool instead of "terminating" it, which results in much better behavior in pypy and Windows, especially for things like tearDown stuff.

  • v1.11.0 Changes

    18 June 2015

    • ➕ Added support for pypy3. Fiixes issue #63.

    • ✅ Disabled the virtual-env aspect of test_versions when run in Travis-CI, which is already in a virtualenv.

  • v1.10.0 Changes

    17 June 2015

    • ✅ Virtualenv directories are now skipped during test discovery, so you can now use discovery on projects that contain one or more virtualenv directories inside of them.

    • Green always runs tests in a separate process now, though by default it still (currently) defaults to only one separate process, to maximize compatibility with large suites that already assume tests are run sequentially.

    • ✅ Green will now catch exceptions that the test framework doesn't handle and report them as test failures. Specifically, if your test case subclasses testtools.TestCase from the popular testtools project, then SystemExit exceptions will escape the TestCase. Green will catch these exceptions and report them as failures. The one special-case is KeyboardInterrupt, which Green catches and interprets as a desire to terminate testing, and stops the test run.

    • 🔄 Changed the -m/--html help text to be a deprecation warning. If you would like this feature to stay, please create an issue stating so at https://github.com/CleanCut/green/issues/new

  • v1.9.4 Changes

    15 June 2015

    • ➕ Added a deprecation warning for the -m/--html option. Unless I get some credible requests to leave the functionality, then I am going to proceed with removing it under the assumption that no one uses it (and I don't want to maintain complex, unused code).

    • Investigated an issue with SystemExit and KeyboardInterrupt halting the python process when your test subclasses testtools.TestCase. Turns out that that is a design decision made by the testtools devs that they want those exceptions to stop everything. So we won't interfere with their desires. If you don't like the behavior, either stop subclassing testtools.TestCase or simply catch those two exceptions in your own tests.

  • v1.9.3 Changes

    7 June 2015

    • 🏁 Switched to cyan instead of blue on Windows only.

    • 👍 Stubbed in the beginnings of support for designating initialization to run in each process to obtain whatever resources might be needed by a single process (like its own database, for example).

  • v1.9.2 Changes

    8 May 2015
    • 🛠 Fixed a regression that caused the -a/--allow-stdout cli option and corresponding config option to be ignored. Fixes issue #58.

  • v1.9.1 Changes

    13 April 2015

    • ✅ Don't do the interactive print/reprint a test line behavior when we're not connected to a terminal. Contributed by Sam Spilsbury. Issue #52. Pull request #53.

    • 🛠 Fixed a rather largeish bug that caused all configuration files to be ignored. Issue #56. Thanks for Monty Hindman for finding and reporting the bug.

    • The g script has been improved so that wildcards are passed through without local expansion. g is is used by developers to try out changes to green itself in-place without installing it. Contributed by Monty Hindman. Pull request #57.

    • 🏗 Switch to Travis CI's docker builders for faster builds. Contributed by Sam Spilsbury. Issue #54. Pull request #55.

    • Cleaned up the formatting of dates on this changelog file.

    • ✂ Removed Python 3.3 builders on Linux, now that they're failing. Official support for Python 3.3 was dropped on 31 August 2014. It may still work in various use cases, but no guarantees.

    • 🛠 Fixed test_versions again. The regex for non-Travis CI builds had broken, so that only the default python was being tested on development setups.

  • v1.9.0 Changes

    8 April 2015

    • 💥 BREAKING CHANGE: --omit was renamed to --omit-patterns for consistency with how other pattern-related options are named.

    • 💥 BREAKING CHANGE: --pattern was renamed to --file-pattern for consistency with how other pattern-related options are named.

    • ➕ Added -n / --test-pattern option to further refine which tests are actually run. Thanks to Monty Hindman for a pull request that got this feature going.

    • 🏗 Tweaked Travis CI builds

  • v1.8.1 Changes

    1 April 2015 (Not a joke!)

    • 🛠 Fixed issue where command-line arguments could not override config 0️⃣ arguments to set options back to default values. Reported by Monty Hindman. Issue #47.

    • Converted this changelog file to markdown format.

  • v1.8.0 Changes

    30 March 2015

    • The tag to use for questions on StackOverflow was changed to python-green to avoid being too generic. The tag has a nice wiki entry and an initial question to get things going. Contributed by Mikko Ohtamaa. Pull request #43.

    • ➕ Added -p/--pattern option to specify the file pattern to search for tests under instead of the default pattern test*py. Contributed by Monty Hindman. Issue #41. Pull request #42.

    • 👍 Green now supports nose-parameterized. Contributed by Sam Spilsbury. Issue #39. Pull request #40.

    • 🛠 Fixed a crash that could occur in PyPy 2.5

    • 🛠 Fixed a crash that could occur during automated build testing with pip 6.x

    • 💅 Colorama is now a dependency on all platforms (dropping python-termstyle as a dependency is planned).