Releases: jupe/pytest-lockable
Releases · jupe/pytest-lockable
fix allocation_timeout argument
v0.7.4 use int type for allocation_timeout argument (#20)
Update lockable dependency
Use lockable with HTTP resources support (#19)
update lockable dependency
v0.7.2 [email protected] (#18)
Cleanup project
Just cleanup setup scripts
auto_lock returns Allocation object
- 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}')
cleanup and update dependencies
Just cleanup dependencies:
https://github.com/jupe/py-lockable/compare/v0.3.0..v0.3.1
update locking module
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 asdict
unlock
extract core functionality to separate library
new dependency: lockable
Custom allocation
New feature:
#9 allow to allocate any lockable during test case
pytest-metadata integration
Collect locked resource info to metadata when pytest-metadata
is installed.