Mailman 3 February 2016 - pytest-dev

Moving pytest-rerunfailures to pytest-dev
by Florian Pilz Oct. 27, 2016

Oct. 27, 2016

Hi, I’m asking whether `pytest-rerunfailures` should be moved to the `pytest-dev` organisation (https://github.com/gocept/pytest-rerunfailures <https://github.com/gocept/pytest-rerunfailures>). Since we (gocept) only rarely take time to work on issues / pull requests of `pytest-rerunfailures` we would prefer to move the extremely useful plugin to `pytest-dev`. There we still can work on it, but are not the only ones taking care of the project. So if you think `pytest-rerunfailures` is a great addition to `pytest` and should be moved to the pytest-dev organization, let us know. :) Best wishes Florian ––––––––– Florian Pilz · fp(a)gocept.com · Software Developer gocept gmbh & co. kg · Forsterstraße 29 · 06112 Halle (Saale) · Germany http://gocept.com <http://gocept.com/> · Tel +49 345 122 9889 7 Python, Pyramid, Plone, Zope · consulting, development, hosting, operations

3 8

Sprint participants writing a blog post?
by Holger Krekel March 10, 2016

March 10, 2016

What about if each of us who wants to participate writes a small blog (lacking a blog a pytest-dev) post of where he/she comes from, past core or plugin work for example, and main areas of interest for the sprint? We could publish them via updates every few days. Any takers? -- Sent using mobile touch keys, increased chances for errors and misunderstandings. Enjoy!

9 26

Redirect pytest.org over readthedocs
by Bruno Oliveira March 4, 2016

March 4, 2016

Hi guys, I think the next step to complete the docs move to readthedocs is a server side configuration to redirect all requests from pytest.org to pytest.readthedocs.org... don't know anything about the subject, but a quick google search suggests its easy and quick to setup and test: http://www.inmotionhosting.com/support/website/redirects/setting-up-a-301-p… (yeah what a terrible website) I understand it's just the matter of writing a .htaccess file in the pytest.org folder with these contents: RewriteEngine on RewriteCond %{HTTP_HOST} ^pytest.org [NC,OR] RewriteCond %{HTTP_HOST} ^https://pytest.org [NC] RewriteRule ^(.*)$ https://pytest.readthedocs.org/en/$1 [L,R=301,NC] I wanted to go over the list first in case I'm missing anything obvious, also I'm wary of messing with the .htaccess site of 37k daily accesses and I know there are people in the list who knows their way around linux servers (The-Compiler for example). :) Cheers, Bruno.

2 4

question about pytest_addoption
by Bryan Berry March 1, 2016

March 1, 2016

dear pytest folks, I am creating an automation framework based on pytest for my employer that i hope to someday soon open-source. This framework is tentatively titled 'Ghost-elephant' after my child's imaginary friend. At a 5,000 foot view my ghost-elephant manages virtual machines and a bag of configuration variables needed to execute the tests. Ghost-elephant adds some custom command-line options but I also want to also allow libraries, say added by separate fixture libraries, to add command-line flags. For example, Ghost-elephant adds a flag --skip-cleanup that my custom software fixtures use to determine if the fixture's cleanup step should be skipped. A specific fixture library, say foo_fixture that handles the installation of some particularly hairy proprietary software, may want to add additional custom options. Perhaps, we need to pass this fixture a special flag to enable ipv6 support. Here is how I have currently attempted to support this feature and it isn't working at all. Could anyone point me towards a working solution? I really want to minimize the code that a user needs to add to their contest.py to take advantage of this. # foo_fixture.py def pytest_addoption_foo(parser): parser.addoption('--ipv6', action='store_true', default=False) @pytest.fixture def foo_fixture(request): ipv6 = request.config.getoption('--ipv6') # lots of complicated stuff # conftest.py def pytest_addoptions(): option_adders = [] gs = globals() for g in gs.keys(): if isinstance(gs[g], function) and g.startswith('pytest_addoption_'): option_adders.append(gs[g]) def pytest_addoption(parser): for o in option_adders: o.__call__(parser) pytest_addoptions()

2 3

Announcing pytest-cram
by Trevor Bekolay Feb. 28, 2016

Feb. 28, 2016

Hi everyone, Over the weekend I wrote a pytest plugin that will run tests developed for the cram tool (see https://bitheap.org/cram/) with pytest. I pushed the first release to PyPI today, and was hoping that anyone with experience with cram could test out pytest-cram on their tests. On PyPI: https://pypi.python.org/pypi/pytest-cram On Github: https://github.com/tbekolay/pytest-cram It's only the first release and no users yet, so I'm not asking to be added to the pytest-dev organization yet, though hopefully that will be possible. For now, I'm hoping that people find it useful. Please let me know if you run into any bugs by filing issues on Github. Thanks! Trevor

1 0

pytest-platform-markers v0.1.0 released!
by Florian Bruhin Feb. 26, 2016

Feb. 26, 2016

Hey, Bruno motivated[1] me to split some code I had in qutebrowser's testsuite to a separate plugin - so pytest-platform-markers[2] was born! The plugin provides various markers such as @pytest.mark.linux or @pytest.mark.windows which makes it easier to skip tests on platforms they don't run on. Enjoy! Florian [1] https://github.com/hackebrot/pytest-tricks/issues/3#issuecomment-188730108 [2] https://github.com/The-Compiler/pytest-platform-markers/ -- http://www.the-compiler.org | me(a)the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/

1 0

pytest 2.9.0-rc.1
by Bruno Oliveira Feb. 26, 2016

Feb. 26, 2016

Hi all, We released pytest 2.9.0-rc.1, a release candidate to try to identify any regressions before the official 2.9.0 release. It would be really helpful if people could install this version, execute their test suites and report any regressions to pytest-dev(a)python.org or the issues page[1]. To install this release, please execute the following with a virtualenv active: pip install -i https://devpi.net/nicoddemus/dev pytest==2.9.0-rc.1 [1] https://github.com/pytest-dev/pytest/issues Thanks, The py.test team.

3 8

ANN: pytest-nodev v0.9.3 - Test-driven code search
by Alessandro Amici Feb. 25, 2016

Feb. 25, 2016

I am pleased to announce the release of the new beta release of pytest-nodev (was pytest-wish) a test-driven code search plugin for pytest: https://pytest-nodev.readthedocs.org Changes: - renamed the package to pytest-nodev from pytest-wish (sorry!) - refuse to run potentially dangerous `--wish-from-all` by default and... - ... document how to run inside a container to safely enable all the features - simpler command line usage - more documentation and references to the academic research on the test-driven code search subject Development effort is directed to fixing bugs and writing better documentation before the 1.0 release. Help is welcomed and appreciated: https://github.com/nodev-io/pytest-nodev User questions are best directed to http://stackoverflow.com/search?q=pytest-nodev and general questions can be sent to pytest-dev(a)python.org. Thanks, Alessandro

1 0

sprint growing / funding at 60% now
by holger krekel Feb. 25, 2016

Feb. 25, 2016

Hey all, just some quick news: Splunk (company from west coast, US) just send $1000 which brings us to about 60% funded status, 22 days left. They'll also send Danielle and Antony from their QA department who i got to know personally a few weeks ago when i gave a master-class training in San Francisco. I amended the list of sprint participants in the repo and also added some preliminary company affilitations. Did i miss anyone except Ronny (who is 99% going to come ASFAIK but can currently be not much online)? Anatoly Bubenkoff, Netherlands Andreas Pelme, Personalkollen, Sweden Anthony Wang, Splunk, US Brianna Laugher, Australia Bruno Oliveira, Brazil Danielle Jenkins, Splunk, US Dave Hunt, UK Florian Bruhin, Switzerland Floris Bruynooghe, UK Holger Krekel, merlinux, Germany Oliver Bestwalter, Avira, Germany Omar Kohl, Germany Raphael Pierzina, US/UK Tom Viner, UK I also have a "likely attend" status from Stephan Obermann who is working for Dolby and at advanced-level with pytest, tox, devpi stuff since a few years. Please let me know if i missed anyone and add company affiliations if you like. Seems like i'll need to look for a bigger place than i initially thought :) More organisational details are coming in March. cheers, holger -- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu

1 0

Continue after rerunning failing test combined with exitfirst
by Florian Pilz Feb. 24, 2016

Feb. 24, 2016

Hi, a new issue was opened for `pytest-rerunfailures`, since it does not work nicely with the `—exitfirst` flag (see https://github.com/pytest-dev/pytest-rerunfailures/issues/30 <https://github.com/pytest-dev/pytest-rerunfailures/issues/30>). I have looked into the reports and tracked the state of `Session.testsfailed`, but since an outcome “failure" is overwritten with the outcome “rerun” no failures are recorded and `Session.testsfailed` remain 0 es expected. However, the test suite still stops after the test finally passes after the required amount of reruns. So my question is, which other mechanisms does pytest have to determine whether the test suite should be stopped? I’m pretty sure that exitfirst / maxfail = 1 is not the reason. To give you more context, I’m running the following tests with `py.test —reruns 3 -x`: def test_before(): pass def test_flaky(): import py path = py.path.local(__file__).dirpath().ensure('test.res') count = path.read() or 1 if int(count) <= 3: path.write(int(count) + 1) raise Exception('Failure: {}'.format(count)) def test_after(): pass ––––––––– Florian Pilz · fp(a)gocept.com · Software Developer gocept gmbh & co. kg · Forsterstraße 29 · 06112 Halle (Saale) · Germany http://gocept.com <http://gocept.com/> · Tel +49 345 122 9889 7 Python, Pyramid, Plone, Zope · consulting, development, hosting, operations

1 0