Mailman 3 September 2018 - pytest-dev

keeping passwords out of code
by Derek Sisson Sept. 26, 2018

Sept. 26, 2018

Hi, I have an end-to-end test framework built on top of pytest, and a big challenge is managing application passwords while keeping them out of the code base. I deal with multiple applications and services, on multiple tiers (staging, production, etc.), so I have a large set of user-password pairs to manage. I currently use a local yaml file, with passwords keyed to account ids, along with a data model of users in the codebase keyed to the same IDs. My conftest queries the yaml file with the ids to grab the passwords, and it's set up to throw exceptions if there is anything out of sync between the data model and the yaml file data. Cumbersome, but works.... locally. I need to port the framework to Jenkins, so I need a better and secure system. Suggestions on better ways of managing passwords and secrets in a pytest/jenkins context? thanks, --derek

3 2

Hacktoberfest - Beginner Issues
by Maik Figura Sept. 24, 2018

Sept. 24, 2018

Hey everyone, I noticed that the issue tracker almost hit 500 issues. Would it be good to discuss how to handle issues in general (follow ups, etc) and on how to maybe reduce the amount of outdated issues (I am not even sure there are outdated ones...). Do we maybe have examples how other projects do this? Or maybe this was already discussed and I just missed it? Best, Maik.

3 5

branch proposals - python2 support and pytest 4.0 preps
by Ronny Pfannschmidt Sept. 24, 2018

Sept. 24, 2018

hi everyone, in face of the pending larger changes for a pytest 4.0 removing various things and for the support branching of python2 id like to propose 2 extra branches a) maintenance-python2 : this will be the branch where bugfixes for the last python2 suporting versions will happen i intend to create it in line with the yet to be shaped plans for the python2 support/maintenance branches once the poll results are reviwerd and we have decided on a timeline to put into action b) removals or breakage : this will be the branch where we merge breaking changes in preparation of major releases i'd like to get this one started soon and create according automation to ensure we merge/move patches across bugfixes, features and the removal/breakage branches in a timely manner -- Ronny

4 5

Re: [pytest-dev] [TIP] pytest Python 2.7 support (poll) (re-sent)
by Ronny Pfannschmidt Sept. 23, 2018

Sept. 23, 2018

(re-sending since i used the wrong mail first) I refuse since its a pain to sort out GDPR compliance when self- hosting that way. public is easy, public and law abiding is a pain. -- Ronny Am Sonntag, den 23.09.2018, 18:57 +0200 schrieb Daniel Knüttel: > Am Sonntag, den 23.09.2018, 08:20 -0500 schrieb Ian Stapleton > Cordasco: > > It's also important to note that you need to have a Twitter account > > to > > vote, which will probably exclude a fair number of potential > > voters. > > > > This would exclude for instance me. If you send me the exact > questions > I can recreate the poll on my personal Nexcloud server so the poll is > truly public. > > By the way: I think 2.7 support should be dropped.

1 0

Accessing markers in pytest_generate_tests
by Nikolaus Rath Sept. 23, 2018

Sept. 23, 2018

Hello, I am currently using code like this: def pytest_generate_tests(metafunc, _info_cache=[]): # [...] fn = metafunc.function do_something(fn.with_backend.kwargs) for spec in fn.with_backend.args: # [...] This has started to emit a warning: /home/nikratio/in-progress/s3ql/tests/t1_backends.py:118: RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code for spec in fn.with_backend.args: In my case, the correction solution seems to be to use the get_closest_marker() method instead. However, this is defined for Node - neither the metafunc nor the metafunc.function objects have such a method. What's the recommended way to access markers in pytest_generate_tests? Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«

3 2

pytest Python 2.7 support (poll)
by Bruno Oliveira Sept. 23, 2018

Sept. 23, 2018

Hi everyone, There's a poll on twitter regarding when pytest should drop Python 2.7 support: https://twitter.com/ossronny/status/1043837215175057408 I urge everyone who uses pytest to cast their vote! Important to note that even when pytest drops support, Python 2.7 users will still be able to use old pytest versions (in fact pip will always install a compatible version automatically). Cheers, Bruno.

1 0

pytest 3.8.1 released
by Ankit Goel Sept. 22, 2018

Sept. 22, 2018

pytest 3.8.1 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 https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Ankit Goel * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Maximilian Albert * Ronny Pfannschmidt * William Jamir Silva * wim glenn Happy testing, The pytest Development Team

1 0

Hacktober coming up
by Brianna Laugher Sept. 21, 2018

Sept. 21, 2018

Hi, I was reminded today that github's month long event encouraging people to submit PRs to open source projects will begin once again in a week or so. I am not sure how much increased activity was notice last year, but perhaps it would be prudent to do a bit of extra issue grooming if we can. Especially labeling beginner friendly/easy issues. Cheers Brianna

1 0

VS Team Services
by Bruno Oliveira Sept. 20, 2018

Sept. 20, 2018

Hi everyone, Just to let the other core-devs know that I have created a pytest-dev organization at Visual Studio Team Services. I'm just reserving the name for now in case we want to make use of VS Team Services in the future (like tox is doing right now). I've sent invites to Holger and Ronny to reduce bus factor, but if others would like to play around and want access just let me know. Cheers, Bruno.

1 0

pytest.raises message parameter
by Bruno Oliveira Sept. 13, 2018

Sept. 13, 2018

Hi everyone, When using `pytest.raises`, it seems a lot of users confuse the parameter `message` (a message to display if the with block finishes with no exception) and `match` (a regular expression that the exception should match), using the former when they meant the latter. This is very dangerous as provides false positives. https://docs.pytest.org/en/latest/reference.html#pytest-raises Roman Yurchak posted a detailed example including PRs of projects that were using the parameter incorrectly (using `message` when they meant `match`), so this seems like a common problem. So we have two proposals: 1, Deprecate `message` and use another parameter name. Little tricky to find a suitable name that cannot be confused with `match`, but this is a safe approach. 2. Removing the parameter altogether (after deprecating it). This would make it match (heh) `pytest.warn`'s signature as well, which is a bonus. This is an excellent option in the long term if there are no good use-cases for it. It would be helpful if people can provide good use cases to keep `message`/`show_failure_message`, around, and also their opinion about this matter. I would like to keep the discussion in the issue itself, I'm using the mailing list because few people here follow the GitHub issues by the sheer amount of it: https://github.com/pytest-dev/pytest/issues/3974 So let's please not continue this discussion here and use the issue itself. Thanks! Cheers, Bruno.

1 0