Skip to content

Latest commit

 

History

History
82 lines (54 loc) · 4.08 KB

CHANGELOG.md

File metadata and controls

82 lines (54 loc) · 4.08 KB

Changelog

Version v1.0.0

  • Date: 2024-02-03
  • Version: >=3.8 and <=3.12
  • Note : this version break major versioning, because old acceptation test fail for this reason

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…
  • Modified --lock argument, now target only test with lock fixture
    • The tests with the lock fixture had skipped status, now they have passed status
    • The tests without the lock fixture had passed status, now they have skipped status

branch: "feature/fixture-lock-pickle"

  • Status: Finish
  • Note: This branch requires that the branch "feature/fixture-lock-method" be finalized.
  • Add pickle extension for lock.lock to support more types of data
  • Now pickle is the default extension for lock.lock if no extension is specified

branch: "feature/fixture-lock-clean"

  • Status: Start
  • Note: This branch requires that the branch "feature/fixture-lock-method" be finalized.
  • If test use --lock and --clean argument, then clean all unused cache files
  • If test use --lock and --clean argument and --only-skip argument, then do anything, it's certainly a mistake (why clean only test with existing lock ?)
  • If test use --lock and --clean argument and --simulate argument, list all unused cache files who will be removed without remove them.
  • If test use --lock and --clean argument and --lock-date argument, thrown exception (can't lock a remove cache file)

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

Version v0.1.0

  • Date: 2024-01-xx
  • Version: xxxxxx

The package upload tests on Pypi were awkwardly carried out with version v0.1.0 and v0.1.1, the package being defective, these were removed but Pypi refuses to change the package contents even after use, even if no download has been made. The first version is therefore v0.1.2.