pytest-lockable

What's Changed

• update py-lockable dependency and drop py 3.7 support by @jupe in https://github.com/jupe/pytest-lockable/pull/34

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.9.3...v0.10.0

What's Changed

• accept py-lockable v0.10.0 usage by @jupe in https://github.com/jupe/pytest-lockable/pull/32

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.9.2...v0.9.3

What's Changed

• CI to run py310 by @jupe in https://github.com/jupe/pytest-lockable/pull/31
• update dep:lockable by @jupe in https://github.com/jupe/pytest-lockable/pull/30

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.9.1...v0.9.2

What's Changed

• py-lockable>=0.8.0,<0.9.0 by @juhhov in https://github.com/jupe/pytest-lockable/pull/28

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.9.0...v0.9.1

What's Changed

• add entrypoint for pytest_lockable.plugin by @jupe in https://github.com/jupe/pytest-lockable/pull/26

no need to enable plugin anymore from conftest.py

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.8.3...v0.9.0

What's Changed

• lockable>=0.7.1,<0.8.0 by @juhhov in https://github.com/jupe/pytest-lockable/pull/25

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.8.2...v0.8.3

What's Changed

• Bump lockable from 0.7.0 to 0.7.1 by @dependabot in https://github.com/jupe/pytest-lockable/pull/24

New Contributors

• @dependabot made their first contribution in https://github.com/jupe/pytest-lockable/pull/24

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.8.1...v0.8.2

What's Changed

• Remove autouse from fixtures by @lorjala in https://github.com/jupe/pytest-lockable/pull/23

New Contributors

• @lorjala made their first contribution in https://github.com/jupe/pytest-lockable/pull/23

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.8.0...v0.8.1

What's Changed

• yield Allocation context instead of resource info dictionary by @jupe in https://github.com/jupe/pytest-lockable/pull/22

This is potential breaking change! Allocation -object contains get -method that is backward compatible with previous yielded dict:get().

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.7.5...v0.8.0

What's Changed

• update [email protected] by @jupe in https://github.com/jupe/pytest-lockable/pull/21

This makes possible to get queue duration and allocation duration

Full Changelog: https://github.com/jupe/pytest-lockable/compare/v0.7.4...v0.7.5

Use lockable with HTTP resources support (#19)

Just cleanup setup scripts

• update py-lockable (#15)

This introduce breaking change:
lockable fixture auto_lock() contextmanager yields Allocation instance instead of dictionary.

Example:

Originally:

def test_example2(lockable):
    """ Simple test """
    with lockable.auto_lock({}) as resource_info:
        print(f'Testing with resource#2: {resource_info}')

Now should be:

def test_example2(lockable):
    """ Simple test """
    with lockable.auto_lock({}) as allocation:
        print(f'Testing with resource#2: {allocation.resource_info}')

Just cleanup dependencies:
https://github.com/jupe/py-lockable/compare/v0.3.0..v0.3.1

new locking module causes some breaking changes that is affected here as well.

Breaking changes:

• lockable fixture returns object that contains API's:
  • lock -> Allocation
  • auto_lock -contextmanager -> yields resource info as dict
  • unlock

new dependency: lockable

New feature:
#9 allow to allocate any lockable during test case

Collect locked resource info to metadata when pytest-metadata is installed.