Mailman 3 December 2010 - pytest-dev

[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] Advanced monkeypatching?
by Virgil Dupras Dec. 21, 2010

Dec. 21, 2010

Hi there, Monkeypatching is great and all, but some type of patching is a little bit more complex to do, such as patching the system time and patching os.stat for specific filenames. I have my own "homebrewed" solution for this, but I was wondering if such solution had their place in the monkeypatch module of pytest itself. Does it? Or should a "pytest-monkeypatch++" package be created? The "homebrewed" code I'm talking about is at https://bitbucket.org/hsoft/hsutil/src/43014954c6a8/hsutil/testutil.py#cl-83 ( patch_osstat() and patch_today() ). -- Virgil Dupras

3 7

[py-dev] Internal Error in xdist remove
by Andy Fundinger Dec. 10, 2010

Dec. 10, 2010

Continuing my attempted upgrade to pytest 2.0.0 I'm running into some errors with using xdist for parallel testing, this test is meant to run on two local nodes in parallel and boxed, but somehow it's trying to remove something that isn't there. Any ideas? The full log is below with a few bits removed because they reference my source code, if they're critical I can obscure the data rather than removing them or try to reproduce with non-project code. Andy Fundinger scheduling tests via LoadScheduling INTERNALERROR> config = <_pytest.config.Config object at 0xff22a90> INTERNALERROR> INTERNALERROR> def pytest_cmdline_main(config): INTERNALERROR> """ default command line protocol for initialization, session, INTERNALERROR> running tests and reporting. """ INTERNALERROR> session = Session(config) INTERNALERROR> session.exitstatus = EXIT_OK INTERNALERROR> try: INTERNALERROR> config.pluginmanager.do_configure(config) INTERNALERROR> config.hook.pytest_sessionstart(session=session) INTERNALERROR> config.hook.pytest_collection(session=session) INTERNALERROR> > config.hook.pytest_runtestloop(session=session) INTERNALERROR> INTERNALERROR> config = <_pytest.config.Config object at 0xff22a90> INTERNALERROR> session = <Session 'gauss_tools'> INTERNALERROR> INTERNALERROR> /home/andy/trunk/ext_linux64/python264/lib/python2.6/site-packages/pytest-2.0.1.dev5-py2.6.egg/_pytest/main.py:65: INTERNALERROR> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ INTERNALERROR> INTERNALERROR> self = <HookCaller 'pytest_runtestloop'> INTERNALERROR> INTERNALERROR> def __call__(self, **kwargs): INTERNALERROR> methods = self.hookrelay._pm.listattr(self.name) INTERNALERROR> > return self._docall(methods, kwargs) INTERNALERROR> INTERNALERROR> kwargs = {'session': <Session 'gauss_tools'>} INTERNALERROR> methods = [<function pytest_runtestloop at 0x1001b758>, <bound method DSession.pytest_runtestloop of <xdist.dsession.DSession instance at 0x180b5368>>] INTERNALERROR> self = <HookCaller 'pytest_runtestloop'> INTERNALERROR> INTERNALERROR> /home/andy/trunk/ext_linux64/python264/lib/python2.6/site-packages/pytest-2.0.1.dev5-py2.6.egg/_pytest/core.py:390: INTERNALERROR> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ INTERNALERROR> INTERNALERROR> self = <HookCaller 'pytest_runtestloop'> INTERNALERROR> methods = [<function pytest_runtestloop at 0x1001b758>, <bound method DSession.pytest_runtestloop of <xdist.dsession.DSession instance at 0x180b5368>>] INTERNALERROR> kwargs = {'session': <Session 'gauss_tools'>} INTERNALERROR> INTERNALERROR> def _docall(self, methods, kwargs): INTERNALERROR> self.trace(self.name, kwargs) INTERNALERROR> self.trace.root.indent += 1 INTERNALERROR> mc = MultiCall(methods, kwargs, firstresult=self.firstresult) INTERNALERROR> try: INTERNALERROR> > res = mc.execute() INTERNALERROR> INTERNALERROR> kwargs = {'session': <Session 'gauss_tools'>} INTERNALERROR> mc = <MultiCall 0 results, 1 meths, kwargs={'session': <Session 'gauss_tools'>}> INTERNALERROR> methods = [<function pytest_runtestloop at 0x1001b758>, <bound method DSession.pytest_runtestloop of <xdist.dsession.DSession instance at 0x180b5368>>] INTERNALERROR> self = <HookCaller 'pytest_runtestloop'> INTERNALERROR> INTERNALERROR> /home/andy/trunk/ext_linux64/python264/lib/python2.6/site-packages/pytest-2.0.1.dev5-py2.6.egg/_pytest/core.py:401: INTERNALERROR> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ INTERNALERROR> INTERNALERROR> self = <MultiCall 0 results, 1 meths, kwargs={'session': <Session 'gauss_tools'>}> INTERNALERROR> INTERNALERROR> def execute(self): INTERNALERROR> while self.methods: INTERNALERROR> method = self.methods.pop() INTERNALERROR> kwargs = self.getkwargs(method) INTERNALERROR> > res = method(**kwargs) INTERNALERROR> INTERNALERROR> kwargs = {} INTERNALERROR> method = <bound method DSession.pytest_runtestloop of <xdist.dsession.DSession instance at 0x180b5368>> INTERNALERROR> self = <MultiCall 0 results, 1 meths, kwargs={'session': <Session 'gauss_tools'>}> INTERNALERROR> INTERNALERROR> /home/andy/trunk/ext_linux64/python264/lib/python2.6/site-packages/pytest-2.0.1.dev5-py2.6.egg/_pytest/core.py:322: INTERNALERROR> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ INTERNALERROR> INTERNALERROR> self = <xdist.dsession.DSession instance at 0x180b5368> INTERNALERROR> INTERNALERROR> def pytest_runtestloop(self): INTERNALERROR> numnodes = len(self.nodemanager.specs) INTERNALERROR> dist = self.config.getvalue("dist") INTERNALERROR> if dist == "load": INTERNALERROR> self.sched = LoadScheduling(numnodes, log=self.log) INTERNALERROR> elif dist == "each": INTERNALERROR> self.sched = EachScheduling(numnodes, log=self.log) INTERNALERROR> else: INTERNALERROR> assert 0, dist INTERNALERROR> self.shouldstop = False INTERNALERROR> self.session_finished = False INTERNALERROR> while not self.session_finished: INTERNALERROR> > self.loop_once() INTERNALERROR> INTERNALERROR> dist = 'load' INTERNALERROR> numnodes = 2 INTERNALERROR> self = <xdist.dsession.DSession instance at 0x180b5368> INTERNALERROR> INTERNALERROR> /home/andy/trunk/ext_linux64/python264/lib/python2.6/site-packages/pytest_xdist-1.6.dev2-py2.6.egg/xdist/dsession.py:204: INTERNALERROR> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ INTERNALERROR> INTERNALERROR> self = <xdist.dsession.DSession instance at 0x180b5368> INTERNALERROR> INTERNALERROR> def loop_once(self): INTERNALERROR> """ process one callback from one of the slaves. """ INTERNALERROR> while 1: INTERNALERROR> try: INTERNALERROR> eventcall = self.queue.get(timeout=2.0) INTERNALERROR> break INTERNALERROR> except queue.Empty: INTERNALERROR> continue INTERNALERROR> callname, kwargs = eventcall INTERNALERROR> assert callname, kwargs INTERNALERROR> method = "slave_" + callname INTERNALERROR> call = getattr(self, method) INTERNALERROR> self.log("calling method: %s(**%s)" % (method, kwargs)) INTERNALERROR> > call(**kwargs) INTERNALERROR> INTERNALERROR> call = <bound method DSession.slave_testreport of <xdist.dsession.DSession instance at 0x180b5368>> INTERNALERROR> callname = 'testreport' INTERNALERROR> eventcall = ('testreport', {'node': <SlaveController gw0>, 'rep': {snip} when='call' outcome='passed'>}) INTERNALERROR> kwargs = {'node': <SlaveController gw0>, 'rep': {snip} when='call' outcome='passed'>} INTERNALERROR> method = 'slave_testreport' INTERNALERROR> self = <xdist.dsession.DSession instance at 0x180b5368> INTERNALERROR> INTERNALERROR> /home/andy/trunk/ext_linux64/python264/lib/python2.6/site-packages/pytest_xdist-1.6.dev2-py2.6.egg/xdist/dsession.py:222: INTERNALERROR> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ INTERNALERROR> INTERNALERROR> self = <xdist.dsession.DSession instance at 0x180b5368>, node = <SlaveController gw0> INTERNALERROR> rep = <TestReport {snip} when='call' outcome='passed'> INTERNALERROR> INTERNALERROR> def slave_testreport(self, node, rep): INTERNALERROR> if rep.when in ("setup", "call"): INTERNALERROR> > self.sched.remove_item(node, rep.nodeid) INTERNALERROR> INTERNALERROR> node = <SlaveController gw0> INTERNALERROR> rep = <TestReport {snip} when='call' outcome='passed'> INTERNALERROR> self = <xdist.dsession.DSession instance at 0x180b5368> INTERNALERROR> INTERNALERROR> /home/andy/trunk/ext_linux64/python264/lib/python2.6/site-packages/pytest_xdist-1.6.dev2-py2.6.egg/xdist/dsession.py:283: INTERNALERROR> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ INTERNALERROR> INTERNALERROR> self = <xdist.dsession.LoadScheduling instance at 0x1930f368>, node = <SlaveController gw0> {item removed} INTERNALERROR> INTERNALERROR> def remove_item(self, node, item): INTERNALERROR> if item not in self.item2nodes: INTERNALERROR> raise AssertiDN_XSS_NEUTRALIZE_onError(item, self.item2nodes) INTERNALERROR> nodes = self.item2nodes[item] INTERNALERROR> if node in nodes: # the node might have gone down already INTERNALERROR> nodes.remove(node) INTERNALERROR> #if not nodes: INTERNALERROR> # del self.item2nodes[item] INTERNALERROR> pending = self.node2pending[node] INTERNALERROR> > pending.remove(item) INTERNALERROR> E ValueError: list.remove(x): x not in list INTERNALERROR> {item and pending removed} INTERNALERROR> node = <SlaveController gw0> INTERNALERROR> nodes = [] INTERNALERROR> self = <xdist.dsession.LoadScheduling instance at 0x1930f368> INTERNALERROR> INTERNALERROR> /home/andy/trunk/ext_linux64/python264/lib/python2.6/site-packages/pytest_xdist-1.6.dev2-py2.6.egg/xdist/dsession.py:103: ValueError Regards, Andy Fundinger Risk Focus Inc. 424.243.6227 New York Office: +1 917 725 6006 Fax: +1 917 591 1616 London Office: +44 (0) 207 760 7184 Fax: +44 (0) 207 691 7165

2 1

[py-dev] Upgrading from pytest 1.3.2 to 2.0 - computed conftest options
by Andy Fundinger Dec. 7, 2010

Dec. 7, 2010

I'm trying to upgrade from py.test 1.3.2 to 2.0 but I'm running into issues with my use of the old style conftest.py feature to specify options. I specify options like: option_cov_branch = True option_cov_data_file = os.path.join(os.environ["PROJECT_ROOT"],"testCovFile%d.log"%random.randint(0,100000)) option_tx = ["popen//python=python",]*multiprocessing.cpu_count() the computed ones are a problem as the new .ini files can't take them and the conftest.py file specification seems to be ignored. Is there a particular hook that I can grab and add/change config values early enough to affect all plugins? Regards, Andy Fundinger Risk Focus Inc. 424.243.6227 New York Office: +1 917 725 6006 Fax: +1 917 591 1616 London Office: +44 (0) 207 760 7184 Fax: +44 (0) 207 691 7165

2 2

[py-dev] pytest-pep 0.7: check everything, determine your own PEP8 ignorance
by holger krekel Dec. 6, 2010

Dec. 6, 2010

Hi Alfredo, thanks for the feedback. i released pytest-pep8 0.7 now which has a [pytest] pep8ignore = OPT1 OPT2 ... option so that you can make up project specific list, starting now with a "check everything" setting. I updated the docs as well, see http://pypi.python.org/pypi/pytest-pep8 cheers, holger On Mon, Dec 06, 2010 at 09:55 -0500, Alfredo Deza wrote: > On Mon, Dec 6, 2010 at 9:50 AM, holger krekel <holger(a)merlinux.eu> wrote: > > > On Mon, Dec 06, 2010 at 09:00 -0500, Alfredo Deza wrote: > > > On Mon, Dec 6, 2010 at 8:46 AM, holger krekel <holger(a)merlinux.eu> > > wrote: > > > > > > > > > > > just released an initial version 0.6 of the pytest-pep8 plugin, > > > > integrating the ``pep8`` module into py.test runs, allowing full > > > > per-project customization and configuration. > > > > > > > > > > > This looks very useful as py.test plugin. > > > > > > Is there any way of getting junit output from it? This would help when > > using > > > it with Hudson. > > > > > > We already use the junit flag to output test results but wanted to add > > > something like the pep8 plugin > > > for correctness :) > > > > Heh, <borrowing-time-machine> actually > > > > py.test --pep8 --junitxml=mypath.xml > > > > should present all PEP8 errors or warnings in the JunitXML file. > > If not, i'd consider it a bug which you can report or fix > > with the http://bitbucket.org/hpk42/pytest-pep8 repo. > > > > Ok great, so no "extras" are involved to make it output to the JunitXML > file. Nice. > > > > > sidenote: i am not sure about the default behaviour - would it > > maybe make sense to start out with warning/erroring on everything > > and leaving it to project-specific configuration which warnings > > and pep8 errors to ignore? > > > > I think it is safe to assume that if you are using this plugin you want > everything > "ON" by default, so you can see what things you are interested in and tweak > (turn off) > as you progress. > > > > > cheers, > > holger > > > > > > > > > > > > > > > See http://pypi.python.org/pypi/pytest-pep8 for installation > > > > and configuration instructions. > > > > > > > > best, > > > > holger > > > > > > > > Usage > > > > ----------------- > > > > > > > > install pytest-pep8 via:: > > > > > > > > easy_install pytest-pep8 # or > > > > pip install pytest-pep8 > > > > > > > > and then type:: > > > > > > > > py.test --pep8 > > > > > > > > to activate source code checking. Every file ending in ``.py`` will be > > > > discovered and checked, starting from the command line arguments. > > > > For example, if you have a file like this:: > > > > > > > > # content of myfile.py > > > > > > > > somefunc( 123,456) > > > > > > > > you can run it with:: > > > > > > > > $ py.test --pep8 > > > > =========================== test session starts > > > > ============================ > > > > platform linux2 -- Python 2.6.5 -- pytest-2.0.1.dev1 > > > > pep8 ignore opts: E202 E221 E222 E241 E301 E302 E401 E501 E701 W293 > > W391 > > > > W601 W602 > > > > collecting ... collected 1 items > > > > > > > > myfile.py F > > > > > > > > ================================= FAILURES > > > > ================================= > > > > ________________________________ PEP8-check > > > > ________________________________ > > > > /tmp/doc-exec-12/myfile.py:2:10: E201 whitespace after '(' > > > > somefunc( 123,456) > > > > ^ > > > > /tmp/doc-exec-12/myfile.py:2:14: E231 missing whitespace after ',' > > > > somefunc( 123,456) > > > > ^ > > > > > > > > ========================= 1 failed in 0.01 seconds > > > > ========================= > > > > > > > > Note that in the testing header you see the current list of default > > > > "ignores". > > > > For the meaning of these error and warning codes, see the error output > > > > when running against your files or checkout `pep8.py > > > > <https://github.com/jcrocholl/pep8/blob/master/pep8.py>`_. > > > > > > > > Configuring PEP8 options per-project > > > > --------------------------------------------- > > > > > > > > Lastly, you may configure PEP8-checking options for your project > > > > by adding an ``pep8options`` entry to your ``pytest.ini`` > > > > or ``setup.cfg`` file like this:: > > > > > > > > [pytest] > > > > pep8options = +W293 -E200 > > > > > > > > > > > > Running PEP8 checks and no other tests > > > > --------------------------------------------- > > > > > > > > You can also restrict your test run to only perform "pep8" tests > > > > and not any other tests by typing:: > > > > > > > > py.test --pep8 -k pep8 > > > > > > > > This will only run tests that are marked with the "pep8" keyword > > > > which is added for the pep8 test items added by this plugin. > > > > > > > > Notes > > > > ------------- > > > > > > > > The repository of this plugin is at > > http://bitbucket.org/hpk42/pytest-pep8 > > > > > > > > For more info on py.test see http://pytest.org > > > > > > > > The code is partially based on Ronny Pfannschmidt's pytest-codecheckers > > > > plugin. > > > > > > > > > > > > _______________________________________________ > > > > testing-in-python mailing list > > > > testing-in-python(a)lists.idyll.org > > > > http://lists.idyll.org/listinfo/testing-in-python > > > > > > > > -- > > --

1 0

Re: [py-dev] [TIP] pytest-pep8 0.6: configurable PEP8 checking in py.test runs
by holger krekel Dec. 6, 2010

Dec. 6, 2010

On Mon, Dec 06, 2010 at 09:00 -0500, Alfredo Deza wrote: > On Mon, Dec 6, 2010 at 8:46 AM, holger krekel <holger(a)merlinux.eu> wrote: > > > > > just released an initial version 0.6 of the pytest-pep8 plugin, > > integrating the ``pep8`` module into py.test runs, allowing full > > per-project customization and configuration. > > > > > This looks very useful as py.test plugin. > > Is there any way of getting junit output from it? This would help when using > it with Hudson. > > We already use the junit flag to output test results but wanted to add > something like the pep8 plugin > for correctness :) Heh, <borrowing-time-machine> actually py.test --pep8 --junitxml=mypath.xml should present all PEP8 errors or warnings in the JunitXML file. If not, i'd consider it a bug which you can report or fix with the http://bitbucket.org/hpk42/pytest-pep8 repo. sidenote: i am not sure about the default behaviour - would it maybe make sense to start out with warning/erroring on everything and leaving it to project-specific configuration which warnings and pep8 errors to ignore? cheers, holger > > > > > See http://pypi.python.org/pypi/pytest-pep8 for installation > > and configuration instructions. > > > > best, > > holger > > > > Usage > > ----------------- > > > > install pytest-pep8 via:: > > > > easy_install pytest-pep8 # or > > pip install pytest-pep8 > > > > and then type:: > > > > py.test --pep8 > > > > to activate source code checking. Every file ending in ``.py`` will be > > discovered and checked, starting from the command line arguments. > > For example, if you have a file like this:: > > > > # content of myfile.py > > > > somefunc( 123,456) > > > > you can run it with:: > > > > $ py.test --pep8 > > =========================== test session starts > > ============================ > > platform linux2 -- Python 2.6.5 -- pytest-2.0.1.dev1 > > pep8 ignore opts: E202 E221 E222 E241 E301 E302 E401 E501 E701 W293 W391 > > W601 W602 > > collecting ... collected 1 items > > > > myfile.py F > > > > ================================= FAILURES > > ================================= > > ________________________________ PEP8-check > > ________________________________ > > /tmp/doc-exec-12/myfile.py:2:10: E201 whitespace after '(' > > somefunc( 123,456) > > ^ > > /tmp/doc-exec-12/myfile.py:2:14: E231 missing whitespace after ',' > > somefunc( 123,456) > > ^ > > > > ========================= 1 failed in 0.01 seconds > > ========================= > > > > Note that in the testing header you see the current list of default > > "ignores". > > For the meaning of these error and warning codes, see the error output > > when running against your files or checkout `pep8.py > > <https://github.com/jcrocholl/pep8/blob/master/pep8.py>`_. > > > > Configuring PEP8 options per-project > > --------------------------------------------- > > > > Lastly, you may configure PEP8-checking options for your project > > by adding an ``pep8options`` entry to your ``pytest.ini`` > > or ``setup.cfg`` file like this:: > > > > [pytest] > > pep8options = +W293 -E200 > > > > > > Running PEP8 checks and no other tests > > --------------------------------------------- > > > > You can also restrict your test run to only perform "pep8" tests > > and not any other tests by typing:: > > > > py.test --pep8 -k pep8 > > > > This will only run tests that are marked with the "pep8" keyword > > which is added for the pep8 test items added by this plugin. > > > > Notes > > ------------- > > > > The repository of this plugin is at http://bitbucket.org/hpk42/pytest-pep8 > > > > For more info on py.test see http://pytest.org > > > > The code is partially based on Ronny Pfannschmidt's pytest-codecheckers > > plugin. > > > > > > _______________________________________________ > > testing-in-python mailing list > > testing-in-python(a)lists.idyll.org > > http://lists.idyll.org/listinfo/testing-in-python > > --

1 0

[py-dev] pytest-pep8 0.6: configurable PEP8 checking in py.test runs
by holger krekel Dec. 6, 2010

Dec. 6, 2010

just released an initial version 0.6 of the pytest-pep8 plugin, integrating the ``pep8`` module into py.test runs, allowing full per-project customization and configuration. See http://pypi.python.org/pypi/pytest-pep8 for installation and configuration instructions. best, holger Usage ----------------- install pytest-pep8 via:: easy_install pytest-pep8 # or pip install pytest-pep8 and then type:: py.test --pep8 to activate source code checking. Every file ending in ``.py`` will be discovered and checked, starting from the command line arguments. For example, if you have a file like this:: # content of myfile.py somefunc( 123,456) you can run it with:: $ py.test --pep8 =========================== test session starts ============================ platform linux2 -- Python 2.6.5 -- pytest-2.0.1.dev1 pep8 ignore opts: E202 E221 E222 E241 E301 E302 E401 E501 E701 W293 W391 W601 W602 collecting ... collected 1 items myfile.py F ================================= FAILURES ================================= ________________________________ PEP8-check ________________________________ /tmp/doc-exec-12/myfile.py:2:10: E201 whitespace after '(' somefunc( 123,456) ^ /tmp/doc-exec-12/myfile.py:2:14: E231 missing whitespace after ',' somefunc( 123,456) ^ ========================= 1 failed in 0.01 seconds ========================= Note that in the testing header you see the current list of default "ignores". For the meaning of these error and warning codes, see the error output when running against your files or checkout `pep8.py <https://github.com/jcrocholl/pep8/blob/master/pep8.py>`_. Configuring PEP8 options per-project --------------------------------------------- Lastly, you may configure PEP8-checking options for your project by adding an ``pep8options`` entry to your ``pytest.ini`` or ``setup.cfg`` file like this:: [pytest] pep8options = +W293 -E200 Running PEP8 checks and no other tests --------------------------------------------- You can also restrict your test run to only perform "pep8" tests and not any other tests by typing:: py.test --pep8 -k pep8 This will only run tests that are marked with the "pep8" keyword which is added for the pep8 test items added by this plugin. Notes ------------- The repository of this plugin is at http://bitbucket.org/hpk42/pytest-pep8 For more info on py.test see http://pytest.org The code is partially based on Ronny Pfannschmidt's pytest-codecheckers plugin.

1 0

[py-dev] pytest-capturelog plugin 0.6
by meme dough Dec. 5, 2010

Dec. 5, 2010

Hi, Thanks to Floris the capturelog plugin now has a funcarg that allows adjusting the log levels and provides access to log records and the log text. :)

1 0