Testing-fixtures

Latest version: v0.4.1

Safety actively analyzes 626727 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

0.4.1

Fix

* fix: remove unnecessary noqa (54)

- CI has started to complain about this ([`2387b18`](https://github.com/abid-mujtaba/testing-fixtures/commit/2387b186ef7b5fed05dab521465fd1ba89f48e98))

0.4.0

Chore

* chore: refactor tox requirements (52)

- Put the test deps in requirements-test.txt.
- Put the lint deps in requirements-lint.txt and also include
requirements-test.txt in it.
- Create a new dev-py312 environment which uses an editable install.
This will serve as the development environment for VS Code. ([`d29cb8f`](https://github.com/abid-mujtaba/testing-fixtures/commit/d29cb8f46fc9d7567fbcf1c4991aa87dbd7f2dc7))

Documentation

* docs: added notes on evolution uptill Nov 2023 (51)

documented the new CI/CD pipeline ([`748e2c8`](https://github.com/abid-mujtaba/testing-fixtures/commit/748e2c8a98cf4355cefab41708b3334c10cfc151))

Feature

* feat: add commonly used utility fixtures (53)

- add a new `.utils` submodule
- add create_temp_dir and create_temp_cwd utility fixtures
- refactor vscode settings
- make mypy strict ([`9edf0f4`](https://github.com/abid-mujtaba/testing-fixtures/commit/9edf0f4e7dccd0f77f4042a3831155d12cfd1f9c))

Style

* style(core): apply new ruff format rules (50)

ruff has acquired a new format rule where even function definitions with
a single argument that are split across multiple lines should have a
trailing comma after that single argument ([`ae2c5fc`](https://github.com/abid-mujtaba/testing-fixtures/commit/ae2c5fc0248939bf32f2577b4a677060e36614f8))

0.3.0

Ci

* ci: add semantic-pr workflow (47)

Ensure that the PR title follows semantic commit style
otherwise version bumping won&39;t work because
it looks at the commit titles to figure out if a bump is required and
the category of bump ([`509ac27`](https://github.com/abid-mujtaba/testing-fixtures/commit/509ac27238db5f57ef58548f847fbb1b0682adb3))

Feature

* feat: bump version to include deps (49)

- Need a commit using semantic convention to trigger a bump version to
pick up the latest change which was to add typing-extension as a dep ([`9d585d8`](https://github.com/abid-mujtaba/testing-fixtures/commit/9d585d827994dfa853e08738b64291b48218f6cb))

Unknown

* Bump version to incorporate new deps (48)

feat: bump version to incorporate new deps

- typing-extensions was added as a dependency but was not incorporated
because the commit didn&39;t have semantic style.
- we have added a github action to validate that can no longer happen
- still need to bump the version to include the new dep ([`6ba5364`](https://github.com/abid-mujtaba/testing-fixtures/commit/6ba536441a62bcec013f3f9c00b43b24cdf10773))

* Add typing-extensions as dependency (46)

Used by library to support lower versions of Python ([`7d2b4a3`](https://github.com/abid-mujtaba/testing-fixtures/commit/7d2b4a39b0172fe257bcc43bbf02fca2b8f03b0d))

0.2.4

Fix

* fix: remove unnecessary fetch-depth config (45)

- the only component of CI/CD that needs access to the full commit history is
the version bumping logic (sematnic-release)
- bring the setup-python actions into consistency with each other ([`16fad96`](https://github.com/abid-mujtaba/testing-fixtures/commit/16fad96401f08cac6a21475bf591833f2c81f6c3))

0.2.3

Ci

* ci: format config (43)

no functional change just add some whitespace and
remove unnecessary name of the checkout step ([`40e8fe2`](https://github.com/abid-mujtaba/testing-fixtures/commit/40e8fe2b360d7cb604b940d5a3dda6062b9857f0))

Fix

* fix: use ruff check and format (44)

* ci: add ruff (check & format), remove black

- ruff check is fantastic
- ruff format is a drop-in replacement for black (in particular the upcoming preview)
the only places where ruff disagrees with black I agree with the former

* ci: configure ruff

- select all rules
- disable the 4 rules globally that conflict with ruff format
- disable certain rules on a per-file basis
- assert is allowed in tests
- we are using print in the unit tests to track execution

* fix: ruff errors

fix all errors detected by ruff after we turned on nearly all the rules

* ci: configure vscode to use ruff

helps find and fix ruff errors ([`c1b1526`](https://github.com/abid-mujtaba/testing-fixtures/commit/c1b1526b1e9eec471888f94d750b82bb414e7a14))

0.2.2

Fix

* fix: semantic-release committer name (42)

the switch to the upstream semantic-release action meant that
the committer name changed from semantic-release to github-actions

we explicitly configure the action to use the former name since that is
what is expected by the other publish workflow ([`480cf2a`](https://github.com/abid-mujtaba/testing-fixtures/commit/480cf2a68f11cd6b60a78a3d23187a24dcc14ff5))

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.