Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support report terminal output in Markdown Table format #1418

Closed
sullivancolin opened this issue Jul 8, 2022 · 16 comments
Closed

Support report terminal output in Markdown Table format #1418

sullivancolin opened this issue Jul 8, 2022 · 16 comments
Labels
enhancement New feature or request fixed

Comments

@sullivancolin
Copy link

The current terminal report is great, but wondered if there would be interest in adding a new output format or flag to support markdown table syntax.

This would enable nice display of coverage reports in rendered html that contains the markdown output. Some examples where this might be nice:

  1. Users could used Cog to automate the inclusion of coverage report information in documentation.
  2. GitHub actions workflow summaries could have nicely formatted tables of coverage information, example here

Current appearance:

Name                      Stmts   Miss  Cover
---------------------------------------------
my_program.py                20      4    80%
my_module.py                 15      2    86%
my_other_module.py           56      6    89%
---------------------------------------------
TOTAL                        91     12    87%

Sample Markdown syntax:

| Name               | Stmts      | Miss     |    Cover |
| ------------------ | ---------- | -------- | -------- |
| my_program.py      |         20 |        4 |      80% |
| my_module.py       |         15 |        2 |      86% |
| my_other_module.py |         56 |        6 |      89% |
| **TOTAL**          |     **91** |   **12** |  **87%** |

Sample Rendering:

Name Stmts Miss Cover
my_program.py 20 4 80%
my_module.py 15 2 86%
my_other_module.py 56 6 89%
TOTAL 91 12 87%

Describe the solution you'd like
Ideally the a flag to the default report subcommand could indicate to use markdown syntax like:

$ coverage report --markdown
| Name               | Stmts      | Miss     |    Cover |
| ------------------ | ---------- | -------- | -------- |
| my_program.py      |         20 |        4 |      80% |
| my_module.py       |         15 |        2 |      86% |
| my_other_module.py |         56 |        6 |      89% |
| **TOTAL**          |     **91** |   **12** |  **87%** |
$

This would allow the output to be piped to a file in the GitHub action summary, or captured by cog to inject into a markdown file.

Describe alternatives you've considered
If the report subcommand is not suitable place to add this flag then a new subcommand specifically for markdown reporting might be a good alternative with coverage markdown

$ coverage markdown
| Name               | Stmts      | Miss     |    Cover |
| ------------------ | ---------- | -------- | -------- |
| my_program.py      |         20 |        4 |      80% |
| my_module.py       |         15 |        2 |      86% |
| my_other_module.py |         56 |        6 |      89% |
| **TOTAL**          |     **91** |   **12** |  **87%** |
$ 
@nedbat
Copy link
Owner

nedbat commented Oct 19, 2022

This is an interesting idea. Maybe someone wants to make a pull request for it. Some thoughts:

The markdown should use right alignment for the numeric columns:

| Name               | Stmts      | Miss     |    Cover |
| ------------------ | ---------: | -------: | -------: |
| my_program.py      |         20 |        4 |      80% |
| my_module.py       |         15 |        2 |      86% |
| my_other_module.py |         56 |        6 |      89% |
| **TOTAL**          |     **91** |   **12** |  **87%** |
Name Stmts Miss Cover
my_program.py 20 4 80%
my_module.py 15 2 86%
my_other_module.py 56 6 89%
TOTAL 91 12 87%

I think a --format=markdown, with a default of --format=text would be the best UI.

There will probably need to be some significant refactoring in summary.py to make this work well.

Of course, another option is to generate a JSON report, and then use a separate program to produce the markdown :)

@nedbat nedbat added good first This could be a good first contribution and removed needs triage labels Oct 19, 2022
@stepeos
Copy link
Contributor

stepeos commented Oct 21, 2022

I lke this feature idea, so I'll try to implement this as my first contribution.
Is there a set of coverage files that cover all cases? E.g. I've seen
fmt_skip_covered = "\n%s file%s skipped due to complete coverage."
in the source code.

@nedbat
Copy link
Owner

nedbat commented Oct 21, 2022

Hi, thanks! I'm not sure what you mean by a set of coverage files. The test suite doesn't have stored coverage data files, it generates them as needed. The test suite is large and weird, so it's not always easy to find the right place to tap into it. Let me know if I can add to the contributing docs to help you navigate, or ask here if you need more guidance.

@stepeos
Copy link
Contributor

stepeos commented Oct 22, 2022

So far, this is what I've come up with. (https://github.com/stepeos/coveragepy)

| Name                                                                                         |  Stmts |   Miss |  Cover |  Missing |
|--------------------------------------------------------------------------------------------- | -----: | -----: | -----: | -------: |
| /some/path/to/some/veryelaborate/packe123/coverage\_testing/dummy\_package/\_\_init\_\_.py   |      0 |      0 |   100% |          |
| /some/path/to/some/veryelaborate/packe123/coverage\_testing/dummy\_package/a/\_\_init\_\_.py |      0 |      0 |   100% |          |
| /some/path/to/some/veryelaborate/packe123/coverage\_testing/dummy\_package/a/foo.py          |     24 |      9 |    62% |16, 22-29 |
| /some/path/to/some/veryelaborate/packe123/coverage\_testing/dummy\_package/b/\_\_init\_\_.py |      0 |      0 |   100% |          |
| /some/path/to/some/veryelaborate/packe123/coverage\_testing/dummy\_package/b/bar.py          |     13 |      3 |    77% |    18-20 |
|                                                                                    **TOTAL** | **37** | **12** |**68%** |          |
Name Stmts Miss Cover Missing
/some/path/to/some/veryelaborate/packe123/coverage_testing/dummy_package/__init__.py 0 0 100%
/some/path/to/some/veryelaborate/packe123/coverage_testing/dummy_package/a/__init__.py 0 0 100%
/some/path/to/some/veryelaborate/packe123/coverage_testing/dummy_package/a/foo.py 24 9 62% 16, 22-29
/some/path/to/some/veryelaborate/packe123/coverage_testing/dummy_package/b/__init__.py 0 0 100%
/some/path/to/some/veryelaborate/packe123/coverage_testing/dummy_package/b/bar.py 13 3 77% 18-20
TOTAL 37 12 68%

@stepeos
Copy link
Contributor

stepeos commented Oct 22, 2022

@nedbat
Thanks for the offer. Here's my question. I'm trying to run the unit tests of test_summary.py , but all tests using run_command (e.g. https://github.com/stepeos/coveragepy/blob/b2224765db03ceb40435df7585ed33620a18c861/tests/test_summary.py#L632 )fail, since I work in an environment without coverage installed. Obviously I get the output:
$ /bin/sh: 1: coverage: not found
How do I best go about this, without rewriting all tests?

@nedbat
Copy link
Owner

nedbat commented Oct 22, 2022

Hi, thanks so much for taking this on! It would really help me to understand how you discovered what to do. I tried to write instructions for contributions and running tests, but they might be in the wrong place, or hard to find, or out of date. Your new eyes are a valuable resource for improving them. What instructions were you following?

@stepeos
Copy link
Contributor

stepeos commented Oct 23, 2022

How I discovered what to do:

I cloned the repor and inserted an ordinary coverage file that I created just for the purpose of this contribution.
I then debugged to understand the process of how to report is printed to stdout.
You already mentioned, that the summary.py is the main mechanism behind the reporting, which was my first clue.

About the testing:

I read here about testing.
I just now noticed, that following the documentation and running tox (tox tests/foo.py::bar) does work, whereaspytest foo::bar does not.
I haven't worked with either before and didn't know the difference, so it was my bad, not poor docu. :)

Running the tests with vscode python testing extension(which uses pytest) doesn't work, which is what I tried to do.
But is there a nice way of debuggin tests in vscode, that's not in the documentation?

Also, I started with a fresh miniconda environment and running tox reported missing modules, I think pytest-xdist and hypothesis, which weren't in the requirements.

@nedbat
Copy link
Owner

nedbat commented Oct 23, 2022

Running the tests with vscode python testing extension (which uses pytest) doesn't work, which is what I tried to do.
But is there a nice way of debugging tests in vscode, that's not in the documentation?

Sorry, I don't have experience with VSCode. Can you show what happened when you try to use its testing extension?

Also, I started with a fresh miniconda environment and running tox reported missing modules, I think pytest-xdist and hypothesis, which weren't in the requirements.

I'm not sure which requirements you used. requirements/pytest.txt mentions pytest-xdist and hypothesis, and it's used by tox.ini, so I'm not sure what's going wrong.

@stepeos
Copy link
Contributor

stepeos commented Oct 23, 2022

So with a fresh mniconda environment, after
$ pip install -r requirements/dev.pip
-> zsh: command not found: tox
I can see, that tox is dev.pip, however, this is probably a problem of my configuration?...

Also, when I run tox, I get some errors, but only for py311,pypy3 and py39

py37: commands succeeded
SKIPPED:  py38: InterpreterNotFound: python3.8
ERROR:   py39: commands failed
ERROR:   py310: commands failed
SKIPPED:  py311: InterpreterNotFound: python3.11
SKIPPED:  pypy3: InterpreterNotFound: pypy3
ERROR:   doc: commands failed
ERROR:   lint: could not install deps [-rrequirements/lint.pip]; v = InvocationError('/home/bookboi/Nextcloud/1_Docs/8_Coding/coveragepy/.tox/lint/bin/python -m pip install -U -r 
requirements/lint.pip', 1)

nedbat added a commit that referenced this issue Nov 5, 2022
* refactoring normal reporting text output

* implemented markdown feature from #1418

* minor changes

* fixed text output

* fixed precision for text and markdown report format

* minor changes

* finished testing for markdown format feature

* fixed testing outside test_summary.py

* removed fixed-length widespace padding for tests

* removed whitespaces

* refactoring, fixing  docs, rewriting cmd args

* fixing code quality

* implementing requested changes

* doc fix

* test: add another test of correct report formatting

* fixed precision printing test

* style: adjust the formatting

Co-authored-by: Ned Batchelder <[email protected]>
@nedbat
Copy link
Owner

nedbat commented Nov 5, 2022

This was done in #1479, and finished in 01d8677.

@nedbat nedbat closed this as completed Nov 5, 2022
@nedbat nedbat added fixed and removed good first This could be a good first contribution labels Nov 5, 2022
@webknjaz
Copy link
Contributor

webknjaz commented Dec 1, 2022

@nedbat how about dogfooding this in CI?

I was using irongut/CodeCoverageSummary. Here's an integration example: https://github.com/ansible-community/ansible-test-gh-action/blob/ce3e835/action.yml#L493-L511.
This one requires producing XML output, but it does look nice. See: https://github.com/ansible-collections/community.mysql/actions/runs/3437117181#summary-9412662875. (ignore the "Tests passed" block — it's produced by another action, https://github.com/test-summary/action)

@nedbat
Copy link
Owner

nedbat commented Dec 3, 2022

This is now released as part of coverage 7.0.0b1.

@sullivancolin
Copy link
Author

Tested this out from the beta and it works great! Using it for github actions summary. Thanks so much for adding this. Wish I had been able to help more.

@webknjaz
Copy link
Contributor

@sullivancolin do you have a demo of your summary output?

@sullivancolin
Copy link
Author

sullivancolin commented Dec 13, 2022

@webknjaz I don't have a public project I can share at the moment. It's pretty simple to setup. I add these steps to my GHA CI workflow. Every time it runs, the Summary view will have the markdown formatted table as well as artifacts for the full coverage html report and the raw .coverage data

      - name: Run tests
        run: |
          poetry run coverage run -m pytest
          poetry run coverage report

      - name: Create HTML report
        run: |
          poetry run coverage html
          echo '## Test Coverage Report\n' >> $GITHUB_STEP_SUMMARY
          poetry run coverage report --format=markdown >> $GITHUB_STEP_SUMMARY

      - name: Upload HTML report
        uses: actions/upload-artifact@v3
        with:
          name: coverage_html
          path: htmlcov

      - name: Upload coverage data
        uses: actions/upload-artifact@v3
        with:
          name: coverage
          path: .coverage

@webknjaz
Copy link
Contributor

Thanks, I was mostly curious about the rendering differences.

netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this issue May 5, 2023
Version 7.2.5 — 2023-04-30
--------------------------

- Fix: ``html_report()`` could fail with an AttributeError on ``isatty`` if run
  in an unusual environment where sys.stdout had been replaced.  This is now
  fixed.


Version 7.2.4 — 2023-04-28
--------------------------

PyCon 2023 sprint fixes!

- Fix: with ``relative_files = true``, specifying a specific file to include or
  omit wouldn't work correctly (`issue 1604`_).  This is now fixed, with
  testing help by `Marc Gibbons <pull 1608_>`_.

- Fix: the XML report would have an incorrect ``<source>`` element when using
  relative files and the source option ended with a slash (`issue 1541`_).
  This is now fixed, thanks to `Kevin Brown-Silva <pull 1608_>`_.

- When the HTML report location is printed to the terminal, it's now a
  terminal-compatible URL, so that you can click the location to open the HTML
  file in your browser.  Finishes `issue 1523`_ thanks to `Ricardo Newbery
  <pull 1613_>`_.

- Docs: a new :ref:`Migrating page <migrating>` with details about how to
  migrate between major versions of coverage.py.  It currently covers the
  wildcard changes in 7.x.  Thanks, `Brian Grohe <pull 1610_>`_.

.. _issue 1523: nedbat/coveragepy#1523
.. _issue 1541: nedbat/coveragepy#1541
.. _issue 1604: nedbat/coveragepy#1604
.. _pull 1608: nedbat/coveragepy#1608
.. _pull 1609: nedbat/coveragepy#1609
.. _pull 1610: nedbat/coveragepy#1610
.. _pull 1613: nedbat/coveragepy#1613


Version 7.2.3 — 2023-04-06
--------------------------

- Fix: the :ref:`config_run_sigterm` setting was meant to capture data if a
  process was terminated with a SIGTERM signal, but it didn't always.  This was
  fixed thanks to `Lewis Gaul <pull 1600_>`_, closing `issue 1599`_.

- Performance: HTML reports with context information are now much more compact.
  File sizes are typically as small as one-third the previous size, but can be
  dramatically smaller. This closes `issue 1584`_ thanks to `Oleh Krehel
  <pull 1587_>`_.

- Development dependencies no longer use hashed pins, closing `issue 1592`_.

.. _issue 1584: nedbat/coveragepy#1584
.. _pull 1587: nedbat/coveragepy#1587
.. _issue 1592: nedbat/coveragepy#1592
.. _issue 1599: nedbat/coveragepy#1599
.. _pull 1600: nedbat/coveragepy#1600


Version 7.2.2 — 2023-03-16
--------------------------

- Fix: if a virtualenv was created inside a source directory, and a sourced
  package was installed inside the virtualenv, then all of the third-party
  packages inside the virtualenv would be measured.  This was incorrect, but
  has now been fixed: only the specified packages will be measured, thanks to
  `Manuel Jacob <pull 1560_>`_.

- Fix: the ``coverage lcov`` command could create a .lcov file with incorrect
  LF (lines found) and LH (lines hit) totals.  This is now fixed, thanks to
  `Ian Moore <pull 1583_>`_.

- Fix: the ``coverage xml`` command on Windows could create a .xml file with
  duplicate ``<package>`` elements. This is now fixed, thanks to `Benjamin
  Parzella <pull 1574_>`_, closing `issue 1573`_.

.. _pull 1560: nedbat/coveragepy#1560
.. _issue 1573: nedbat/coveragepy#1573
.. _pull 1574: nedbat/coveragepy#1574
.. _pull 1583: nedbat/coveragepy#1583


Version 7.2.1 — 2023-02-26
--------------------------

- Fix: the PyPI page had broken links to documentation pages, but no longer
  does, closing `issue 1566`_.

- Fix: public members of the coverage module are now properly indicated so that
  mypy will find them, fixing `issue 1564`_.

.. _issue 1564: nedbat/coveragepy#1564
.. _issue 1566: nedbat/coveragepy#1566


Version 7.2.0 — 2023-02-22
--------------------------

- Added a new setting ``[report] exclude_also`` to let you add more exclusions
  without overwriting the defaults.  Thanks, `Alpha Chen <pull 1557_>`_,
  closing `issue 1391`_.

- Added a :meth:`.CoverageData.purge_files` method to remove recorded data for
  a particular file.  Contributed by `Stephan Deibel <pull 1547_>`_.

- Fix: when reporting commands fail, they will no longer congratulate
  themselves with messages like "Wrote XML report to file.xml" before spewing a
  traceback about their failure.

- Fix: arguments in the public API that name file paths now accept pathlib.Path
  objects.  This includes the ``data_file`` and ``config_file`` arguments to
  the Coverage constructor and the ``basename`` argument to CoverageData.
  Closes `issue 1552`_.

- Fix: In some embedded environments, an IndexError could occur on stop() when
  the originating thread exits before completion.  This is now fixed, thanks to
  `Russell Keith-Magee <pull 1543_>`_, closing `issue 1542`_.

- Added a ``py.typed`` file to announce our type-hintedness.  Thanks,
  `KotlinIsland <pull 1550_>`_.

.. _issue 1391: nedbat/coveragepy#1391
.. _issue 1542: nedbat/coveragepy#1542
.. _pull 1543: nedbat/coveragepy#1543
.. _pull 1547: nedbat/coveragepy#1547
.. _pull 1550: nedbat/coveragepy#1550
.. _issue 1552: nedbat/coveragepy#1552
.. _pull 1557: nedbat/coveragepy#1557


Version 7.1.0 — 2023-01-24
--------------------------

- Added: the debug output file can now be specified with ``[run] debug_file``
  in the configuration file.  Closes `issue 1319`_.

- Performance: fixed a slowdown with dynamic contexts that's been around since
  6.4.3.  The fix closes `issue 1538`_.  Thankfully this doesn't break the
  `Cython change`_ that fixed `issue 972`_.  Thanks to Mathieu Kniewallner for
  the deep investigative work and comprehensive issue report.

- Typing: all product and test code has type annotations.

.. _Cython change: nedbat/coveragepy#1347
.. _issue 972: nedbat/coveragepy#972
.. _issue 1319: nedbat/coveragepy#1319
.. _issue 1538: nedbat/coveragepy#1538

Version 7.0.5 — 2023-01-10
--------------------------

- Fix: On Python 3.7, a file with type annotations but no ``from __future__
  import annotations`` would be missing statements in the coverage report. This
  is now fixed, closing `issue 1524`_.

.. _issue 1524: nedbat/coveragepy#1524


Version 7.0.4 — 2023-01-07
--------------------------

- Performance: an internal cache of file names was accidentally disabled,
  resulting in sometimes drastic reductions in performance.  This is now fixed,
  closing `issue 1527`_.   Thanks to Ivan Ciuvalschii for the reproducible test
  case.

.. _issue 1527: nedbat/coveragepy#1527


Version 7.0.3 — 2023-01-03
--------------------------

- Fix: when using pytest-cov or pytest-xdist, or perhaps both, the combining
  step could fail with ``assert row is not None`` using 7.0.2.  This was due to
  a race condition that has always been possible and is still possible. In
  7.0.1 and before, the error was silently swallowed by the combining code.
  Now it will produce a message "Couldn't combine data file" and ignore the
  data file as it used to do before 7.0.2.  Closes `issue 1522`_.

.. _issue 1522: nedbat/coveragepy#1522


Version 7.0.2 — 2023-01-02
--------------------------

- Fix: when using the ``[run] relative_files = True`` setting, a relative
  ``[paths]`` pattern was still being made absolute.  This is now fixed,
  closing `issue 1519`_.

- Fix: if Python doesn't provide tomllib, then TOML configuration files can
  only be read if coverage.py is installed with the ``[toml]`` extra.
  Coverage.py will raise an error if TOML support is not installed when it sees
  your settings are in a .toml file. But it didn't understand that
  ``[tools.coverage]`` was a valid section header, so the error wasn't reported
  if you used that header, and settings were silently ignored.  This is now
  fixed, closing `issue 1516`_.

- Fix: adjusted how decorators are traced on PyPy 7.3.10, fixing `issue 1515`_.

- Fix: the ``coverage lcov`` report did not properly implement the
  ``--fail-under=MIN`` option.  This has been fixed.

- Refactor: added many type annotations, including a number of refactorings.
  This should not affect outward behavior, but they were a bit invasive in some
  places, so keep your eyes peeled for oddities.

- Refactor: removed the vestigial and long untested support for Jython and
  IronPython.

.. _issue 1515: nedbat/coveragepy#1515
.. _issue 1516: nedbat/coveragepy#1516
.. _issue 1519: nedbat/coveragepy#1519


Version 7.0.1 — 2022-12-23
--------------------------

- When checking if a file mapping resolved to a file that exists, we weren't
  considering files in .whl files.  This is now fixed, closing `issue 1511`_.

- File pattern rules were too strict, forbidding plus signs and curly braces in
  directory and file names.  This is now fixed, closing `issue 1513`_.

- Unusual Unicode or control characters in source files could prevent
  reporting.  This is now fixed, closing `issue 1512`_.

- The PyPy wheel now installs on PyPy 3.7, 3.8, and 3.9, closing `issue 1510`_.

.. _issue 1510: nedbat/coveragepy#1510
.. _issue 1511: nedbat/coveragepy#1511
.. _issue 1512: nedbat/coveragepy#1512
.. _issue 1513: nedbat/coveragepy#1513


Version 7.0.0 — 2022-12-18
--------------------------

Nothing new beyond 7.0.0b1.


Version 7.0.0b1 — 2022-12-03
----------------------------

A number of changes have been made to file path handling, including pattern
matching and path remapping with the ``[paths]`` setting (see
:ref:`config_paths`).  These changes might affect you, and require you to
update your settings.

(This release includes the changes from `6.6.0b1 <changes_6-6-0b1_>`_, since
6.6.0 was never released.)

- Changes to file pattern matching, which might require updating your
  configuration:

  - Previously, ``*`` would incorrectly match directory separators, making
    precise matching difficult.  This is now fixed, closing `issue 1407`_.

  - Now ``**`` matches any number of nested directories, including none.

- Improvements to combining data files when using the
  :ref:`config_run_relative_files` setting, which might require updating your
  configuration:

  - During ``coverage combine``, relative file paths are implicitly combined
    without needing a ``[paths]`` configuration setting.  This also fixed
    `issue 991`_.

  - A ``[paths]`` setting like ``*/foo`` will now match ``foo/bar.py`` so that
    relative file paths can be combined more easily.

  - The :ref:`config_run_relative_files` setting is properly interpreted in
    more places, fixing `issue 1280`_.

- When remapping file paths with ``[paths]``, a path will be remapped only if
  the resulting path exists.  The documentation has long said the prefix had to
  exist, but it was never enforced.  This fixes `issue 608`_, improves `issue
  649`_, and closes `issue 757`_.

- Reporting operations now implicitly use the ``[paths]`` setting to remap file
  paths within a single data file.  Combining multiple files still requires the
  ``coverage combine`` step, but this simplifies some single-file situations.
  Closes `issue 1212`_ and `issue 713`_.

- The ``coverage report`` command now has a ``--format=`` option.  The original
  style is now ``--format=text``, and is the default.

  - Using ``--format=markdown`` will write the table in Markdown format, thanks
    to `Steve Oswald <pull 1479_>`_, closing `issue 1418`_.

  - Using ``--format=total`` will write a single total number to the
    output.  This can be useful for making badges or writing status updates.

- Combining data files with ``coverage combine`` now hashes the data files to
  skip files that add no new information.  This can reduce the time needed.
  Many details affect the speed-up, but for coverage.py's own test suite,
  combining is about 40% faster. Closes `issue 1483`_.

- When searching for completely un-executed files, coverage.py uses the
  presence of ``__init__.py`` files to determine which directories have source
  that could have been imported.  However, `implicit namespace packages`_ don't
  require ``__init__.py``.  A new setting ``[report]
  include_namespace_packages`` tells coverage.py to consider these directories
  during reporting.  Thanks to `Felix Horvat <pull 1387_>`_ for the
  contribution.  Closes `issue 1383`_ and `issue 1024`_.

- Fixed environment variable expansion in pyproject.toml files.  It was overly
  broad, causing errors outside of coverage.py settings, as described in `issue
  1481`_ and `issue 1345`_.  This is now fixed, but in rare cases will require
  changing your pyproject.toml to quote non-string values that use environment
  substitution.

- An empty file has a coverage total of 100%, but used to fail with
  ``--fail-under``.  This has been fixed, closing `issue 1470`_.

- The text report table no longer writes out two separator lines if there are
  no files listed in the table.  One is plenty.

- Fixed a mis-measurement of a strange use of wildcard alternatives in
  match/case statements, closing `issue 1421`_.

- Fixed internal logic that prevented coverage.py from running on
  implementations other than CPython or PyPy (`issue 1474`_).

- The deprecated ``[run] note`` setting has been completely removed.

.. _implicit namespace packages: https://peps.python.org/pep-0420/
.. _issue 608: nedbat/coveragepy#608
.. _issue 649: nedbat/coveragepy#649
.. _issue 713: nedbat/coveragepy#713
.. _issue 757: nedbat/coveragepy#757
.. _issue 991: nedbat/coveragepy#991
.. _issue 1024: nedbat/coveragepy#1024
.. _issue 1212: nedbat/coveragepy#1212
.. _issue 1280: nedbat/coveragepy#1280
.. _issue 1345: nedbat/coveragepy#1345
.. _issue 1383: nedbat/coveragepy#1383
.. _issue 1407: nedbat/coveragepy#1407
.. _issue 1418: nedbat/coveragepy#1418
.. _issue 1421: nedbat/coveragepy#1421
.. _issue 1470: nedbat/coveragepy#1470
.. _issue 1474: nedbat/coveragepy#1474
.. _issue 1481: nedbat/coveragepy#1481
.. _issue 1483: nedbat/coveragepy#1483
.. _pull 1387: nedbat/coveragepy#1387
.. _pull 1479: nedbat/coveragepy#1479



Version 6.6.0b1 — 2022-10-31
----------------------------

(Note: 6.6.0 final was never released. These changes are part of `7.0.0b1
<changes_7-0-0b1_>`_.)

- Changes to file pattern matching, which might require updating your
  configuration:

  - Previously, ``*`` would incorrectly match directory separators, making
    precise matching difficult.  This is now fixed, closing `issue 1407`_.

  - Now ``**`` matches any number of nested directories, including none.

- Improvements to combining data files when using the
  :ref:`config_run_relative_files` setting:

  - During ``coverage combine``, relative file paths are implicitly combined
    without needing a ``[paths]`` configuration setting.  This also fixed
    `issue 991`_.

  - A ``[paths]`` setting like ``*/foo`` will now match ``foo/bar.py`` so that
    relative file paths can be combined more easily.

  - The setting is properly interpreted in more places, fixing `issue 1280`_.

- Fixed environment variable expansion in pyproject.toml files.  It was overly
  broad, causing errors outside of coverage.py settings, as described in `issue
  1481`_ and `issue 1345`_.  This is now fixed, but in rare cases will require
  changing your pyproject.toml to quote non-string values that use environment
  substitution.

- Fixed internal logic that prevented coverage.py from running on
  implementations other than CPython or PyPy (`issue 1474`_).

.. _issue 991: nedbat/coveragepy#991
.. _issue 1280: nedbat/coveragepy#1280
.. _issue 1345: nedbat/coveragepy#1345
.. _issue 1407: nedbat/coveragepy#1407
.. _issue 1474: nedbat/coveragepy#1474
.. _issue 1481: nedbat/coveragepy#1481
nedbat added a commit that referenced this issue Dec 21, 2023
These were lost in commit cf1efa8

commit cf1efa8
Author: stepeos <82703776 [email protected]>
Date:   Sat Nov 5 17:29:04 2022  0100

    feat: report terminal output in Markdown Table format #1418 (#1479)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request fixed
Projects
None yet
Development

No branches or pull requests

4 participants