Mailman 3 February 2012 - pytest-dev

[py-dev] New plugin: pytest-timeout
by Floris Bruynooghe March 9, 2012

March 9, 2012

Hi all, This is to announce the first release of pytest-timeout, a plugin which will interrupt long running (i.e. blocking) tests. This is particularly useful when running the tests on a CI host. When a test is interrupted the stacks of all threads are dumped to stderr, which helps you to locate the reason for the blocking. If the system supports SIGALRM then the test itself is interrupted using pytest.fail() and other tests continue to run, otherwise the stack(s) are dumped to stderr and the process exists immediately. The plugin is available from the cheeseshop: http://pypi.python.org/pypi/pytest-timeout and the code lives at bitbucket: https://bitbucket.org/flub/pytest-timeout/. Feel free to provide any feedback or report issues. Regards, Floris -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org

4 12

[py-dev] XML Parsing Error when esc characters are in traceback
by Anton P March 5, 2012

March 5, 2012

Hello all, I have the following issue with generated junitxml reports: I'm writing test cases which use scapy functions. So I make asserts on some packet objects. As I understand scapy uses esc characters for its own objects representation, and I can see colorful output on the console. But when test is failed, and its traceback went to xml, I can't open generated xml due to the error "XML Parsing Error: not well-formed" In my case the problem with esc charecter 033 (\x1b). I resolved the issue by adding the following code to append_failure method in LogXML class: longrepr = str(report.longrepr).replace('\x1b', '\\033') fail.append(longrepr) I think that it will be good if you add some cleanup functions to avoid such situations. Thank you, -Anton

2 2

[py-dev] how to access docstrings from pytest_report_teststatus or pytest_runtest_logreport
by Anton P Feb. 17, 2012

Feb. 17, 2012

Hi, I'm trying to write my own py.test pluging for extended junitxml reports. This pluging have to parse testcase's docstrings for some additional info for report. I've found the next code in pytest_bugzilla plugin: def pytest_report_teststatus(self,report): if report.failed: if self.analysed(report.item.function.__doc__): return "analysed", "A", "ANALYSED" And I've tried to do the same to access docstrings. But I'm confused, because report object does not contain "item" attribute. At the moment I've added class ExtTestReport(TestReport) and redefined pytest_runtest_makereport() in plugin. The last hook now return report with "item" object. But I think, that redefining native pytest_runtest_makereport() in pluging is not the best idea. Especially because new method is always called regardless of my pluging usage. Please, point me to right solution to access testcase's docstrings from pytest_report_teststatus() or pytest_runtest_logreport(). Thank you in advance!

2 2

[py-dev] New plugin pytest-pydev
by Sebastian Rahlf Feb. 7, 2012

Feb. 7, 2012

Hello all! I've just released the first version of a new py.test plugin which will allow you to use a remote Python debug server. This will, for instance, come in especially handy if you want to find out why a particular unittest is failing in a web application. Simply fire up your debug server in your IDE (PyDev or PyCharm) e.g. on localhost:8042 and run your unittests with py.test --pydevd=your-ip:8042 If you have set a break point you should soon see the effects. Enjoy! Sebastian P.S. Feedback is always welcome!

1 1

[py-dev] pytest-2.2.2: bug fixes, collectonly improvements
by holger krekel Feb. 5, 2012

Feb. 5, 2012

pytest-2.2.2 is a minor backward-compatible release of the py.test testing tool. It contains bug fixes and a few refinements particularly to reporting with "--collectonly", see below for betails. For general information see here: http://pytest.org/ To install or upgrade pytest: pip install -U pytest # or easy_install -U pytest Special thanks for helping on this release to Ronny Pfannschmidt and Ralf Schmitt and the contributors of issues. best, holger krekel Changes between 2.2.1 and 2.2.2 ---------------------------------------- - fix issue101: wrong args to unittest.TestCase test function now produce better output - fix issue102: report more useful errors and hints for when a test directory was renamed and some pyc/__pycache__ remain - fix issue106: allow parametrize to be applied multiple times e.g. from module, class and at function level. - fix issue107: actually perform session scope finalization - don't check in parametrize if indirect parameters are funcarg names - add chdir method to monkeypatch funcarg - fix crash resulting from calling monkeypatch undo a second time - fix issue115: make --collectonly robust against early failure (missing files/directories) - "-qq --collectonly" now shows only files and the number of tests in them - "-q --collectonly" now shows test ids - allow adding of attributes to test reports such that it also works with distributed testing (no upgrade of pytest-xdist needed)

1 0