Go to file
Bruno Oliveira f1183c2422 Remove the 'issue' marker from test suite
It doesn't seem to add much value (why would one execute tests
based on that marker?), plus using the docstring for that
encourages one to write a more descriptive message about the test
2019-05-09 19:36:38 -03:00
.github GitHub: revisit issue/PR templates [ci skip] 2019-04-23 18:01:13 +02:00
bench pre-commit autoupdate 2019-04-12 04:52:47 -07:00
changelog Change ``--strict`` to ``--strict-markers``, preserving the old one 2019-05-09 19:36:38 -03:00
doc/en Change ``--strict`` to ``--strict-markers``, preserving the old one 2019-05-09 19:36:38 -03:00
extra Fix formatting of print() calls 2018-11-22 00:15:14 -08:00
scripts ci: Azure: fix coverage generation with PyPy 2019-03-04 17:46:01 +01:00
src Change ``--strict`` to ``--strict-markers``, preserving the old one 2019-05-09 19:36:38 -03:00
testing Remove the 'issue' marker from test suite 2019-05-09 19:36:38 -03:00
.coveragerc .coveragerc: use "src" only from current dir 2019-03-22 17:48:14 +01:00
.gitattributes Add codecov support to AppVeyor and remove coveralls 2018-09-05 19:50:06 -03:00
.gitignore Ignore pip-generated 'pip-wheel-metadata' folder [skip ci] 2019-02-08 21:06:33 -02:00
.pre-commit-config.yaml pre-commit autoupdate 2019-04-12 04:52:47 -07:00
.travis.yml Merge master into features 2019-03-26 10:23:21 +01:00
AUTHORS logging: improve default logging format (issue5214) 2019-05-08 21:37:59 +03:00
CHANGELOG.rst Preparing release version 4.4.1 2019-04-15 14:24:17 +00:00
CITATION Fix linting issues 2018-07-14 16:35:33 +01:00
CONTRIBUTING.rst CI: use py37 instead of py36 by default 2018-11-12 03:16:52 +01:00
HOWTORELEASE.rst doc: fix HOWTORELEASE.rst 2018-11-03 21:26:08 +01:00
LICENSE Update copyright year 2019-01-04 10:37:07 -02:00
README.rst Remove appveyor.yml and related scripts 2019-02-26 19:03:53 -03:00
azure-pipelines.yml Use 'pypy' as executable on PyPy env [skip travis] 2019-05-04 10:27:06 -03:00
pyproject.toml Use isolated_build option in tox.ini 2019-02-08 15:50:33 -02:00
setup.cfg Fix usages of py.io.saferepr 2019-01-20 16:36:23 -08:00
setup.py use wcwidth 2019-04-05 17:43:11 +02:00
tox.ini Remove the 'issue' marker from test suite 2019-05-09 19:36:38 -03:00

README.rst

.. image:: https://docs.pytest.org/en/latest/_static/pytest1.png
   :target: https://docs.pytest.org/en/latest/
   :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/ambv/black

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

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/latest/getting-started.html#our-first-test-run>`_ for more examples.


Features
--------

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

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

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

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

- Python 2.7, Python 3.4+, PyPy 2.3, Jython 2.5 (untested);

- Rich plugin architecture, with over 315+ `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/latest/.


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/latest/changelog.html>`__ page for fixes and enhancements of each version.


License
-------

Copyright Holger Krekel and others, 2004-2019.

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