mutmut 3.0.5__py3-none-any.whl

mutmut/result_browser_layout.tcss

@@ -0,0 +1,26 @@
+Screen {
+    layout: vertical;
+}
+.container {
+    layout: horizontal;
+    height: 50%;
+}
+
+
+DataTable {
+    color: #c0c0c0;
+}
+
+DataTable:focus {
+    color: white;
+}
+
+.datatable--cursor {
+    color: black;
+    background: white;
+}
+
+DataTable:focus .datatable--cursor {
+    color: black;
+    background: orange;
+}

mutmut-3.0.5.dist-info/AUTHORS.rst

@@ -0,0 +1,22 @@
+=======
+Credits
+=======
+
+* Anders Hovmöller <boxed@killingar.net>
+* Felipe Pontes <felipemfpontes@gmail.com>
+* William Orr <will@worrbase.com>
+* Trevin Gandhi <trevin.gandhi@petuum.com>
+* Daniel Hahler <git@thequod.de>
+* Marcelo Da Cruz Pinto
+* Jakub Stolarski
+* Hristo Georgiev
+* Savo Kovačević <savo.s.kovacevic@gmail.com>
+* Nathan Klapstein <nklapste@ualberta.ca>
+* Brian Skinn <brian.skinn@gmail.com>
+* Jim Jazwiecki <jim.jazwiecki@gmail.com>
+* neroks <gneroks@gmail.com>
+* John Vandenberg <jayvdb@gmail.com>
+* Luca Simonetto <luca.simonetto.94@gmail.com>
+* Emil Stenström <emil@emilstenstrom.se>
+* Roxane Bellott <roxane.bellot@gmail.com>
+* Tomáš Chvátal <tchvatal@suse.com>

mutmut-3.0.5.dist-info/LICENSE

@@ -0,0 +1,12 @@
+Copyright (c) 2016, Anders Hovmöller
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
+
+* Neither the name of mutmut nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

mutmut-3.0.5.dist-info/METADATA

@@ -0,0 +1,201 @@
+Metadata-Version: 2.1
+Name: mutmut
+Version: 3.0.5
+Summary: mutation testing for Python 3
+Home-page: https://github.com/boxed/mutmut
+Author: Anders Hovmöller
+Author-email: boxed@killingar.net
+License: BSD
+Keywords: mutmut mutant mutation test testing
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: BSD License
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.7
+License-File: LICENSE
+License-File: AUTHORS.rst
+Requires-Dist: parso
+Requires-Dist: click
+Requires-Dist: junit-xml==1.8
+Requires-Dist: setproctitle
+Requires-Dist: textual
+
+mutmut - python mutation tester
+===============================
+
+.. image:: https://github.com/boxed/mutmut/actions/workflows/tests.yml/badge.svg
+    :target: https://github.com/boxed/mutmut/actions/workflows/tests.yml
+
+.. image:: https://readthedocs.org/projects/mutmut/badge/?version=latest
+    :target: https://mutmut.readthedocs.io/en/latest/?badge=latest
+    :alt: Documentation Status
+
+
+Mutmut is a mutation testing system for Python, with a strong focus on ease
+of use. If you don't know what mutation testing is try starting with
+`this article <https://kodare.net/2016/12/01/mutmut-a-python-mutation-testing-system.html>`_.
+
+Some highlight features:
+
+- Found mutants can be applied on disk with a simple command making it very
+  easy to work with the results
+- Remembers work that has been done, so you can work incrementally
+- Knows which tests to execute, speeding up mutation testing
+- Interactive terminal based UI
+- Parallel and fast execution
+
+.. image:: browse_screenshot.png
+
+
+If you want to mutate code outside of functions, you can try using mutmut 2,
+which has a different execution model than mutmut 3+.
+
+
+Requirements
+------------
+
+Mutmut must be run on a system with `fork` support. This means that if you want
+to run on windows, you must run inside WSL.
+
+
+
+Install and run
+---------------
+
+You can get started with a simple:
+
+.. code-block:: console
+
+    pip install mutmut
+    mutmut run
+
+This will by run pytest on tests in the "tests" or "test" folder and
+it will try to figure out where the code to mutate is.
+
+
+
+.. code-block:: ini
+
+    [mutmut]
+    paths_to_mutate=src/
+    tests_dir=tests/
+
+You can stop the mutation run at any time and mutmut will restart where you
+left off. It will continue where it left off, and re-test functions that were
+modified since last run.
+
+To work with the results, use `mutmut browse` where you can see the mutants,
+retest them when you've updated your tests.
+
+You can also write a mutant to disk from the `browse` interface, or via
+`mutmut apply <mutant>`. You should **REALLY** have the file you mutate under
+source code control and committed before you apply a mutant!
+
+
+Wildcards for testing mutants
+-----------------------------
+
+Unix filename pattern matching style on mutants is supported. Example:
+
+.. code-block:: console
+
+    mutmut run "my_module*"
+    mutmut run "my_module.my_function*"
+
+In the `browse` TUI you can press `f` to retest a function, and `m` to retest
+an entire module.
+
+
+"also copy" files
+-----------------
+
+To run the full test suite some files are often needed above the tests and the
+source. You can configure to copy extra files that you need by adding
+directories and files to `also_copy` in your `setup.cfg`:
+
+.. code-block:: ini
+
+    also_copy=
+        iommi/snapshots/
+        conftest.py
+
+
+Limit stack depth
+-----------------
+
+In big code bases some functions are called incidentally by huge swaths of the
+codebase, but you really don't want tests that hit those executions to count
+for mutation testing purposes. Incidentally tested functions lead to slow
+mutation testing as hundreds of tests can be checked for things that should
+have clean and fast unit tests, and it leads to bad test suites as any
+introduced bug in those base functions will lead to many tests that fail which
+are hard to understand how they relate to the function with the change.
+
+You can configure mutmut to only count a test as being relevant for a function
+if the stack depth from the test to the function is below some limit. In your
+`setup.cfg` add:
+
+.. code-block:: ini
+
+    max_stack_depth=8
+
+A lower value will increase mutation speed and lead to more localized tests,
+but will also lead to more surviving mutants that would otherwise have been
+caught.
+
+
+Exclude files from mutation
+---------------------------
+
+You can exclude files from mutation in `setup.cfg`:
+
+.. code-block::
+
+    do_not_mutate=
+        *__tests.py
+
+
+Whitelisting
+------------
+
+You can mark lines like this:
+
+.. code-block:: python
+
+    some_code_here()  # pragma: no mutate
+
+to stop mutation on those lines. Some cases we've found where you need to
+whitelist lines are:
+
+- The version string on your library. You really shouldn't have a test for this :P
+- Optimizing break instead of continue. The code runs fine when mutating break
+  to continue, but it's slower.
+
+
+Example mutations
+-----------------
+
+- Integer literals are changed by adding 1. So 0 becomes 1, 5 becomes 6, etc.
+- `<` is changed to `<=`
+- break is changed to continue and vice versa
+
+In general the idea is that the mutations should be as subtle as possible.
+See `__init__.py` for the full list.
+
+
+Workflow
+--------
+
+This section describes how to work with mutmut to enhance your test suite.
+
+1. Run mutmut with `mutmut run`. A full run is preferred but if you're just
+   getting started you can exit in the middle and start working with what you
+   have found so far.
+2. Show the mutants with `mutmut browse`
+3. Find a mutant you want to work on and write a test to try to kill it.
+4. Press `r` to rerun the mutant and see if you successfully managed to kill it.
+
+Mutmut keeps the data of what it has done and the mutants in the `mutants/`
+directory.If  you want to make sure you run a full mutmut run you can delete
+this directory to start from scratch.

mutmut-3.0.5.dist-info/RECORD

@@ -0,0 +1,10 @@
+mutmut/__init__.py,sha256=HDQy_am_TuPHZQGTFVSeaJsaYvF7L-9AseXHuX4SFE8,8905
+mutmut/__main__.py,sha256=-JP2n6tis1VwLcJQkQDXnmxu90boUwQwS42nnL8caO4,48325
+mutmut/result_browser_layout.tcss,sha256=w7HZ-Ox3KwkgqEijpLbcQOCvV9NmzWEEIx9aF7m4MJs,311
+mutmut-3.0.5.dist-info/AUTHORS.rst,sha256=8TSzLFfqqHsxF0EtnJidExV1CtJkhgsUOG94JIticS8,687
+mutmut-3.0.5.dist-info/LICENSE,sha256=uy76yP7fDHTtI37Via4XLfFIkEpXgafsmZkJLcr29Dk,1471
+mutmut-3.0.5.dist-info/METADATA,sha256=dtht_92SHZsqJe54UnJwzGZScf7VXetavskVW4jG89M,5980
+mutmut-3.0.5.dist-info/WHEEL,sha256=eOLhNAGa2EW3wWl_TU484h7q1UNgy0JXjjoqKoxAAQc,92
+mutmut-3.0.5.dist-info/entry_points.txt,sha256=qjOZfcGw95gooit1WRIYz-DB9IQ1atqRSTaHTI5CoTs,47
+mutmut-3.0.5.dist-info/top_level.txt,sha256=kkYeffNQuAzat-wZ_8Om-BNrYRgqG6krGvNO6aRMfiA,7
+mutmut-3.0.5.dist-info/RECORD,,

mutmut-3.0.5.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: bdist_wheel (0.44.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

mutmut-3.0.5.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+mutmut = mutmut.__main__:cli

mutmut-3.0.5.dist-info/top_level.txt

@@ -0,0 +1 @@
+mutmut