Green

Latest version: v4.0.2

Safety actively analyzes 687881 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 16

3.4.1

20 January 2021

- Fixed a situation where syntax errors in a test file were being silently ignored, resulting in the entire test file being omitted from the test. This would happen if the module with a syntax error was loaded via specifying a "dot name" such as `mymodule.MyClass.mytest` as the target to test. Now green reliably crashes in this situation. Note that this changes the behavior for syntax errors when initiated with a filename target. Previously specifying the test target as a filename such as `mymodule.py` that had a syntax error in it would result in converting the loading exception into a single test failure representing the inability to load a test file. Now, we simply crash on the syntax error. In practice, I believe this is an improvement...as syntax errors are easy to fix, and folks are used to hitting the crash and fixing them, while obscuring them behind a custom test failure is not only unusual, it's also a lot of work to make it happen inside green.

3.4.0

12 January 2021

- Four levels of verbosity (`-vvvv` on the command line or `verbose=4` in the config) now displays the test method name _and_ the test method docstring. Resolves 252.

3.3.0

15 July 2021

- Added `-X NUM, --maxtasksperchild NUM` to force worker processes to exit and respawn after a certain number of tasks so that we could use it in integration tests to force the condition fixed below. A "task" is typically the suite of tests from a single file.
- Fixed processes failing to respawn on Python 3.8+. In the happy path, processes never die, so there is no problem. In the sad path, if all processes got killed before all test suites had been run then Green would hang forever with a queue of tests to run without any worker processes to run them. Resolves 250.

3.2.6

25 April 2021

- Color is now properly emitted on Windows runners in GitHub Actions. See 245.
- Unexpected successes now count as failures like they do in unittest. Resolves 241.
- Fix internal coverage not reporting in CI + other internal CI improvements

3.2.5

23 Nov 2020

- Fix failing/erroring SubTests not properly reporting output to stdout/stderr. Resolves 238.

3.2.4

1 Nov 2020

- Fix `-j/--junit-report` so that it writes to the properly-named file when specified from a config file. Contributed by jwaschkau in 236.
- Fix Windows CI by dropping a broken Python 2 test.

Page 2 of 16

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.