Pytest-play

------------------

- Documentation improvements

- Add bzt/Taurus/BlazeMeter compatibility

------------------

- Small documentation improvements

- Now ``test_XXX.json`` files are automatically collected and executed

- You can run a test scenario using the pytest CLI ``pytest test_YYY.json``

- Introduced json test scenario ini file with markers definition. For a given
``test_YYY.json`` scenario you can add a ``test_YYY.ini`` ini file::

[pytest]
markers =
marker1
marker2

and filter scenarios using marker expressions ``pytest -m marker1``

- Enabled parametrization of arguments for a plain json scenario in scenario ini file::

[pytest]
test_data =
{"username": "foo"}
{"username": "bar"}

and your json scenario will be executed twice

- ``pytest-play`` loads some variables based on the contents of the optional ``pytest-play``
section in your ``pytest-variables`` file now. So if your variables file contains the following
values::

pytest-play:
foo: bar
date_format: YYYYMMDD

you will be able to use expressions ``$foo``, ``$date_format``, ``variables['foo']`` or
``variables['date_format']``

------------------

- Add ``sorted`` in python expressions

------------------

- Add more tests

- Documentation update

- play_json fixture no more assumes that you
have some pytest-variables settings.
No more mandatory

- fix include scenario bug that occurs only
on Windows (slash vs backslash and
JSON decoding issues)

------------------

- documentation improvements

- supports teardown callbacks

------------------

- implement python based commands in ``pytest-play`` and
deprecates ``play_python``.
So this feature is a drop-in replacement for the
``play-python`` plugin.

You should no more install ``play_python`` since now.

- update documentation

- deprecate selenium commands (they will be implemented
on a separate plugin and dropped in
``pytest-play`` >= 2.0.0). All your previous scripts
will work fine, this warning is just for people
directly importing the provider for some reason.

- implement skip conditions. You can omit the execution of
any command evaluating a Python based skip condition