v0.1.2

Version v0.1.2

• Date: 2024-01-27
• Version: >=3.8 and <=3.12

branch: "feature/lock-fixture"

• Status: Finish
• Note: Branch containing the base of the pytest fixture 'lock', it must be able to easily integrate new functions, CLI arguments, etc…

• Add fixtures lock

branch: "feature/fixtures-lock-method"

• Status: Finish
• Note: This branch requires that the branch "feature/lock-fixture" be finalized.

• Add fixtures method lock.lock to lock the result of a test to a cache file

  • If test use lock.lock and result was not locked, exception is thrown

  • If test use lock.lock result is in the cache file and is the same as the result of the test, test is valid

  • If test use lock.lock result is in the cache file and is not the same as the result of the test, test is invalid (failed)

  • If test use lock.lock and --lock in cli argument, then start test and lock the result in cache file.

  • If test use lock.lock and --simulate in cli argument, then simulate the result of the test, not write to the cache file.

  • If test use lock.lock and --only-skip in cli argument, then don't update lock if the result was not locked.

  • If test use lock.lock and --lock-date in cli argument, then lock the result of the test to a cache file with the date of the lock, if date was expired, then the test is failed

  • If test use --simulate argument and not --lock argument, then it's invalid, throw exception

  • If test use --lock-date argument and not --lock argument, then it's invalid, throw exception

  • If test use --only-skip argument and not --lock argument, then it's invalid, throw exception

branch: "feature/fixture-lock-date-support"

• Status: Finish
• Note: This branch requires that the branch "feature/fixture-lock-method" be finalized.

• Add support for pytest --lock --lock-date 13/12/2023, if test has lock fixture, then lock the result of the
  test to a cache file with the date of the lock, if date was expired, then the test is skipped

---