Mailman 3 April 2010 - pytest-dev

[py-dev] Testing and Coverage against different python interpreter versions
by James Mills April 26, 2010

April 26, 2010

Hi All, I am in need of a solution regarding the use of py.test and pytest-coverage (the coverage plugin I help maintain for py.test). The problem is being able to run a test suite against 2 or more different python interpreter versions (eg: 2.5 and 2.6) AND combining their coverage data. Without the above behavior, it would not be possible to achieve 100% code coverage (by tests). Often (at least I do) in situations where you wish to support 2 or more different versions of python you might have: try: import foo # 2.6 import except ImportError: import bar # 2.5 import and if sys.version_info[:2] == (2, 6): # 2.6 code else: # 2.5 code Currently I have no solution for this, I'm hoping others might have some ideas or are already working on something similar that might achieve this. cheers James -- -- "Problems are solved by method"

3 8

[py-dev] distributed test slave activation of external plugin
by meme dough April 26, 2010

April 26, 2010

Hi, Is there any way to activate external plugins for distributed testing on the slave side? Currently pytest-cov requires that it is installed on the slave version of python. This differs from pytest-xdist that will rsync itself across, such that the only requirement on the slave side is python. If pytest-cov is not installed on the slave then the master has sent the slaveinput but the plugin is never activated on the slave hence no coverage. I can rsync pytest-cov over to the slave in same way as py / xdist already get done but unknown if I can activate the plugin. A separate but related issue: It would be good to have some way (cmd line / conftest / api) to tell xdist not to rsync py / xdist to the slave. The case is needed for the client code where it take care of all rsync so second rsync by xdist produce the warning about to two py and two xdist on path. :)

2 1

[py-dev] xdist sending info between master and slave - support for client code
by meme dough April 23, 2010

April 23, 2010

Hi, I'm using pytest and the xdist plugin. I'd like to get some information from the master to the slave, specifically on the slave side I need to know the master's host, master's topdir and master's rsync roots. Currently I modified xdist to send the required info over the channel in install_slave: master_host = socket.gethostname() master_topdir = config.topdir channel.send((config, basetemp, gateway.id, master_host, master_topdir, roots)) The rsync roots were passed into the TXNode during creation by the NodeManager: node = TXNode(gateway, self.config, putevent, self.roots) That gets the info there but I'm not sure of the best way. The master host / topdir could be added to config.options since that get pickled over the channel, but it's not a command line option so it doesn't seem the best place to put that info. But it would work from a client point of view without modifying xdist. The master rsync roots can't be worked out by client unless it reimplements the NodeManager._getrsyncdirs logic. This happens because DSession does setup which creates NodeManager and setup_nodes which does install_slave without any client hook in between so at no point can client get rsync roots from session.nodemanager.roots and put them in something like config.options to get to slave side. That is the first half. Next I need to send some info back from slave to master when slave has finished. Currently I modified xdist to send back a report object when the slave has finished. The SlaveNode has a report object which any client hook can change or add to if they want to send info back to master: self.report = None I use pytest_sessionfinish hook on slave to set report to dict with info. When slave finish it sendevent with the report: self.sendevent("slavefinished", report=self.report) The TXNode on master gets report and stores the slave report on itself: self.report = kwargs['report'] Then on master use pytest_testnodedown hook to get slave report off TXNode. That gets the info back from slave to master but I'm not sure if that's best way. Is it possible to modify xdist so that client code on master can send info to the slave. Will need access to rsync roots before it goes ahead and installs the slave though. Is it possible to modify xdist so that client code on the slave can send info back to the master. This looks like must modify xdist somehow since it doesn't seem to send any report back at finish. Now that I wrote all that, what is the obvious answer that I didn't see? :)

2 10

[py-dev] py.test : setup / teardown at the directory level
by Philippe Fremy April 16, 2010

April 16, 2010

Hi, I was wondering if there is a possibility to have or emulate setup/teardown method for an entire directory of tests ? I have an expensive setup/teardown method, which I share through about 10 modules, each with about 20 tests. I would save time if I could do the setup/teardown just for that directory. cheers, Philippe

3 9

[py-dev] order of setup / teardown
by Philippe Fremy April 12, 2010

April 12, 2010

Hi, I am not sure if this has been brought before, but I am surprised to see some calls inside the test "hooks" after the test session has finished. I am referring here to teardown_class, revealed by a quick example: pytest_sessionstart setup_class setup_method test1 teardown_method setup_method test2 teardown_method pytest_sessionfinish teardown_class This is creating problems for me because I am assuming that all resources are setup in sesssionstart, and torn down in sessionfinish. And teardown_class is using one of those resources. Is it a bug or intended behavior ? cheers, Philippe

2 1

[py-dev] oesjkit
by Laura Creighton April 8, 2010

April 8, 2010

Any idea how to get it listed here? http://pycheesecake.org/wiki/PythonTestingToolsTaxonomy#MockTestingTools Laura (still ill, but reading some mail now at any rate)

1 0

[py-dev] using oejskit to test hosted html
by simongsmith＠gmail.com April 8, 2010

April 8, 2010

I've been exploring the examples of using oejskit (from [http://www2.openend.se/~pedronis/oejskit/talk/examples.tgz: <http://www2.openend.se/~pedronis/oejskit/talk/examples.tgz>]) and they work fine for me. I wanted to change the test_open_eval.py to access the same foo.html via an apache website I'm hosting (it is static in the original). I'm envoking with "py.test test" and am using python2.6, py.test 1.2.1 and oejskit 0.8.8 on a Mac running OS X. Original code (test/test_open_eval.py) from oejskit.testing import BrowserTestClass, JsFailed class TestOpenEval(BrowserTestClass): jstests_browser_kind = 'supported' def test_open_eval(self): pg = self.open('/static/foo.html') title = pg.eval('document.title') assert title == 'Foo' I changed the open call: pg = self.open('http://mysite.net/foo.html') When I re-run the test, the foo.html is loaded into the browser that is launched as a result of the test, and it is identical (via "View Frame Source") as the original, but I get the following error: self = <oejskit.browser_ctl.PageContext object at 0x156dc90> js = 'document.title', variant = 'eval' def eval(self, js, variant='eval'): outcome = self._execute(variant, js, self.root, self.timeout) if outcome.get('error'): > raise JsFailed('[%s] %s' % (self.label, js), outcome['error']) E JsFailed: [[http://ctier.arcode.com:8888/foo.html: <http://ctier.arcode.com:8888/foo.html>]] document.title: FAILED: E message: Result of expression 'frameWin.eval' [undefined] is not a function. E line: 169 E sourceId: 457014824 E sourceURL: [http://localhost:62737/browser_testing/rt/InBrowserTesting.js: <http://localhost:62737/browser_testing/rt/InBrowserTesting.js>] E expressionBeginOffset: 4985 E expressionCaretOffset: 4998 E expressionEndOffset: 5004 E name: TypeError ../../../arcode/python/arcode/js- infrastructure/oejskit/browser_ctl.py:263: JsFailed I've dug around in the oejskit code and I don't understand what's going wrong and I can't find any documentation on this… has anyone successfully used oejskit to assert against html hosted on a remote apache? Or does anyone have any suggestions as to what I might be doing incorrectly? foo.html follows below. Thanks!!! Simon Smith [simongsmith(a)gmail.com: <mailto:simongsmith@gmail.com>] foo.html: <html> <head> <title>Foo<title> <script> </script> </head> <body> </body> </html>

2 1

[py-dev] ANN: oejskit 0.8.8 JavaScript in-browser testing with py.test plugin and unittest.py glue
by Samuele Pedroni April 6, 2010

April 6, 2010

Hi, I just pushed a new release of OE jskit 0.8.8 to PyPI. Main points of interest: * the code to check for the presence of browsers locally has been improved, browser specifications can now with confidence list absent browsers and the respective runs/tests will be skipped * added a workaround to a bug in Firefox 3.5 that interferes with the global variable leak detection code, this is simply turned off for FF3.5. The bug itself is fixed in FF3.6 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 requires py.test 1.1.1 and should also work with current trunk. More information and downloading at: http://pypi.python.org/pypi/oejskit including a changelog, documentation and the talk I gave at Europython 2009. jskit was initially developed by Open End AB and is released under the MIT license. In various incarnations it has been in use and useful at Open End for more than two years, we are quite happy to share it. Samuele Pedroni for Open End _______________________________________________ py-dev mailing list py-dev(a)codespeak.net http://codespeak.net/mailman/listinfo/py-dev

1 0