Mailman 3 August 2014 - pytest-dev

pytest github organization is taken
by Anatoly Bubenkov Jan. 29, 2015

Jan. 29, 2015

Hi all if it was you who created this org https://github.com/pytest please make Holger an admin if this name was taken by someone who's not related to pytest in any way, then we should make a claim to github to get the rights i guess the org is empty and created Oct 21, 2013 -- Anatoly Bubenkov

3 5

latest pytest and pytest-xdist
by Anatoly Bubenkov Sept. 2, 2014

Sept. 2, 2014

Hi anybody knows about the source of such message after test run: Unhandled exception in thread started by <bound method WorkerPool._perform_spawn of <execnet.gateway_base.WorkerPool object at 0xf8dbe10>> ? -- Anatoly Bubenkov

2 2

Encouraging the use of bookmarks rather then branches
by Floris Bruynooghe Aug. 15, 2014

Aug. 15, 2014

Hi, I was wondering if people would be fine with encouraging contributors to use bookmarks rather then named branches in mercurial for pull requests. Named branches are rather permanent and more suited for things like the 2.6.x release branch or permanent things like that. Bookmarks work really nice, the only downside is that bitbucket does not support them as well. They are shown on the commits view just fine, however when doing a pull request you will have to use the hex revision number in the bitbucket UI rather then having to use the bookmark name as it will just show the branch name "default" together with the hex number (multiple times if you have multiple heads). An additional benefit is that they wouldn't need the "closing branch" commit we get so often right now. Bookmarks do not make it to the repo on accepting a pull request. Even if a bookmark gets pushed to the hpk42/pytest repo they can be easily deleted without a commit (hg bookmark -d $name; hg push -B $name). The CONTRIBUTING.rst file would not even change that much for simple use, I've included the diff below to demonstrate. What do people think of this? Or am I the only one who doesn't like the accumulation of closed branches? Regards, Floris diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -97,11 +97,11 @@ 2. Create and activate a fork-specific v .. _checkout: 3. Clone your fork locally using `Mercurial <http://mercurial.selenic.com/>`_ - (``hg``) and create a branch:: + (``hg``) and create a bookmark:: $ hg clone ssh://hg@bitbucket.org/YOUR_BITBUCKET_USERNAME/pytest $ cd pytest - $ hg branch your-branch-name + $ hg bookmark your-bookmark-name If you need some help with Mercurial, follow this quick start guide: http://mercurial.selenic.com/wiki/QuickStart @@ -136,7 +136,7 @@ 4. You can now edit your local working c 5. Commit and push once your tests pass and you are happy with your change(s):: $ hg commit -m"<commit message>" - $ hg push -b . + $ hg push -B your-bookmark-name 6. Finally, submit a pull request through the BitBucket website: @@ -144,10 +144,14 @@ 6. Finally, submit a pull request throug :width: 700px :align: center - :: + Unfortunately bitbucket does currently not support pull requests + from bookmarks very well, this means you have to do the pull request + by the hex commit number rather then by name. To find the hex + commit revision run ``hg bookmarks`` locally and then use it in the + pull request dialog:: source: YOUR_BITBUCKET_USERNAME/pytest - branch: your-branch-name + branch: hex-commit-rev target: hpk42/pytest branch: default -- Debian GNU/Linux -- The Power of Freedom www.debian.org | www.gnu.org | www.kernel.org

5 7

pytest-2.6.1: fixes and expecting exceptions in xfail
by holger krekel Aug. 7, 2014

Aug. 7, 2014

pytest-2.6.1: fixes and new xfail marker feature =========================================================================== pytest is a mature Python testing tool with an extensive self-test test suite, passing on many different interpreters and platforms. The 2.6.1 release is drop-in compatible to 2.5.2 and actually fixes some regressions introduced with 2.6.0. It also brings a little feature to the xfail marker which now recognizes expected exceptions, see the CHANGELOG below. See docs at: http://pytest.org As usual, you can upgrade from pypi via:: pip install -U pytest Thanks to all who contributed, among them: Floris Bruynooghe Bruno Oliveira Nicolas Delaby have fun, holger krekel Changes 2.6.1 ================= - No longer show line numbers in the --verbose output, the output is now purely the nodeid. The line number is still shown in failure reports. Thanks Floris Bruynooghe. - fix issue437 where assertion rewriting could cause pytest-xdist slaves to collect different tests. Thanks Bruno Oliveira. - fix issue555: add "errors" attribute to capture-streams to satisfy some distutils and possibly other code accessing sys.stdout.errors. - fix issue547 capsys/capfd also work when output capturing ("-s") is disabled. - address issue170: allow pytest.mark.xfail(...) to specify expected exceptions via an optional "raises=EXC" argument where EXC can be a single exception or a tuple of exception classes. Thanks David Mohr for the complete PR. - fix integration of pytest with unittest.mock.patch decorator when it uses the "new" argument. Thanks Nicolas Delaby for test and PR. - fix issue with detecting conftest files if the arguments contain "::" node id specifications (copy pasted from "-v" output) - fix issue544 by only removing "@NUM" at the end of "::" separated parts and if the part has an ".py" extension - don't use py.std import helper, rather import things directly. Thanks Bruno Oliveira.

1 0

extended asserts
by Anatoly Bubenkov Aug. 4, 2014

Aug. 4, 2014

what do you think about extending the existing assert representation with this https://pypi.python.org/pypi/datadiff would be nice if we could extend datadiff with what pytest does for string diff and then just use datadiff for all assertions because for now, it's not too useful to see a comparison of 2 dicts in the pytest it's not readable especially if 2 dicts are big and nowadays, json so dicts are everywhere datadiff is cool at showing the diff between 2 dicts the reason why im asking without the PR is the politics about the dependencies as i know you're not so positive about adding them also this standalone mode is a bit tricky in that case, i guess example: def test_ticket_filter_on_order_uid__in(app, first_ticket, second_ticket, second_basket_ticket, order, second_order): """Test if the right result is returned when filtering on basket.""" ticket_filter = pta.ticket.filter(api_key=app.uid, order_uid__in=[order['uid']]).content > assert ticket_filter == [first_ticket, second_ticket] E assert [{'code': '91...dulum'}, ...}] == [{'basket_uid'... 'EUR'}, ...}] E At index 0 diff: {'code': '911338060856', 'subtitle': {'en': u'Subtitle1 Kaleidoscope'}, 'uid': u'37bc3c15e66a45e9bf3b52233fcdff02', 'order_uid': u'08dec1bd7ec249109729de448ffcc571', 'price': {'currency': 'EUR', 'amount': '1.20'}, 'fees': [{'price': {'currency': 'EUR', 'amount': '2.00'}, 'type': 'service costs'}], 'product_uid': u'32c2a6f98f0642b9843a8dcce6dead56', 'name': {'en': u'Ticket1 \u2603 Weapon'}} != {'subtitle': {'en': u'Subtitle1 Kaleidoscope'}, 'uid': u'37bc3c15e66a45e9bf3b52233fcdff02', 'price': {'currency': 'EUR', 'amount': '1.20'}, 'fees': [{'price': {'currency': 'EUR', 'amount': '2.00'}, 'type': 'service costs'}], 'basket_uid': u'871e829da04e4cd9a45d244f55824c83', 'product_uid': u'32c2a6f98f0642b9843a8dcce6dead56', 'name': {'en': u'Ticket1 \u2603 Weapon'}} just unreadable -- Anatoly Bubenkov

4 9