Mailman 3 November 2012 - pytest-dev

[py-dev] steps to include a new plugin
by Adam Goucher Dec. 3, 2012

Dec. 3, 2012

If I wanted to try and add https://github.com/adamgoucher/pytest-marks to the main pytest distribution. Is there a process for consideration, code style rules, etc.? The idea of this plugin is to allow script creators to not have to do @pytest.mark.red @pytest.mark.green @pytest.mark.blue @pytest.mark.black @pytest.mark.orange @pytest.mark.pink def some_test_method(self): # some check-y stuff but rather @pytest.marks('red', 'green', 'blue', 'black', 'orange', 'pink') def some_test_method(self): # some check-y stuff -adam

4 5

[py-dev] pytest-2.3.4: bugfixes and extended selection with "-k expr"
by holger krekel Nov. 20, 2012

Nov. 20, 2012

pytest-2.3.4: stabilization, more flexible selection via "-k expr" =========================================================================== pytest-2.3.4 is a small stabilization release of the py.test tool which offers uebersimple assertions, scalable fixture mechanisms and deep customization for testing with Python. This release comes with the following fixes and features: - make "-k" option accept an expressions the same as with "-m" so that one can write: -k "name1 or name2" etc. This is a slight usage incompatibility if you used special syntax like "TestClass.test_method" which you now need to write as -k "TestClass and test_method" to match a certain method in a certain test class. - allow to dynamically define markers via item.keywords[...]=assignment integrating with "-m" option - yielded test functions will now have autouse-fixtures active but cannot accept fixtures as funcargs - it's anyway recommended to rather use the post-2.0 parametrize features instead of yield, see: http://pytest.org/latest/example/parametrize.html - fix autouse-issue where autouse-fixtures would not be discovered if defined in a a/conftest.py file and tests in a/tests/test_some.py - fix issue226 - LIFO ordering for fixture teardowns - fix issue224 - invocations with >256 char arguments now work - fix issue91 - add/discuss package/directory level setups in example - fixes related to autouse discovery and calling Thanks in particular to Thomas Waldmann for spotting and reporting issues. See http://pytest.org/ for general information. To install or upgrade pytest: pip install -U pytest # or easy_install -U pytest best, holger krekel

1 0

[py-dev] using tmpdir/monkeypatch/... from non-function scopes
by holger krekel Nov. 20, 2012

Nov. 20, 2012

Hi folks, while writing tests on a new project using pytest-2.3 i noticed again an inconvience: fixtures such as tmpdir or monkeypatch could implementation-wise easily support being called from non-function scoped fixtures. But currently if you do:: @pytest.fixture(scope="module") def something(monkeypatch): ... you get a ScopeMismatchError because the function-scoped monkeypatch fixture cannot be called from a module-scoped fixture. I am considering introducing an "any" scope for a fixture declaration that would avoid this error. The "monkeypatch" and "something" fixture would then look like this:: @pytest.fixture(scope="any") def monkeypatch(...): # unmodified builtin monkeypatch implementation @pytest.fixture(scope="module") def something(monkeypatch): ... This would not raise a ScopeMismatchError but just work: monkeypatch-finalizers would be called when the last test in a module using the "something" fixture has run. However, if we additionally have a function-scoped fixture:: @pytest.fixture(scope="function") def other(monkeypatch): ... The "monkeypatch" instance could obviously not be the same object as the one in ``something(monkeypatch)`` above. monkeypatch-finalizers would raher be called after a test function using the "other" fixture has finalized. I am not sure if there is confusion potential about this. If there are any questions or comments, please shoot. best, holger

2 6

[py-dev] Contributing to py
by Philipp Konrad Nov. 19, 2012

Nov. 19, 2012

Hello, my name is Philipp Konrad, I am a computer science student, a young Python programmer and researcher from Vienna, Austria. My developer experience started around two years ago in Java, but half year ago I was introduced to the Python world. I want to contribute to the py or py.test project and can assign one working day per week. Generally, I never have contributed to an open source project, so I would need some help for my first steps. - 1. Where is a good point to start? Is there a good site with first steps, a manual or something similiar? - 2. Do you have special coding / testing guidelines/ 'code of conduct' additional to PEP8? - 3. In which domain do you need new people? - 3.1 Code new features - 3.2 Documentation - 3.3 Write unit and integration tests - 3.4 Translation - 3.5 Community work - 4. Is there an organizational structure or hierachy that I should bear in mind? Take care, Philipp

2 3

[py-dev] [hpk42/pytest] finalizer function does not get called (issue #225)
by Thomas Waldmann Nov. 14, 2012

Nov. 14, 2012

--- you can reply above this line --- New issue 225: finalizer function does not get called https://bitbucket.org/hpk42/pytest/issue/225/finalizer-function-does-not-ge… Thomas Waldmann: py.test 2.3.3 release from pypi :::python import pytest @pytest.fixture(scope="function") def fix(request): print "fix init" def fin(): print "fix finalize" request.addfinalizer(fin) return 42 def test_xxx(fix): print fix assert False Captured stdout: ------------------------------------------------------ fix init 42 ========== 1 failed in 0.03 seconds ============== -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] a really large argument string will throw py.error.ENAMETOOLONG (issue #224)
by Anonymous Nov. 11, 2012

Nov. 11, 2012

--- you can reply above this line --- New issue 224: a really large argument string will throw py.error.ENAMETOOLONG https://bitbucket.org/hpk42/pytest/issue/224/a-really-large-argument-string… Anonymous: If you call py.test with something nefarious like this, config.py/getcfg() throws py.error.ENAMETOOLONG because it tries to make a file path from each command argument. py.test -m "flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py or flyingmonkey1.py" scripts/ I'm not sure if 'right' solution is to just not do this, or to catch this particular exception. try: if p.check(): # the rest of things except py.error.ENAMETOOLONG: continue -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] pytest fails collecting on py25 with "import file mismatch" - HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules (issue #223)
by Sorin Sbarnea Nov. 9, 2012

Nov. 9, 2012

--- you can reply above this line --- New issue 223: pytest fails collecting on py25 with "import file mismatch" - HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules https://bitbucket.org/hpk42/pytest/issue/223/pytest-fails-collecting-on-py2… Sorin Sbarnea: I use tox + pytest to test my python module but pytest fails to run on python2.5 giving something like: ``` #!python import file mismatch: imported module 'tendo.ansiterm' has this __file__ attribute: /Users/sorins/dev/py/tendo/.tox/py25/lib/python2.5/site-packages/tendo/ansiterm.py which is not the same as the test file we want to collect: /Users/sorins/dev/py/tendo/tendo/ansiterm.py HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules ``` Please take a look at https://github.com/pycontribs/tendo I am running the tests with the `test` shell script from the repository root. Everything goes well for python 2.6 and 2.7 but for 2.5 pytest complains about this. I know that others had similar problems when they included the tests in the libraries but this should be possible, especially for small modules. -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] mark expressions break for items that dont have a obj property (issue #222)
by Ronny Pfannschmidt Nov. 9, 2012

Nov. 9, 2012

--- you can reply above this line --- New issue 222: mark expressions break for items that dont have a obj property https://bitbucket.org/hpk42/pytest/issue/222/mark-expressions-break-for-ite… Ronny Pfannschmidt: https://bitbucket.org/RonnyPfannschmidt/pytest-codecheckers/issue/2/attribu… -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] PEP 420 namespace packages (issue #221)
by Anonymous Nov. 8, 2012

Nov. 8, 2012

--- you can reply above this line --- New issue 221: PEP 420 namespace packages https://bitbucket.org/hpk42/pytest/issue/221/pep-420-namespace-packages Anonymous: It seems that pytest (I'm using 2.3.3) doesn't support PEP 420 style namespace packages. I'm trying to run the tests from XIST 4.4 and get the following results: ``` #!bash $ hg clone https://bitbucket.org/doerwalter/livinglogic.python.xist $ cd livinglogic.python.xist/ $ pip install . $ python -mpytest test/test_misc.py ========================================================================================================================= test session starts ========================================================================================================================= platform darwin -- Python 3.3.0 -- pytest-2.3.3 collected 19 items test/test_misc.py ................... ====================================================================================================================== 19 passed in 0.52 seconds ====================================================================================================================== ``` However if I remove the namespace package __init__.py file: ``` #!bash rm ~/pyvenvs/default/lib/python3.3/site-packages/ll_xist-4.4-py3.3-macosx-10.7-x86_64.egg/ll/__init__.py ``` The output of the test run looks like this: ``` #!bash $ python -mpytest test/test_misc.py ========================================================================================================================= test session starts ========================================================================================================================= platform darwin -- Python 3.3.0 -- pytest-2.3.3 collected 0 items / 1 errors =============================================================================================================================== ERRORS ================================================================================================================================ _________________________________________________________________________________________________________________ ERROR collecting test/test_misc.py __________________________________________________________________________________________________________________ test/test_misc.py:14: in <module> > from ll import misc <frozen importlib._bootstrap>:1558: in _find_and_load > ??? <frozen importlib._bootstrap>:1516: in _find_and_load_unlocked > ??? <frozen importlib._bootstrap>:1470: in _find_module > ??? ../pyvenvs/default/lib/python3.3/site-packages/pytest-2.3.3-py3.3.egg/_pytest/assertion/rewrite.py:66: in find_module > fd, fn, desc = imp.find_module(lastname, path) ../.local/lib/python3.3/imp.py:192: in find_module > "not {}".format(type(name))) E RuntimeError: 'list' must be None or a list, not <class 'str'> ======================================================================================================================= 1 error in 0.05 seconds ======================================================================================================================= ``` However using the package from within Python still works without a problem: ``` #!bash $ python Python 3.3.0 (default, Sep 29 2012, 23:56:05) [GCC 4.2.1 Compatible Apple Clang 4.0 ((tags/Apple/clang-421.0.57))] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from ll import misc >>> misc.gzip(b'foo') b'\x1f\x8b\x08\x00\xb4\xbc\x9bP\x02\xffK\xcb\xcf\x07\x00!es\x8c\x03\x00\x00\x00' ``` -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0

[py-dev] [hpk42/pytest] setup_class was not set correctly as class level (issue #220)
by Anonymous Nov. 7, 2012

Nov. 7, 2012

--- you can reply above this line --- New issue 220: setup_class was not set correctly as class level https://bitbucket.org/hpk42/pytest/issue/220/setup_class-was-not-set-correc… Anonymous: #test_d.py source: setup_class was called for each test cases, while teardown was called once import pytest import imp, sys, subprocess class TestD: @classmethod def setup_class(cls): print 1/0 def test_ssl_exchange_cert(self): assert 1==1 def test_verify(self): assert 1==1 @classmethod def teardown_class(cls): print 1/0 ######################################### #Output from console ######################################### ============================= test session starts ============================== platform linux2 -- Python 2.7.3 -- pytest-2.2.4 collecting ... collected 2 items test_d.py EEE ==================================== ERRORS ==================================== ________________ ERROR at setup of TestD.test_ssl_exchange_cert ________________ cls = <class test_d.TestD at 0x8738fbc> @classmethod def setup_class(cls): > print 1/0 E ZeroDivisionError: integer division or modulo by zero test_d.py:8: ZeroDivisionError _____________________ ERROR at setup of TestD.test_verify ______________________ cls = <class test_d.TestD at 0x8738fbc> @classmethod def setup_class(cls): > print 1/0 E ZeroDivisionError: integer division or modulo by zero test_d.py:8: ZeroDivisionError ____________________ ERROR at teardown of TestD.test_verify ____________________ cls = <class test_d.TestD at 0x8738fbc> @classmethod def teardown_class(cls): > print 1/0 E ZeroDivisionError: integer division or modulo by zero test_d.py:21: ZeroDivisionError =========================== 3 error in 0.02 seconds ============================ -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue.

1 0