Mutatest

Latest version: v3.1.0

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

Scan your dependencies

Page 1 of 6

3.1.0

~~~~~

- Maintenance patches and API changes to skip/only category selection.

3.0.2

~~~~~

- `Maintenance patch 27 <https://github.com/EvanKepner/mutatest/pull/27>`_ updating source
code conditional logic in the CLI argument parsing.
- Minor fixes for the most updated CI checks.

3.0.1

~~~~~

- `Bug fix 24 <https://github.com/EvanKepner/mutatest/issues/24>`_ where the bit-shift
operators where not being applied during mutation trials and raised ``KeyError``.
- A new ``test_all_op_types.py`` ensures all mutation substitutions work as intended.

3.0.0

~~~~~

- ``Mutatest`` has reached a level of maturity to warrant a stable release.
With the addition of the multiprocessing capabilities, support for ``coverage`` versions
4.x and 5.x, support for Python 3.7 and 3.8, being installable through ``pip`` or
``conda``, and with Azure Pipelines CI for platform tests, the tool and API are
unlikely to change in a major way without moving to ``4.0.0``.

New in this release:

- Multiprocessing support on Python 3.8!
- The new ``--parallel`` command argument will instruct ``mutatest`` to use
multiprocessing for mutation trials. See the documentation for complete details.

- Bug fix in ``mutatest.cache.create_cache_dirs()`` where the cache directory did not
include "parents" in case of packages with nested directories without existing pycache.
- Removal of the ``sr`` subcategory of slice mutations (``Slice_RC`` for range changes).
These were rare, and supporting both Python 3.7 and 3.8 required excessive complexity.
The ``su`` category remains valid as the primary slice mutation set.


Beta Releases
-------------

2.2.0

~~~~~

- Added support for specifying settings in ``setup.cfg`` using either ``[mutatest]`` or
``[tool:mutatest]`` sections in addition to the ``mutatest.ini`` file.

2.1.3

~~~~~

- Addressing test issues on Windows platform in the coverage tests by adding a
``resolve_source`` flag to the ``CoverageFilter.filter`` method.

Page 1 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.