diff --git a/doc/en/assert.rst b/doc/en/assert.rst index bc06faed2..d83383da6 100644 --- a/doc/en/assert.rst +++ b/doc/en/assert.rst @@ -26,7 +26,7 @@ you will see the return value of the function call:: $ py.test test_assert1.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items @@ -143,7 +143,7 @@ if you run this module:: $ py.test test_assert2.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items diff --git a/doc/en/cache.rst b/doc/en/cache.rst index 9e025c741..33e4c700d 100644 --- a/doc/en/cache.rst +++ b/doc/en/cache.rst @@ -80,7 +80,7 @@ If you then run it with ``--lf``:: $ py.test --lf ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 run-last-failure: rerun last 2 failures rootdir: $REGENDOC_TMPDIR, inifile: collected 50 items @@ -121,7 +121,7 @@ of ``FF`` and dots):: $ py.test --ff ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 run-last-failure: rerun last 2 failures first rootdir: $REGENDOC_TMPDIR, inifile: collected 50 items @@ -226,7 +226,7 @@ You can always peek at the content of the cache using the $ py.test --cache-clear ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items diff --git a/doc/en/capture.rst b/doc/en/capture.rst index 457568b82..8e696a8d7 100644 --- a/doc/en/capture.rst +++ b/doc/en/capture.rst @@ -64,7 +64,7 @@ of the failing function and hide the other one:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 2 items diff --git a/doc/en/doctest.rst b/doc/en/doctest.rst index e7e15bd64..f13752e66 100644 --- a/doc/en/doctest.rst +++ b/doc/en/doctest.rst @@ -49,7 +49,7 @@ then you can just invoke ``py.test`` without command line options:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: pytest.ini collected 1 items diff --git a/doc/en/example/markers.rst b/doc/en/example/markers.rst index aaa459387..85a57b9b8 100644 --- a/doc/en/example/markers.rst +++ b/doc/en/example/markers.rst @@ -31,7 +31,7 @@ You can then restrict a test run to only run tests marked with ``webtest``:: $ py.test -v -m webtest ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 4 items @@ -45,7 +45,7 @@ Or the inverse, running all tests except the webtest ones:: $ py.test -v -m "not webtest" ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 4 items @@ -66,7 +66,7 @@ tests based on their module, class, method, or function name:: $ py.test -v test_server.py::TestClass::test_method ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 5 items @@ -79,7 +79,7 @@ You can also select on the class:: $ py.test -v test_server.py::TestClass ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 4 items @@ -92,7 +92,7 @@ Or select multiple nodes:: $ py.test -v test_server.py::TestClass test_server.py::test_send_http ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 8 items @@ -130,7 +130,7 @@ select tests based on their names:: $ py.test -v -k http # running with the above defined example module ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 4 items @@ -144,7 +144,7 @@ And you can also run all tests except the ones that match the keyword:: $ py.test -k "not send_http" -v ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 4 items @@ -160,7 +160,7 @@ Or to select "http" and "quick" tests:: $ py.test -k "http or quick" -v ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 4 items @@ -350,7 +350,7 @@ the test needs:: $ py.test -E stage2 ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items @@ -362,7 +362,7 @@ and here is one that specifies exactly the environment needed:: $ py.test -E stage1 ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items @@ -481,7 +481,7 @@ then you will see two test skipped and two executed tests as expected:: $ py.test -rs # this option reports skip reasons ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 4 items @@ -495,7 +495,7 @@ Note that if you specify a platform via the marker-command line option like this $ py.test -m linux2 ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 4 items @@ -547,7 +547,7 @@ We can now use the ``-m option`` to select one set:: $ py.test -m interface --tb=short ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 4 items @@ -569,7 +569,7 @@ or to select both "event" and "interface" tests:: $ py.test -m "interface or event" --tb=short ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 4 items diff --git a/doc/en/example/nonpython.rst b/doc/en/example/nonpython.rst index 756e25255..01eca5ec7 100644 --- a/doc/en/example/nonpython.rst +++ b/doc/en/example/nonpython.rst @@ -27,7 +27,7 @@ now execute the test specification:: nonpython $ py.test test_simple.yml ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR/nonpython, inifile: collected 2 items @@ -59,7 +59,7 @@ consulted when reporting in ``verbose`` mode:: nonpython $ py.test -v ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR/nonpython, inifile: collecting ... collected 2 items @@ -81,7 +81,7 @@ interesting to just look at the collection tree:: nonpython $ py.test --collect-only ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR/nonpython, inifile: collected 2 items diff --git a/doc/en/example/parametrize.rst b/doc/en/example/parametrize.rst index 4423ea257..12062e650 100644 --- a/doc/en/example/parametrize.rst +++ b/doc/en/example/parametrize.rst @@ -130,7 +130,7 @@ objects, they are still using the default pytest representation:: $ py.test test_time.py --collect-only ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 6 items @@ -181,7 +181,7 @@ this is a fully self-contained example which you can run with:: $ py.test test_scenarios.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 4 items @@ -194,7 +194,7 @@ If you just collect tests you'll also nicely see 'advanced' and 'basic' as varia $ py.test --collect-only test_scenarios.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 4 items @@ -259,7 +259,7 @@ Let's first see how it looks like at collection time:: $ py.test test_backends.py --collect-only ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 2 items @@ -320,7 +320,7 @@ The result of this test will be successful:: $ py.test test_indirect_list.py --collect-only ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items @@ -397,8 +397,11 @@ is to be run with different sets of arguments for its three arguments: Running it results in some skips if we don't have all the python interpreters installed and otherwise runs all combinations (5 interpreters times 5 interpreters times 3 objects to serialize/deserialize):: . $ py.test -rs -q multipython.py - ........................... - 27 passed in 0.12 seconds + ssssssssssss...ssssssssssss + ======= short test summary info ======== + SKIP [12] $REGENDOC_TMPDIR/CWD/multipython.py:23: 'python2.6' not found + SKIP [12] $REGENDOC_TMPDIR/CWD/multipython.py:23: 'python3.3' not found + 3 passed, 24 skipped in 0.12 seconds Indirect parametrization of optional implementations/imports -------------------------------------------------------------------- @@ -445,7 +448,7 @@ If you run this with reporting for skips enabled:: $ py.test -rs test_module.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 2 items diff --git a/doc/en/example/pythoncollection.rst b/doc/en/example/pythoncollection.rst index f8af169f9..6305aae31 100644 --- a/doc/en/example/pythoncollection.rst +++ b/doc/en/example/pythoncollection.rst @@ -82,7 +82,7 @@ then the test collection looks like this:: $ py.test --collect-only ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: setup.cfg collected 2 items @@ -128,7 +128,7 @@ You can always peek at the collection tree without running tests like this:: . $ py.test --collect-only pythoncollection.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: pytest.ini collected 3 items @@ -182,7 +182,7 @@ interpreters and will leave out the setup.py file:: $ py.test --collect-only ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: pytest.ini collected 0 items diff --git a/doc/en/example/reportingdemo.rst b/doc/en/example/reportingdemo.rst index 6e79b3072..db35c2a73 100644 --- a/doc/en/example/reportingdemo.rst +++ b/doc/en/example/reportingdemo.rst @@ -13,7 +13,7 @@ get on the terminal - we are working on that): assertion $ py.test failure_demo.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR/assertion, inifile: collected 42 items @@ -28,7 +28,7 @@ get on the terminal - we are working on that): > assert param1 * 2 < param2 E assert (3 * 2) < 6 - failure_demo.py:15: AssertionError + failure_demo.py:16: AssertionError _______ TestFailing.test_simple ________ self = @@ -44,7 +44,7 @@ get on the terminal - we are working on that): E + where 42 = .f at 0xdeadbeef>() E + and 43 = .g at 0xdeadbeef>() - failure_demo.py:28: AssertionError + failure_demo.py:29: AssertionError _______ TestFailing.test_simple_multiline ________ self = @@ -54,7 +54,7 @@ get on the terminal - we are working on that): 42, > 6*9) - failure_demo.py:33: + failure_demo.py:34: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ a = 42, b = 54 @@ -64,7 +64,7 @@ get on the terminal - we are working on that): b) E assert 42 == 54 - failure_demo.py:11: AssertionError + failure_demo.py:12: AssertionError _______ TestFailing.test_not ________ self = @@ -76,7 +76,7 @@ get on the terminal - we are working on that): E assert not 42 E + where 42 = .f at 0xdeadbeef>() - failure_demo.py:38: AssertionError + failure_demo.py:39: AssertionError _______ TestSpecialisedExplanations.test_eq_text ________ self = @@ -87,7 +87,7 @@ get on the terminal - we are working on that): E - spam E + eggs - failure_demo.py:42: AssertionError + failure_demo.py:43: AssertionError _______ TestSpecialisedExplanations.test_eq_similar_text ________ self = @@ -100,7 +100,7 @@ get on the terminal - we are working on that): E + foo 2 bar E ? ^ - failure_demo.py:45: AssertionError + failure_demo.py:46: AssertionError _______ TestSpecialisedExplanations.test_eq_multiline_text ________ self = @@ -113,7 +113,7 @@ get on the terminal - we are working on that): E + eggs E bar - failure_demo.py:48: AssertionError + failure_demo.py:49: AssertionError _______ TestSpecialisedExplanations.test_eq_long_text ________ self = @@ -130,7 +130,7 @@ get on the terminal - we are working on that): E + 1111111111b222222222 E ? ^ - failure_demo.py:53: AssertionError + failure_demo.py:54: AssertionError _______ TestSpecialisedExplanations.test_eq_long_text_multiline ________ self = @@ -154,7 +154,7 @@ get on the terminal - we are working on that): E 2 E 2 - failure_demo.py:58: AssertionError + failure_demo.py:59: AssertionError _______ TestSpecialisedExplanations.test_eq_list ________ self = @@ -165,7 +165,7 @@ get on the terminal - we are working on that): E At index 2 diff: 2 != 3 E Use -v to get the full diff - failure_demo.py:61: AssertionError + failure_demo.py:62: AssertionError _______ TestSpecialisedExplanations.test_eq_list_long ________ self = @@ -178,7 +178,7 @@ get on the terminal - we are working on that): E At index 100 diff: 1 != 2 E Use -v to get the full diff - failure_demo.py:66: AssertionError + failure_demo.py:67: AssertionError _______ TestSpecialisedExplanations.test_eq_dict ________ self = @@ -195,7 +195,7 @@ get on the terminal - we are working on that): E {'d': 0} E Use -v to get the full diff - failure_demo.py:69: AssertionError + failure_demo.py:70: AssertionError _______ TestSpecialisedExplanations.test_eq_set ________ self = @@ -212,7 +212,7 @@ get on the terminal - we are working on that): E 21 E Use -v to get the full diff - failure_demo.py:72: AssertionError + failure_demo.py:73: AssertionError _______ TestSpecialisedExplanations.test_eq_longer_list ________ self = @@ -223,7 +223,7 @@ get on the terminal - we are working on that): E Right contains more items, first extra item: 3 E Use -v to get the full diff - failure_demo.py:75: AssertionError + failure_demo.py:76: AssertionError _______ TestSpecialisedExplanations.test_in_list ________ self = @@ -232,7 +232,7 @@ get on the terminal - we are working on that): > assert 1 in [0, 2, 3, 4, 5] E assert 1 in [0, 2, 3, 4, 5] - failure_demo.py:78: AssertionError + failure_demo.py:79: AssertionError _______ TestSpecialisedExplanations.test_not_in_text_multiline ________ self = @@ -250,7 +250,7 @@ get on the terminal - we are working on that): E and a E tail - failure_demo.py:82: AssertionError + failure_demo.py:83: AssertionError _______ TestSpecialisedExplanations.test_not_in_text_single ________ self = @@ -263,7 +263,7 @@ get on the terminal - we are working on that): E single foo line E ? +++ - failure_demo.py:86: AssertionError + failure_demo.py:87: AssertionError _______ TestSpecialisedExplanations.test_not_in_text_single_long ________ self = @@ -276,7 +276,7 @@ get on the terminal - we are working on that): E head head foo tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail E ? +++ - failure_demo.py:90: AssertionError + failure_demo.py:91: AssertionError ______ TestSpecialisedExplanations.test_not_in_text_single_long_term _______ self = @@ -289,7 +289,7 @@ get on the terminal - we are working on that): E head head fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffftail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail tail E ? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ - failure_demo.py:94: AssertionError + failure_demo.py:95: AssertionError _______ test_attribute ________ def test_attribute(): @@ -300,7 +300,7 @@ get on the terminal - we are working on that): E assert 1 == 2 E + where 1 = .Foo object at 0xdeadbeef>.b - failure_demo.py:101: AssertionError + failure_demo.py:102: AssertionError _______ test_attribute_instance ________ def test_attribute_instance(): @@ -311,7 +311,7 @@ get on the terminal - we are working on that): E + where 1 = .Foo object at 0xdeadbeef>.b E + where .Foo object at 0xdeadbeef> = .Foo'>() - failure_demo.py:107: AssertionError + failure_demo.py:108: AssertionError _______ test_attribute_failure ________ def test_attribute_failure(): @@ -322,7 +322,7 @@ get on the terminal - we are working on that): i = Foo() > assert i.b == 2 - failure_demo.py:116: + failure_demo.py:117: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = .Foo object at 0xdeadbeef> @@ -331,7 +331,7 @@ get on the terminal - we are working on that): > raise Exception('Failed to get attrib') E Exception: Failed to get attrib - failure_demo.py:113: Exception + failure_demo.py:114: Exception _______ test_attribute_multiple ________ def test_attribute_multiple(): @@ -346,7 +346,7 @@ get on the terminal - we are working on that): E + and 2 = .Bar object at 0xdeadbeef>.b E + where .Bar object at 0xdeadbeef> = .Bar'>() - failure_demo.py:124: AssertionError + failure_demo.py:125: AssertionError _______ TestRaises.test_raises ________ self = @@ -355,22 +355,22 @@ get on the terminal - we are working on that): s = 'qwe' > raises(TypeError, "int(s)") - failure_demo.py:133: + failure_demo.py:134: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > int(s) E ValueError: invalid literal for int() with base 10: 'qwe' - <0-codegen $PYTHON_PREFIX/lib/python3.4/site-packages/_pytest/python.py:1300>:1: ValueError + <0-codegen $PYTHON_PREFIX/lib/python3.4/site-packages/_pytest/python.py:1302>:1: ValueError _______ TestRaises.test_raises_doesnt ________ self = def test_raises_doesnt(self): > raises(IOError, "int('3')") - E Failed: DID NOT RAISE + E Failed: DID NOT RAISE - failure_demo.py:136: Failed + failure_demo.py:137: Failed _______ TestRaises.test_raise ________ self = @@ -379,7 +379,7 @@ get on the terminal - we are working on that): > raise ValueError("demo error") E ValueError: demo error - failure_demo.py:139: ValueError + failure_demo.py:140: ValueError _______ TestRaises.test_tupleerror ________ self = @@ -388,7 +388,7 @@ get on the terminal - we are working on that): > a,b = [1] E ValueError: need more than 1 value to unpack - failure_demo.py:142: ValueError + failure_demo.py:143: ValueError ______ TestRaises.test_reinterpret_fails_with_print_for_the_fun_of_it ______ self = @@ -399,7 +399,7 @@ get on the terminal - we are working on that): > a,b = l.pop() E TypeError: 'int' object is not iterable - failure_demo.py:147: TypeError + failure_demo.py:148: TypeError --------------------------- Captured stdout call --------------------------- l is [1, 2, 3] _______ TestRaises.test_some_error ________ @@ -410,26 +410,26 @@ get on the terminal - we are working on that): > if namenotexi: E NameError: name 'namenotexi' is not defined - failure_demo.py:150: NameError + failure_demo.py:151: NameError _______ test_dynamic_compile_shows_nicely ________ def test_dynamic_compile_shows_nicely(): src = 'def foo():\n assert 1 == 0\n' name = 'abc-123' module = py.std.imp.new_module(name) - code = py.code.compile(src, name, 'exec') + code = _pytest._code.compile(src, name, 'exec') py.builtin.exec_(code, module.__dict__) py.std.sys.modules[name] = module > module.foo() - failure_demo.py:165: + failure_demo.py:166: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ def foo(): > assert 1 == 0 E assert 1 == 0 - <2-codegen 'abc-123' $REGENDOC_TMPDIR/assertion/failure_demo.py:162>:2: AssertionError + <2-codegen 'abc-123' $REGENDOC_TMPDIR/assertion/failure_demo.py:163>:2: AssertionError _______ TestMoreErrors.test_complex_error ________ self = @@ -441,9 +441,9 @@ get on the terminal - we are working on that): return 43 > somefunc(f(), g()) - failure_demo.py:175: + failure_demo.py:176: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ - failure_demo.py:8: in somefunc + failure_demo.py:9: in somefunc otherfunc(x,y) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ @@ -453,7 +453,7 @@ get on the terminal - we are working on that): > assert a==b E assert 44 == 43 - failure_demo.py:5: AssertionError + failure_demo.py:6: AssertionError _______ TestMoreErrors.test_z1_unpack_error ________ self = @@ -463,7 +463,7 @@ get on the terminal - we are working on that): > a,b = l E ValueError: need more than 0 values to unpack - failure_demo.py:179: ValueError + failure_demo.py:180: ValueError _______ TestMoreErrors.test_z2_type_error ________ self = @@ -473,7 +473,7 @@ get on the terminal - we are working on that): > a,b = l E TypeError: 'int' object is not iterable - failure_demo.py:183: TypeError + failure_demo.py:184: TypeError _______ TestMoreErrors.test_startswith ________ self = @@ -485,7 +485,7 @@ get on the terminal - we are working on that): E assert ('456') E + where = '123'.startswith - failure_demo.py:188: AssertionError + failure_demo.py:189: AssertionError _______ TestMoreErrors.test_startswith_nested ________ self = @@ -501,7 +501,7 @@ get on the terminal - we are working on that): E + where '123' = .f at 0xdeadbeef>() E + and '456' = .g at 0xdeadbeef>() - failure_demo.py:195: AssertionError + failure_demo.py:196: AssertionError _______ TestMoreErrors.test_global_func ________ self = @@ -511,7 +511,7 @@ get on the terminal - we are working on that): E assert isinstance(43, float) E + where 43 = globf(42) - failure_demo.py:198: AssertionError + failure_demo.py:199: AssertionError _______ TestMoreErrors.test_instance ________ self = @@ -522,7 +522,7 @@ get on the terminal - we are working on that): E assert 42 != 42 E + where 42 = .x - failure_demo.py:202: AssertionError + failure_demo.py:203: AssertionError _______ TestMoreErrors.test_compare ________ self = @@ -532,7 +532,7 @@ get on the terminal - we are working on that): E assert 11 < 5 E + where 11 = globf(10) - failure_demo.py:205: AssertionError + failure_demo.py:206: AssertionError _______ TestMoreErrors.test_try_finally ________ self = @@ -543,7 +543,7 @@ get on the terminal - we are working on that): > assert x == 0 E assert 1 == 0 - failure_demo.py:210: AssertionError + failure_demo.py:211: AssertionError _______ TestCustomAssertMsg.test_single_line ________ self = @@ -557,7 +557,7 @@ get on the terminal - we are working on that): E assert 1 == 2 E + where 1 = .A'>.a - failure_demo.py:221: AssertionError + failure_demo.py:222: AssertionError _______ TestCustomAssertMsg.test_multiline ________ self = @@ -574,7 +574,7 @@ get on the terminal - we are working on that): E assert 1 == 2 E + where 1 = .A'>.a - failure_demo.py:227: AssertionError + failure_demo.py:228: AssertionError _______ TestCustomAssertMsg.test_custom_repr ________ self = @@ -594,5 +594,5 @@ get on the terminal - we are working on that): E assert 1 == 2 E + where 1 = This is JSON\n{\n 'foo': 'bar'\n}.a - failure_demo.py:237: AssertionError + failure_demo.py:238: AssertionError ======= 42 failed in 0.12 seconds ======== diff --git a/doc/en/example/simple.rst b/doc/en/example/simple.rst index a5643fffc..8bddb1348 100644 --- a/doc/en/example/simple.rst +++ b/doc/en/example/simple.rst @@ -108,7 +108,7 @@ directory with the above conftest.py:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 0 items @@ -156,7 +156,7 @@ and when running it will see a skipped "slow" test:: $ py.test -rs # "-rs" means report details on the little 's' ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 2 items @@ -170,7 +170,7 @@ Or run it including the ``slow`` marked test:: $ py.test --runslow ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 2 items @@ -262,7 +262,7 @@ which will add the string to the test header accordingly:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 project deps: mylib-1.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 0 items @@ -286,7 +286,7 @@ which will add info only when run with "--v":: $ py.test -v ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache info1: did you know that ... did you? @@ -299,7 +299,7 @@ and nothing when run plainly:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 0 items @@ -332,7 +332,7 @@ Now we can profile which test functions execute the slowest:: $ py.test --durations=3 ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 3 items @@ -341,7 +341,7 @@ Now we can profile which test functions execute the slowest:: ======= slowest 3 test durations ======== 0.20s call test_some_are_slow.py::test_funcslow2 0.10s call test_some_are_slow.py::test_funcslow1 - 0.00s setup test_some_are_slow.py::test_funcslow2 + 0.00s setup test_some_are_slow.py::test_funcfast ======= 3 passed in 0.12 seconds ======== incremental testing - test steps @@ -394,7 +394,7 @@ If we run this:: $ py.test -rx ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 4 items @@ -465,7 +465,7 @@ We can run this:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 7 items @@ -479,7 +479,7 @@ We can run this:: file $REGENDOC_TMPDIR/b/test_error.py, line 1 def test_root(db): # no db here, will error out fixture 'db' not found - available fixtures: record_xml_property, pytestconfig, cache, capsys, recwarn, monkeypatch, tmpdir, capfd, tmpdir_factory + available fixtures: cache, tmpdir_factory, capsys, pytestconfig, capfd, record_xml_property, recwarn, tmpdir, monkeypatch use 'py.test --fixtures [testpath]' for help on them. $REGENDOC_TMPDIR/b/test_error.py:1 @@ -569,7 +569,7 @@ and run them:: $ py.test test_module.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 2 items @@ -660,7 +660,7 @@ and run it:: $ py.test -s test_module.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 3 items diff --git a/doc/en/fixture.rst b/doc/en/fixture.rst index 398e091d8..6f7794eb8 100644 --- a/doc/en/fixture.rst +++ b/doc/en/fixture.rst @@ -75,7 +75,7 @@ marked ``smtp`` fixture function. Running the test looks like this:: $ py.test test_smtpsimple.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items @@ -193,7 +193,7 @@ inspect what is going on and can now run the tests:: $ py.test test_module.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 2 items @@ -480,7 +480,7 @@ Running the above tests results in the following test IDs being used:: $ py.test --collect-only ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 10 items @@ -531,7 +531,7 @@ Here we declare an ``app`` fixture which receives the previously defined $ py.test -v test_appsetup.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 2 items @@ -597,7 +597,7 @@ Let's run the tests in verbose mode and with looking at the print-output:: $ py.test -v -s test_module.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- $PYTHON_PREFIX/bin/python3.4 cachedir: .cache rootdir: $REGENDOC_TMPDIR, inifile: collecting ... collected 8 items diff --git a/doc/en/getting-started.rst b/doc/en/getting-started.rst index d15beb994..6ab8638b9 100644 --- a/doc/en/getting-started.rst +++ b/doc/en/getting-started.rst @@ -27,7 +27,7 @@ Installation options:: To check your installation has installed the correct version:: $ py.test --version - This is pytest version 2.8.7, imported from $PYTHON_PREFIX/lib/python3.4/site-packages/pytest.py + This is pytest version 2.9.0, imported from $PYTHON_PREFIX/lib/python3.4/site-packages/pytest.py If you get an error checkout :ref:`installation issues`. @@ -49,7 +49,7 @@ That's it. You can execute the test function now:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items diff --git a/doc/en/parametrize.rst b/doc/en/parametrize.rst index 468a739d2..66449fbdd 100644 --- a/doc/en/parametrize.rst +++ b/doc/en/parametrize.rst @@ -55,7 +55,7 @@ them in turn:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 3 items @@ -103,7 +103,7 @@ Let's run this:: $ py.test ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 3 items @@ -201,7 +201,7 @@ list:: $ py.test -q -rs test_strings.py s ======= short test summary info ======== - SKIP [1] $PYTHON_PREFIX/lib/python3.4/site-packages/_pytest/python.py:1417: got empty parameter set, function test_valid_string at $REGENDOC_TMPDIR/test_strings.py:1 + SKIP [1] $PYTHON_PREFIX/lib/python3.4/site-packages/_pytest/python.py:1419: got empty parameter set, function test_valid_string at $REGENDOC_TMPDIR/test_strings.py:1 1 skipped in 0.12 seconds For further examples, you might want to look at :ref:`more diff --git a/doc/en/skipping.rst b/doc/en/skipping.rst index 62c46dea1..cd8f5d8a4 100644 --- a/doc/en/skipping.rst +++ b/doc/en/skipping.rst @@ -224,15 +224,15 @@ Running it with the report-on-xfail option gives this output:: example $ py.test -rx xfail_demo.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR/example, inifile: collected 7 items - + xfail_demo.py xxxxxxx ======= short test summary info ======== XFAIL xfail_demo.py::test_hello XFAIL xfail_demo.py::test_hello2 - reason: [NOTRUN] + reason: [NOTRUN] XFAIL xfail_demo.py::test_hello3 condition: hasattr(os, 'sep') XFAIL xfail_demo.py::test_hello4 @@ -242,10 +242,9 @@ Running it with the report-on-xfail option gives this output:: XFAIL xfail_demo.py::test_hello6 reason: reason XFAIL xfail_demo.py::test_hello7 - + ======= 7 xfailed in 0.12 seconds ======== - xfail signature summary ~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/en/tmpdir.rst b/doc/en/tmpdir.rst index 1da211384..21497d8ea 100644 --- a/doc/en/tmpdir.rst +++ b/doc/en/tmpdir.rst @@ -29,7 +29,7 @@ Running this would result in a passed test except for the last $ py.test test_tmpdir.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 1 items diff --git a/doc/en/unittest.rst b/doc/en/unittest.rst index 7d9ef909b..f1ef1b2d9 100644 --- a/doc/en/unittest.rst +++ b/doc/en/unittest.rst @@ -88,7 +88,7 @@ the ``self.db`` values in the traceback:: $ py.test test_unittest_db.py ======= test session starts ======== - platform linux -- Python 3.4.3, pytest-2.8.7, py-1.4.31, pluggy-0.3.1 + platform linux -- Python 3.4.0, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 rootdir: $REGENDOC_TMPDIR, inifile: collected 2 items