Go to file
Bruno Oliveira d4ca634ef6
Fix linting
2018-10-31 18:21:55 -03:00
.github Use full link to changelog's README in PR template 2018-10-15 12:19:52 -03:00
bench Apply reorder-python-imports to all files 2018-10-25 00:01:29 -07:00
changelog Fix linting 2018-10-31 18:21:55 -03:00
doc/en Fix linting2 2018-10-31 11:05:58 -03:00
extra Apply reorder-python-imports to all files 2018-10-25 00:01:29 -07:00
scripts Apply reorder-python-imports to all files 2018-10-25 00:01:29 -07:00
src Improve the warning message for the implicitly str conversion 2018-10-31 16:19:10 -03:00
testing Improve the warning message for the implicitly str conversion 2018-10-31 16:19:10 -03:00
.coveragerc coverage: use modules for source 2018-09-19 07:46:19 +02:00
.gitattributes Add codecov support to AppVeyor and remove coveralls 2018-09-05 19:50:06 -03:00
.gitignore Ignore Sphinx's .doctrees folder 2018-09-14 16:00:35 -03:00
.pre-commit-config.yaml Upgrade pre-commit hooks 2018-10-30 11:02:44 -07:00
.travis.yml Attempt to fix macosx build setup 2018-10-24 12:46:45 -03:00
AUTHORS Merge remote-tracking branch 'upstream/master' into merge-master-into-features 2018-10-15 12:55:28 -03:00
CHANGELOG.rst Spelling and grammar fixes 2018-10-29 23:45:45 +02:00
CITATION Fix linting issues 2018-07-14 16:35:33 +01:00
CONTRIBUTING.rst Fix linting 2018-10-15 08:15:40 -03:00
HOWTORELEASE.rst Update release procedure [ci skip] 2018-08-29 14:13:08 -07:00
LICENSE Update copyright date in LICENSE and README.rst 2017-06-13 14:58:07 +02:00
README.rst Replace coveralls' badge by codecov's 2018-09-05 22:37:32 -03:00
appveyor.yml AppVeyor: use fast_finish 2018-10-14 14:27:34 +02:00
pyproject.toml fix #4177 - pin setuptools>=40.0 2018-10-17 20:08:07 +02:00
setup.cfg fix url quotes in setup.cfg metadata 2018-10-16 21:48:39 +02:00
setup.py Apply reorder-python-imports to all files 2018-10-25 00:01:29 -07:00
tox.ini Add back some {posargs} placeholders for pytest invocations in tox.ini 2018-10-18 21:57:11 -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://ci.appveyor.com/api/projects/status/mrgbjaua7t33pg6b?svg=true
    :target: https://ci.appveyor.com/project/pytestbot/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-2018.

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