Mailman 3 January 2011 - pytest-dev

[py-dev] py.test doctest and hooks...
by Christian Klinger March 14, 2011

March 14, 2011

Hello, are there any hooks in pytest which are executed before doctests are executed? I try to setup some stuff, which i want to hide in the doctest. I already tried some "normal" pytest hooks ala: - pytest_runtest_call(item):- pytest_runtest_setup(item): But none of them seems to be executed on doctest execution. Any ideas? Christian

2 3

[py-dev] use of md5 checksum in config.py/getconftestmodules looks fishy
by Ralf Schmitt Jan. 11, 2011

Jan. 11, 2011

_pytest/config.py contains the following code: ,---- | ... | conftestpath = path.join("conftest.py") | if conftestpath.check(file=1): | key = conftestpath.computehash() | # XXX logging about conftest loading | if key not in self._md5cache: | clist.append(self.importconftest(conftestpath)) | self._md5cache[key] = conftestpath | else: | # use some kind of logging | print ("WARN: not loading %s" % conftestpath) `---- If I put multiple conftest.py files with the same content into different subdirecties py.test will only read one of them. I try to make py.test ignore multiple subdirectories by putting the same conftest.py file into those subdirectories. py.test currently only ignores one of those. Regards -- Ralf

2 1

[py-dev] ANN: oejskit 0.9.0 JavaScript in-browser testing, now with py.test 2.0 support
by Samuele Pedroni Jan. 10, 2011

Jan. 10, 2011

Hi, I'm happy to announce a new release of OE jskit 0.9.0, just pushed to PyPI. Main highlights: - *py.test 2.0 is now supported!* py.test 1.x still works as well - reusing one page (tab/window) for all tests using the same setup in a session is now the default, this is enforced when using py.test 2.0 which collects all tests first - to make the one test page more functional, jskit displays during the test run a list of links on the upper right corner of the pages to easily jump to specific outcome section for a JavaScript test files or python module with JavaScript tests. About OE jskit: jskit contains infrastructure and in particular a py.test plugin to enable running unit tests for JavaScript code inside browsers. It contains also glue code to run JavaScript tests from unittest.py based test suites. The approach also enables to write integration tests such that the JavaScript code is tested against server-side Python code mocked as necessary. Any server-side framework that can already be exposed through WSGI can play. The plugin works with py.test 2.0 or late py.test 1.x. More information and downloading at: http://pypi.python.org/pypi/oejskit jskit was initially developed by Open End AB and is released under the MIT license. Samuele Pedroni

1 0

[py-dev] Using funcargs (monkeypatch, tmpdir) during setup
by Virgil Dupras Jan. 4, 2011

Jan. 4, 2011

Hi all, it's me again. I'm wondering what's the common pattern of pytest users regarding the use of monkey-patching and temporary directories in setup functions. I already have my own "home-brewed" (again!) mechanism for that, but I want to "pytest-ify" the way I write tests. So far, the only solution I can come up with is to have all tests use the funcarg(s) and pass them to the setup function when they're called. Example: def my_setup(monkeypatch, tmpdir): moneypatch.setattr(module, 'something', foo) tmpdir.mkdir('bar') def test1(monkeypatch, tmpdir): my_setup(monkeypatch, tmpdir) # test stuff def test2(monkeypatch, tmpdir): my_setup(monkeypatch, tmpdir) # test stuff This code works, but it seems repetitive to me, especially if only the setup use the monkeypatching and tmpdir, not the tests themselves. What are other pytest users doing in these situations? Is there some clever trick I'm unaware of? I'm certainly not the only person in that situation, am I? Thanks, Virgil Dupras

2 2