Mailman 3 August 2018 - pytest-dev

pytest Quick Start Guide
by Bruno Oliveira Aug. 30, 2018

Aug. 30, 2018

Hi everyone, I'm pleased to announce the release of my book about pytest: https://www.packtpub.com/web-development/pytest-quick-start-guide I cover how to get started quickly to use pytest in your daily work, and some more niche topics like techniques to convert unittest-based suites to pytest. Cheers, Bruno.

2 2

anyone up for giving a training in SFO?
by holger krekel Aug. 29, 2018

Aug. 29, 2018

Hello pytest testing experts and devs, a good longtime client has asked me if someone not too far away from San francisco could give pytest training(s) (beginner/advanced). Me and Carl Meyer have given these trainings but are both not available currently (and not very local to SFO). There is good tested training materials i can provide -- and preferred is someone who wouldn't have long travel to SFO. Please let me know if you are interested. best, holger

1 0

sorting out broken config initialization - by doing major releases with api breakages
by RonnyPfannschmidt Aug. 21, 2018

Aug. 21, 2018

Hi everyone, currently pytest configguration initialization is pretty much broken in many details, and as far as i can tell its going to be even more tricky to try and fix than marks, i will not again go trough the pain that i had with marks and want to sort out a gate to lift and change detail apis that will be broken. -- Ronny

3 6

junitxml update
by Rusty Howell Aug. 20, 2018

Aug. 20, 2018

Hey all, I am interested in working on junitxml. There are several bugs right now relating to it. https://github.com/pytest-dev/pytest/issues/3777 https://github.com/pytest-dev/pytest/issues/3547 https://github.com/pytest-dev/pytest/issues/1862 https://github.com/pytest-dev/pytest/issues/1126 In the comments in those bugs, there are some big ideas about the path forward, but I'd like to have a more consolidated space for those ideas. My end goal would be to have xml output that is compatible with the Jenkins Junit Test Report plugin. We may even have to support multiple versions of the plugin. Additionally, there are certainly other xUnit style tools that my be slightly different than Junit. Ronny mentioned in one of the bugs the idea of Pytest creating a serialized test log, and then have an Junitxml plugin consume the serialized data and reformat/output as needed. To me it seems that perhaps this could be analogous to logging Loggers and Handlers, where a handler could be specific, like "Jenkins Junit Test Report v1.3" vs "Jenkins Junit Test Report v1.4", or "Allure 2.6.0", etc. What are the general thoughts on the path forward for junitxml? Thanks

4 11

pytest 3.7.2 released
by Bruno Oliveira Aug. 18, 2018

Aug. 18, 2018

pytest 3.7.2 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at http://doc.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Josh Holland * Ronny Pfannschmidt * Sankt Petersbug * Wes Thomas * turturica Happy testing, The pytest Development Team

1 0

Partnership possibility with Pytest
by Alex Georgie Aug. 8, 2018

Aug. 8, 2018

Hi everyone, I'm Alex from SeedAndDew. I was chatting with Holger and Bruno about SeedAndDew and whether Pytest would like to participate and they mentioned bringing it to the dev mailing list to get your opinions. *What is it?* SeedAndDew is a common subscription platform that allows users to contribute to a number of open source projects with a single subscription. The idea here is that it's a lot easier to get people to contribute $10/month to every open source project they work with than it is to get them to contribute $5/month for a specific project. The subscription revenue will be distributed based on the amount of time users spend reading documentation of the respective project which I anticipate will correspond well with actual use. So if a user spends 10% of their time reading the Pytest documentation, you get 10% of the subscription revenue. *How it works* We provide you a script that you add to the Pytest site. That script makes a call to our site to create a 'drop' every 2 seconds a user is on your site. If the user is part of our network, we would have provided a cookie to them when they signed in which gets passed to us when that call is made. We authenticate using that cookie and assign that drop to them and you. If they are not part of the network there is no cookie, they won't be authenticated and the process ends there. We aggregate those drops at the end of the month to figure out the revenue distribution. The info we have is purely opt in since the user need to not only have an account with us but pay us every month. We haven't built this yet, but the intention is to keep that data for 3 months for auditing purposes and then delete it. We take a 30% cut of the subscription that includes payment processing costs which allows us to be sustainable, so we don't need to get creative with the data. The other feature needed for GDPR is the export of user data which is also in the pipeline. Our goal is to increase the pool of people who contribute to open source by removing the friction of having to manage subscriptions paid to specific projects and changing it as your stack and interests change. This would be a passive income source that doesn't require any further work outside of the initial integration. So far we have 10 projects including SQL Alchemy, RSpec, Bundler, Browsh and Parse. Does this seem like something you would be interested in? Thanks, Alex <http://mailstat.us/tr/opt-out?guid=ycoxm178jk9b4dpm> <http://mailstat.us/tr/t/dummy>

5 7

Code of conduct for pytest organisation on GitHub
by Dave Hunt Aug. 4, 2018

Aug. 4, 2018

I’d like to add a code of conduct for my pytest plugins, and as they’re mostly under the pytest organisation on GitHub I thought it would make sense to use the same as the pytest project. I was surprised to find that the pytest project does not currently have a code of conduct according to https://github.com/pytest-dev/pytest/community <https://github.com/pytest-dev/pytest/community>. Is there one documented elsewhere? If not, which should we adopt? Cheers, Dave

6 10

PEP420, Namespace Packages and Pytest Test Layout
by Alexandre Figura Aug. 2, 2018

Aug. 2, 2018

Hi all, I recently discovered that it was possible to import test modules from other test modules without having __init__.py files in my test directories. I thought it was impossible to do so with Pytest. And discovered it was possible because of the PEP420 and namespace packages <https://docs.pytest.org/en/latest/goodpractices.html?highlight=pep420#tests…>. However, I am wondering now if I should rely on the PEP420 to import test modules. I mean, is Pytest designed to be used in this way? Or should I avoid to rely on Python 3 behavior, and use a more "Pytestic" way of structuring my test modules? Waiting for your feedback on this topic, Have a nice day ;)

2 1