Mailman 3 December 2018 - pytest-dev

enhancing the assertion rewriting experience with custom integration/workflows
by Ronny Pfannschmidt July 29, 2019

July 29, 2019

Hi everyone, at a project at work which integrates pytest we did build a custom workflow around invoking tests and pytest. This in turn triggers a lot of warnings from the assertion rewriter about things that have been already imported. at first glance fixing this seems rather problematic, as the configuration of the assertion rewriting is deeply bound to the pytest configuration and it seems we cant do something simple and crude like letting a pth file fix the issue. i believe opening up the hooking system could be best done by moving it to a package with some sort of singleton control anyway - then pytest would be just a consumer of that api enabling if not enabled and push in its own "import roots". i'd like ot hear other impressions and ideas on this as well. -- Ronny

2 2

pytest 4.0.2
by Bruno Oliveira Dec. 14, 2018

Dec. 14, 2018

Hi everyone, pytest 4.0.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 https://docs.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Anthony Sottile * Bruno Oliveira * Daniel Hahler * Pedro Algarvio * Ronny Pfannschmidt * Tomer Keren * Yash Todi Happy testing, The pytest Development Team

1 0

data science benchmarks with pytest
by Sylvain MARIE Dec. 12, 2018

Dec. 12, 2018

Dear pytest community I am pleased to share with you today the first example in https://smarie.github.io/pytest-patterns/ ! This first example shows how to create a data science benchmark, like the ones in kaggle or driven data, using pytest and a few plugins (you will recognize the names from my previous posts ;) ). Maybe in the future someone in the community will find other “best practices” to share in terms of parameters/fixtures architectures for specific applications. In that case this project can serve as a placeholder for such examples. Kind regards -- Sylvain

1 0

Using pytest for the sympy doctests
by Oscar Benjamin Dec. 9, 2018

Dec. 9, 2018

Hi all, I'm trying to make it possible to use pytest with SymPy. I'm mostly there for the main tests now and the next step is to try and get it working for the doctests. Currently SymPy has it's own test runner which runs the doctests but it works a little differently from the standard doctests. Firstly SymPy's doctests are required to import all names use in the doctest. Standard doctest allows names from the enclosing module to be used without imports. It's considered important in SymPy that the doctests should error out if the imports are not included. So for example if I have def f(): '''' >>> f() 42 ''' return 42 then this should give an error in the doctests because the function f is undefined. A valid doctest for this would look like def f(): '''' >>> from module import f >>> f() 42 ''' return 42 It seems there is a feature in sympy to inject symbols into the doctest namespace: https://docs.pytest.org/en/latest/doctest.html#the-doctest-namespace-fixture but I'm really interested in removing things from the namespace to test for errors when something isn't properly imported in the doctest. The other issue is that SymPy has a few different ways of displaying output at the terminal: the repr, the ascii version, and the pretty version. The doctests are written for the ascii version but under pytest the pretty version is found as output. You can see this problem if you run e.g. $ git clone https://github.com/sympy/sympy.git $ cd sympy $ pytest --doctest-modules sympy/solvers/ode.py An example of the failures is /Users/enojb/current/sympy/sympy/sympy/solvers/ode.py:1501: DocTestFailure ___________________ [doctest] sympy.solvers.ode.constant_renumber 2896 Only constants in the given range (inclusive) are renumbered; 2897 the renumbering always starts from 1: 2898 2899 >>> constant_renumber(C1 + C3 + C4, 'C', 1, 3) 2900 C1 + C2 + C4 2901 >>> constant_renumber(C0 + C1 + C3 + C4, 'C', 2, 4) 2902 C0 + 2*C1 + C2 2903 >>> constant_renumber(C0 + 2*C1 + C2, 'C', 0, 1) 2904 C1 + 3*C2 2905 >>> pprint(C2 + C1*x + C3*x**2) Expected: 2 C1*x + C2 + C3*x Got: 2 C₁⋅x + C₂ + C₃⋅x To make this work I need to figure out a way for pytest to meet these two requirements: 1) Customise namespace used for tests 2) Customise the function that generates output before comparing with expected output of a doctest. Does anyone know if it's possible to do either of these things with pytest? -- Oscar

3 7

document outlining added values
by Sivan Grünberg Dec. 4, 2018

Dec. 4, 2018

Hi All, A transcript from a conversation about considering porting django TestCase's to pytest: "Some counterpoints: - Tomorrow `some_other_test` will be the guideline and pytest will be passe - Why add a new dependency when you have something built in, _if it's good enough_ But all that is just conversation, the real issue i'm having is: Now we have 2 ways of doing something in the project consistency is my #1 goal or requirement in a project Makes the codebase so much easier to maintain and learn (edited) I'm trying to grok if pytest gives us such advantages that it's worth gradually porting all tests to use it for consistency, but while the syntax is nice you could achieve the same thing by reading those paramterized lists in a loop i think?" Last remark was in reference to @pytest.mark.parametrize. Do we have a document somewhere to answer such? like a comparison that outlines why it might be better to do so , or alternatively, to discuss the contexts where sticking to Django TestCase's is better? Is there a full feature list that I may point people at when they ask me "why pytest" ? Cheers, -Sivan

3 6

Looking for additional maintainers for pytest plugins
by Dave Hunt Dec. 3, 2018

Dec. 3, 2018

Due to a change in my role, I’m no longer going to be able to spend as much time as I have with maintaining the plugins listed below. The maintenance burden is very light, and releases are handled through Travis CI. I’ve already had some excellent help from Jim Brännlund (BeyondEvil), and have added him as a developer to a few of these. I’d appreciate any additional help from the community to support these plugins, and if you’re aware of somebody who would like to contribute please point them in my direction. https://github.com/pytest-dev/pytest-base-url <https://github.com/pytest-dev/pytest-base-url> - A very small plugin, no commits in over a year https://github.com/pytest-dev/pytest-selenium <https://github.com/pytest-dev/pytest-selenium> - Jim is a developer, and helps out a lot with this one, he's taken care of much of the recent development and responding to issues https://github.com/pytest-dev/pytest-html <https://github.com/pytest-dev/pytest-html> - This is probably the most popular plugin I’ve been maintaining, and I think there’s a lot of potential for enhancements (great ideas already in the tracker) https://github.com/pytest-dev/pytest-metadata <https://github.com/pytest-dev/pytest-metadata> - Split off as a dependency for pytest-html, relatively small plugin and minimal maintenance needs. Jim is a developer for this plugin too https://github.com/pytest-dev/pytest-variables <https://github.com/pytest-dev/pytest-variables> - Another small plugin with very few maintenance needs https://github.com/pytest-dev/pytest-repeat <https://github.com/pytest-dev/pytest-repeat> - I don’t really maintain this one currently, but feel that it’s worth mentioning because I was one of the early contributors I’m happy to answer any questions, and keen to hear any suggestions for handling any handover I’m sure these are in safe hands, and I will continue to use them myself, and promote the use of them to others! Cheers, Dave

5 6