Skip to content

Releases: jupe/pytest-lockable

fix allocation_timeout argument

22 Sep 10:10
0c5cb16
Compare
Choose a tag to compare
v0.7.4

use int type for allocation_timeout argument (#20)

Update lockable dependency

19 Aug 08:45
beaff35
Compare
Choose a tag to compare

Use lockable with HTTP resources support (#19)

update lockable dependency

08 Jun 07:27
748511b
Compare
Choose a tag to compare

Cleanup project

08 May 14:25
0354a9b
Compare
Choose a tag to compare

Just cleanup setup scripts

auto_lock returns Allocation object

14 Apr 20:04
Compare
Choose a tag to compare
  • 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

16 Mar 12:38
1808547
Compare
Choose a tag to compare

update locking module

05 Oct 07:15
e9928a6
Compare
Choose a tag to compare
update locking module Pre-release
Pre-release

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

extract core functionality to separate library

03 Oct 06:38
867d2e6
Compare
Choose a tag to compare

new dependency: lockable

Custom allocation

20 Jul 07:19
213d923
Compare
Choose a tag to compare

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

pytest-metadata integration

07 Jul 05:50
887fa73
Compare
Choose a tag to compare

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