SatelliteQE / satellite-populate

This new module adds tools and commands to populate and validate entities in the system based in YAML file.
Other
8 stars 10 forks source link

Update pytest to 3.3.1 #112

Closed pyup-bot closed 6 years ago

pyup-bot commented 6 years ago

There's a new version of pytest available. You are currently using 3.2.1. I have updated it to 3.3.1

These links might come in handy: PyPI | Changelog | Repo | Homepage

Changelog

3.3.1

=========================

Bug Fixes

  • Fix issue about -p no:<plugin> having no effect. (2920 <https://github.com/pytest-dev/pytest/issues/2920>_)

  • Fix regression with warnings that contained non-strings in their arguments in Python 2. (2956 <https://github.com/pytest-dev/pytest/issues/2956>_)

  • Always escape null bytes when setting PYTEST_CURRENT_TEST. (2957 <https://github.com/pytest-dev/pytest/issues/2957>_)

  • Fix ZeroDivisionError when using the testmon plugin when no tests were actually collected. (2971 <https://github.com/pytest-dev/pytest/issues/2971>_)

  • Bring back TerminalReporter.writer as an alias to TerminalReporter._tw. This alias was removed by accident in the 3.3.0 release. (2984 <https://github.com/pytest-dev/pytest/issues/2984>_)

  • The pytest-capturelog plugin is now also blacklisted, avoiding errors when running pytest with it still installed. (3004 <https://github.com/pytest-dev/pytest/issues/3004>_)

Improved Documentation

  • Fix broken link to plugin pytest-localserver. (2963 <https://github.com/pytest-dev/pytest/issues/2963>_)

Trivial/Internal Changes

  • Update github "bugs" link in CONTRIBUTING.rst (2949 <https://github.com/pytest-dev/pytest/issues/2949>_)

3.3.0

=========================

Deprecations and Removals

  • Pytest no longer supports Python 2.6 and 3.3. Those Python versions are EOL for some time now and incur maintenance and compatibility costs on the pytest core team, and following up with the rest of the community we decided that they will no longer be supported starting on this version. Users which still require those versions should pin pytest to <3.3. (2812 <https://github.com/pytest-dev/pytest/issues/2812>_)

  • Remove internal _preloadplugins() function. This removal is part of the pytest_namespace() hook deprecation. (2636 <https://github.com/pytest-dev/pytest/issues/2636>_)

  • Internally change CallSpec2 to have a list of marks instead of a broken mapping of keywords. This removes the keywords attribute of the internal CallSpec2 class. (2672 <https://github.com/pytest-dev/pytest/issues/2672>_)

  • Remove ParameterSet.deprecated_argdict - its not a public api and the lack of the underscore was a naming error. (2675 <https://github.com/pytest-dev/pytest/issues/2675>)

  • Remove the internal multi-typed attribute Node._evalskip and replace it with the boolean Node._skipped_by_mark. (2767 <https://github.com/pytest-dev/pytest/issues/2767>_)

  • The params list passed to pytest.fixture is now for all effects considered immutable and frozen at the moment of the pytest.fixture call. Previously the list could be changed before the first invocation of the fixture allowing for a form of dynamic parametrization (for example, updated from command-line options), but this was an unwanted implementation detail which complicated the internals and prevented some internal cleanup. See issue 2959 <https://github.com/pytest-dev/pytest/issues/2959>_ for details and a recommended workaround.

Features

  • pytest_fixture_post_finalizer hook can now receive a request argument. (2124 <https://github.com/pytest-dev/pytest/issues/2124>_)

  • Replace the old introspection code in compat.py that determines the available arguments of fixtures with inspect.signature on Python 3 and funcsigs.signature on Python 2. This should respect __signature__ declarations on functions. (2267 <https://github.com/pytest-dev/pytest/issues/2267>_)

  • Report tests with global pytestmark variable only once. (2549 <https://github.com/pytest-dev/pytest/issues/2549>_)

  • Now pytest displays the total progress percentage while running tests. The previous output style can be set by configuring the console_output_style setting to classic. (2657 <https://github.com/pytest-dev/pytest/issues/2657>_)

  • Match warns signature to raises by adding match keyword. (2708 <https://github.com/pytest-dev/pytest/issues/2708>_)

  • Pytest now captures and displays output from the standard logging module. The user can control the logging level to be captured by specifying options in pytest.ini, the command line and also during individual tests using markers. Also, a caplog fixture is available that enables users to test the captured log during specific tests (similar to capsys for example). For more information, please see the logging docs <https://docs.pytest.org/en/latest/logging.html>. This feature was introduced by merging the popular pytest-catchlog <https://pypi.org/project/pytest-catchlog/> plugin, thanks to Thomas Hisch <https://github.com/thisch>. Be advised that during the merging the backward compatibility interface with the defunct pytest-capturelog has been dropped. (2794 <https://github.com/pytest-dev/pytest/issues/2794>)

  • Add allow_module_level kwarg to pytest.skip(), enabling to skip the whole module. (2808 <https://github.com/pytest-dev/pytest/issues/2808>_)

  • Allow setting file_or_dir, -c, and -o in PYTESTADDOPTS. (2824 <https://github.com/pytest-dev/pytest/issues/2824>)

  • Return stdout/stderr capture results as a namedtuple, so out and err can be accessed by attribute. (2879 <https://github.com/pytest-dev/pytest/issues/2879>_)

  • Add capfdbinary, a version of capfd which returns bytes from readouterr(). (2923 <https://github.com/pytest-dev/pytest/issues/2923>_)

  • Add capsysbinary a version of capsys which returns bytes from readouterr(). (2934 <https://github.com/pytest-dev/pytest/issues/2934>_)

  • Implement feature to skip setup.py files when run with --doctest-modules. (502 <https://github.com/pytest-dev/pytest/issues/502>_)

Bug Fixes

  • Resume output capturing after capsys/capfd.disabled() context manager. (1993 <https://github.com/pytest-dev/pytest/issues/1993>_)

  • pytest_fixture_setup and pytest_fixture_post_finalizer hooks are now called for all conftest.py files. (2124 <https://github.com/pytest-dev/pytest/issues/2124>_)

  • If an exception happens while loading a plugin, pytest no longer hides the original traceback. In python2 it will show the original traceback with a new message that explains in which plugin. In python3 it will show 2 canonized exceptions, the original exception while loading the plugin in addition to an exception that PyTest throws about loading a plugin. (2491 <https://github.com/pytest-dev/pytest/issues/2491>_)

  • capsys and capfd can now be used by other fixtures. (2709 <https://github.com/pytest-dev/pytest/issues/2709>_)

  • Internal pytester plugin properly encodes bytes arguments to utf-8. (2738 <https://github.com/pytest-dev/pytest/issues/2738>_)

  • testdir now uses use the same method used by tmpdir to create its temporary directory. This changes the final structure of the testdir directory slightly, but should not affect usage in normal scenarios and avoids a number of potential problems. (2751 <https://github.com/pytest-dev/pytest/issues/2751>_)

  • Pytest no longer complains about warnings with unicode messages being non-ascii compatible even for ascii-compatible messages. As a result of this, warnings with unicode messages are converted first to an ascii representation for safety. (2809 <https://github.com/pytest-dev/pytest/issues/2809>_)

  • Change return value of pytest command when --maxfail is reached from 2 (interrupted) to 1 (failed). (2845 <https://github.com/pytest-dev/pytest/issues/2845>_)

  • Fix issue in assertion rewriting which could lead it to rewrite modules which should not be rewritten. (2939 <https://github.com/pytest-dev/pytest/issues/2939>_)

  • Handle marks without description in pytest.ini. (2942 <https://github.com/pytest-dev/pytest/issues/2942>_)

Trivial/Internal Changes

  • pytest now depends on attrs <https://pypi.org/project/attrs/> for internal structures to ease code maintainability. (2641 <https://github.com/pytest-dev/pytest/issues/2641>)

  • Refactored internal Python 2/3 compatibility code to use six. (2642 <https://github.com/pytest-dev/pytest/issues/2642>_)

  • Stop vendoring pluggy - we're missing out on its latest changes for not much benefit (2719 <https://github.com/pytest-dev/pytest/issues/2719>_)

  • Internal refactor: simplify ascii string escaping by using the backslashreplace error handler in newer Python 3 versions. (2734 <https://github.com/pytest-dev/pytest/issues/2734>_)

  • Remove unnecessary mark evaluator in unittest plugin (2767 <https://github.com/pytest-dev/pytest/issues/2767>_)

  • Calls to Metafunc.addcall now emit a deprecation warning. This function is scheduled to be removed in pytest-4.0. (2876 <https://github.com/pytest-dev/pytest/issues/2876>_)

  • Internal move of the parameterset extraction to a more maintainable place. (2877 <https://github.com/pytest-dev/pytest/issues/2877>_)

  • Internal refactoring to simplify scope node lookup. (2910 <https://github.com/pytest-dev/pytest/issues/2910>_)

  • Configure pytest to prevent pip from installing pytest in unsupported Python versions. (2922 <https://github.com/pytest-dev/pytest/issues/2922>_)

3.2.5

=========================

Bug Fixes

  • Remove py<1.5 restriction from pytest as this can cause version conflicts in some installations. (2926 <https://github.com/pytest-dev/pytest/issues/2926>_)

3.2.4

=========================

Bug Fixes

  • Fix the bug where running with --pyargs will result in items with empty parent.nodeid if run from a different root directory. (2775 <https://github.com/pytest-dev/pytest/issues/2775>_)

  • Fix issue with pytest.parametrize if argnames was specified as keyword arguments. (2819 <https://github.com/pytest-dev/pytest/issues/2819>_)

  • Strip whitespace from marker names when reading them from INI config. (2856 <https://github.com/pytest-dev/pytest/issues/2856>_)

  • Show full context of doctest source in the pytest output, if the line number of failed example in the docstring is < 9. (2882 &lt;https://github.com/pytest-dev/pytest/issues/2882&gt;_)

  • Match fixture paths against actual path segments in order to avoid matching folders which share a prefix. (2836 &lt;https://github.com/pytest-dev/pytest/issues/2836&gt;_)

Improved Documentation

  • Introduce a dedicated section about conftest.py. (1505 &lt;https://github.com/pytest-dev/pytest/issues/1505&gt;_)

  • Explicitly mention xpass in the documentation of xfail. (1997 &lt;https://github.com/pytest-dev/pytest/issues/1997&gt;_)

  • Append example for pytest.param in the example/parametrize document. (2658 &lt;https://github.com/pytest-dev/pytest/issues/2658&gt;_)

  • Clarify language of proposal for fixtures parameters (2893 &lt;https://github.com/pytest-dev/pytest/issues/2893&gt;_)

  • List python 3.6 in the documented supported versions in the getting started document. (2903 &lt;https://github.com/pytest-dev/pytest/issues/2903&gt;_)

  • Clarify the documentation of available fixture scopes. (538 &lt;https://github.com/pytest-dev/pytest/issues/538&gt;_)

  • Add documentation about the python -m pytest invocation adding the current directory to sys.path. (911 &lt;https://github.com/pytest-dev/pytest/issues/911&gt;_)

3.2.3

=========================

Bug Fixes

  • Fix crash in tab completion when no prefix is given. (2748 &lt;https://github.com/pytest-dev/pytest/issues/2748&gt;_)

  • The equality checking function (__eq__) of MarkDecorator returns False if one object is not an instance of MarkDecorator. (2758 &lt;https://github.com/pytest-dev/pytest/issues/2758&gt;_)

  • When running pytest --fixtures-per-test: don't crash if an item has no fixtureinfo attribute (e.g. doctests) (2788 &lt;https://github.com/pytest-dev/pytest/issues/2788&gt;)

Improved Documentation

  • In help text of -k option, add example of using not to not select certain tests whose names match the provided expression. (1442 &lt;https://github.com/pytest-dev/pytest/issues/1442&gt;_)

  • Add note in parametrize.rst about calling metafunc.parametrize multiple times. (1548 &lt;https://github.com/pytest-dev/pytest/issues/1548&gt;_)

Trivial/Internal Changes

  • Set xfail_strict=True in pytest's own test suite to catch expected failures as soon as they start to pass. (2722 &lt;https://github.com/pytest-dev/pytest/issues/2722&gt;_)

  • Fix typo in example of passing a callable to markers (in example/markers.rst) (2765 &lt;https://github.com/pytest-dev/pytest/issues/2765&gt;_)

3.2.2

=========================

Bug Fixes

  • Calling the deprecated request.getfuncargvalue() now shows the source of the call. (2681 &lt;https://github.com/pytest-dev/pytest/issues/2681&gt;_)

  • Allow tests declared as staticmethod to use fixtures. (2699 &lt;https://github.com/pytest-dev/pytest/issues/2699&gt;_)

  • Fixed edge-case during collection: attributes which raised pytest.fail when accessed would abort the entire collection. (2707 &lt;https://github.com/pytest-dev/pytest/issues/2707&gt;_)

  • Fix ReprFuncArgs with mixed unicode and UTF-8 args. (2731 &lt;https://github.com/pytest-dev/pytest/issues/2731&gt;_)

Improved Documentation

  • In examples on working with custom markers, add examples demonstrating the usage of pytest.mark.MARKER_NAME.with_args in comparison with pytest.mark.MARKER_NAME.__call__ (2604 &lt;https://github.com/pytest-dev/pytest/issues/2604&gt;_)

  • In one of the simple examples, use pytest_collection_modifyitems() to skip tests based on a command-line option, allowing its sharing while preventing a user error when acessing pytest.config before the argument parsing. (2653 &lt;https://github.com/pytest-dev/pytest/issues/2653&gt;_)

Trivial/Internal Changes

  • Fixed minor error in 'Good Practices/Manual Integration' code snippet. (2691 &lt;https://github.com/pytest-dev/pytest/issues/2691&gt;_)

  • Fixed typo in goodpractices.rst. (2721 &lt;https://github.com/pytest-dev/pytest/issues/2721&gt;_)

  • Improve user guidance regarding --resultlog deprecation. (2739 &lt;https://github.com/pytest-dev/pytest/issues/2739&gt;_)

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

pyup-bot commented 6 years ago

Closing this in favor of #113