Go to file
Ran Benita f86e4516eb junitxml: convert from py.xml to xml.etree.ElementTree
Part of the effort to reduce dependency on the py library.

Besides that, py.xml implements its own XML serialization which is
pretty scary.

I tried to keep the code with minimal changes (though it could use some
cleanups). The differences in behavior I have noticed are:

- Attributes in the output are not sorted.

- Some unneeded escaping is no longer performed, for example escaping
  `"` to `"` in a text node.
2020-07-29 10:52:21 +03:00
.github Merge pull request #7304 from asottile/cache_pre_commit 2020-06-09 10:56:42 -03:00
bench Add rudimentary mypy type checking 2019-07-09 12:12:07 -07:00
changelog junitxml: convert from py.xml to xml.etree.ElementTree 2020-07-29 10:52:21 +03:00
doc/en Update markers.rst (#7563) 2020-07-29 09:10:13 +02:00
extra pre-commit: upgrade flake8 3.7.7 -> 3.8.1 2020-05-12 09:29:40 +03:00
scripts Update text and links in announce templates 2020-07-28 17:29:09 -03:00
src junitxml: convert from py.xml to xml.etree.ElementTree 2020-07-29 10:52:21 +03:00
testing junitxml: convert from py.xml to xml.etree.ElementTree 2020-07-29 10:52:21 +03:00
.coveragerc Ignore "assert False" statements in coverage 2020-02-15 17:08:01 +02:00
.gitattributes Add codecov support to AppVeyor and remove coveralls 2018-09-05 19:50:06 -03:00
.gitblameignore Add .gitblameignore (#6848) 2020-03-04 05:32:30 +01:00
.gitignore Add pyproject.toml support (#7247) 2020-06-08 10:03:10 -03:00
.pre-commit-config.yaml Type annotate _pytest.debugging (a bit) 2020-06-05 11:34:20 +03:00
.travis.yml ci: fix Travis (#236) (#6786) 2020-02-21 12:50:54 +01:00
AUTHORS docs: Add a note about -q option used in getting started guide 2020-07-20 01:28:11 +05:30
CHANGELOG.rst Point to stable docs instead of latest 2020-07-07 07:45:27 -03:00
CITATION Fix linting issues 2018-07-14 16:35:33 +01:00
CODE_OF_CONDUCT.md remove myself from the list of coc handlers (#6857) 2020-03-03 19:08:59 -03:00
CONTRIBUTING.rst Point to stable docs instead of latest 2020-07-07 07:45:27 -03:00
LICENSE Update copyright year to 2020 2020-01-04 08:46:58 -03:00
OPENCOLLECTIVE.rst doc: fix typos in OPENCOLLECTIVE.rst [ci skip] 2019-07-10 20:15:22 +02:00
README.rst Point to stable docs instead of latest 2020-07-07 07:45:27 -03:00
RELEASING.rst Support generating major releases using issue comments (#7548) 2020-07-28 13:40:14 +02:00
TIDELIFT.rst Add asottile as well 2020-05-08 08:57:22 -07:00
codecov.yml Adjust codecov: only patch statuses 2020-06-02 08:17:43 -03:00
pyproject.toml Add pyproject.toml support (#7247) 2020-06-08 10:03:10 -03:00
setup.cfg Publish our types 2020-07-04 13:18:15 +03:00
setup.py Run setup-py-upgrade and setup-cfg-fmt 2020-06-04 09:58:58 -07:00
tox.ini Set correct version during regen 2020-07-08 17:49:09 -04:00

README.rst

.. image:: https://docs.pytest.org/en/stable/_static/pytest1.png
   :target: https://docs.pytest.org/en/stable/
   :align: center
   :alt: pytest


------

.. image:: https://img.shields.io/pypi/v/pytest.svg
    :target: https://pypi.org/project/pytest/

.. image:: https://img.shields.io/conda/vn/conda-forge/pytest.svg
    :target: https://anaconda.org/conda-forge/pytest

.. image:: https://img.shields.io/pypi/pyversions/pytest.svg
    :target: https://pypi.org/project/pytest/

.. image:: https://codecov.io/gh/pytest-dev/pytest/branch/master/graph/badge.svg
    :target: https://codecov.io/gh/pytest-dev/pytest
    :alt: Code coverage Status

.. image:: https://travis-ci.org/pytest-dev/pytest.svg?branch=master
    :target: https://travis-ci.org/pytest-dev/pytest

.. image:: https://dev.azure.com/pytest-dev/pytest/_apis/build/status/pytest-CI?branchName=master
    :target: https://dev.azure.com/pytest-dev/pytest

.. image:: https://img.shields.io/badge/code%20style-black-000000.svg
    :target: https://github.com/psf/black

.. image:: https://www.codetriage.com/pytest-dev/pytest/badges/users.svg
    :target: https://www.codetriage.com/pytest-dev/pytest

.. image:: https://readthedocs.org/projects/pytest/badge/?version=latest
    :target: https://pytest.readthedocs.io/en/latest/?badge=latest
    :alt: Documentation Status

The ``pytest`` framework makes it easy to write small tests, yet
scales to support complex functional testing for applications and libraries.

An example of a simple test:

.. code-block:: python

    # content of test_sample.py
    def inc(x):
        return x + 1


    def test_answer():
        assert inc(3) == 5


To execute it::

    $ pytest
    ============================= test session starts =============================
    collected 1 items

    test_sample.py F

    ================================== FAILURES ===================================
    _________________________________ test_answer _________________________________

        def test_answer():
    >       assert inc(3) == 5
    E       assert 4 == 5
    E        +  where 4 = inc(3)

    test_sample.py:5: AssertionError
    ========================== 1 failed in 0.04 seconds ===========================


Due to ``pytest``'s detailed assertion introspection, only plain ``assert`` statements are used. See `getting-started <https://docs.pytest.org/en/stable/getting-started.html#our-first-test-run>`_ for more examples.


Features
--------

- Detailed info on failing `assert statements <https://docs.pytest.org/en/stable/assert.html>`_ (no need to remember ``self.assert*`` names);

- `Auto-discovery
  <https://docs.pytest.org/en/stable/goodpractices.html#python-test-discovery>`_
  of test modules and functions;

- `Modular fixtures <https://docs.pytest.org/en/stable/fixture.html>`_ for
  managing small or parametrized long-lived test resources;

- Can run `unittest <https://docs.pytest.org/en/stable/unittest.html>`_ (or trial),
  `nose <https://docs.pytest.org/en/stable/nose.html>`_ test suites out of the box;

- Python 3.5+ and PyPy3;

- Rich plugin architecture, with over 850+ `external plugins <http://plugincompat.herokuapp.com>`_ and thriving community;


Documentation
-------------

For full documentation, including installation, tutorials and PDF documents, please see https://docs.pytest.org/en/stable/.


Bugs/Requests
-------------

Please use the `GitHub issue tracker <https://github.com/pytest-dev/pytest/issues>`_ to submit bugs or request features.


Changelog
---------

Consult the `Changelog <https://docs.pytest.org/en/stable/changelog.html>`__ page for fixes and enhancements of each version.


Support pytest
--------------

`Open Collective`_ is an online funding platform for open and transparent communities.
It provides tools to raise money and share your finances in full transparency.

It is the platform of choice for individuals and companies that want to make one-time or
monthly donations directly to the project.

See more details in the `pytest collective`_.

.. _Open Collective: https://opencollective.com
.. _pytest collective: https://opencollective.com/pytest


pytest for enterprise
---------------------

Available as part of the Tidelift Subscription.

The maintainers of pytest and thousands of other packages are working with Tidelift to deliver commercial support and
maintenance for the open source dependencies you use to build your applications.
Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use.

`Learn more. <https://tidelift.com/subscription/pkg/pypi-pytest?utm_source=pypi-pytest&utm_medium=referral&utm_campaign=enterprise&utm_term=repo>`_

Security
^^^^^^^^

pytest has never been associated with a security vulnerability, but in any case, to report a
security vulnerability please use the `Tidelift security contact <https://tidelift.com/security>`_.
Tidelift will coordinate the fix and disclosure.


License
-------

Copyright Holger Krekel and others, 2004-2020.

Distributed under the terms of the `MIT`_ license, pytest is free and open source software.

.. _`MIT`: https://github.com/pytest-dev/pytest/blob/master/LICENSE