Git Product home page Git Product logo

ipython_pytest's Introduction

ipython_pytest

This little IPython extension gives you the ability to run tests using Pytest in an IPython Notebook.

Note: There are now better and more actively maintained tools to achieve this. There was also a rejected Pytest feature request for supporting notebooks - see the discussion for interesting details about this challenge:

See also testbook for adding separate unit tests for a notebook.

The motivation for the extension was to make it possible to demonstrate test-driven development using pytest in an IPython notebook driven presentation.

This extension does not attempt to enable using notebooks as test suites. The intention is also not to collect test results from multiple cells, but to do separate test runs for cells in an interactive presentation.

This extension attempts to achieve for pytest what the ipython_nose extension does for nose. Unfortunately it isn't able to inject globals from the notebook environment into the test like the %%nose cell magic in ipython_nose. Instead, in ipython_pytest, all imports, constants and helper functions need to be contained in the test cell itself.

Installation

  • Make sure your IPython Notebook server can import ipython_pytest.py (e.g. copy it to a directory in your PYTHONPATH, or modify PYTHONPATH before starting IPython Notebook). It's also probably sufficient to have ipython_pytest.py in the directory from which you run the notebook, e.g.:

    $ ls
    ipython_pytest.py
    $ ipython notebook
    
  • You can also install it in a virtualenv in development mode:

    $ cd ipython-pytest
    $ pip install -e .
    

Usage

  • Add a cell containing:

    %load_ext ipython_pytest
    

    somewhere in your notebook.

  • Write tests that conform to Pytest conventions, e.g.:

    def test_arithmetic():
        assert 1+1 == 2
    
  • Add a cell consisting of:

    %%pytest
    
    def test_my_stuff():
        assert 42 == 42
    

    to your notebook and run that cell. That will discover your test_* functions, run them, and show console output from Pytest.

  • Pass standard Pytest arguments to the magic:

    %%pytest --tb=short
    

Caveats

  • None of the objects defined in other cells of the notebook are available in the test cell.

Authors

  • Antti Kaihola <antti dot kaihola at wartsila dot com>

Acknowledgements

Thanks to Taavi Burns for the idea in his ipython_nose package.

Get the code

git clone https://github.com/akaihola/ipython_pytest.git

Copyright (c) 2016, 2018, Antti Kaihola.

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

Neither the name of the developers nor the names of contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

ipython_pytest's People

Contributors

akaihola avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

ipython_pytest's Issues

Problem collecting things

I found this plugin from Austin's question on SO http://stackoverflow.com/questions/41304311/running-pytest-test-functions-inside-a-jupyter-notebook

I cloned the repository and then put a symlink to the Python file in . of the Jupyter notebook kernel. I added the %load in a cell and executed it, then executed the cell creating all the data for the tests and then executed the tests. Sadly this last execution failed with:

============================================================================================== test session starts ==============================================================================================
platform linux -- Python 3.5.3, pytest-3.0.6, py-1.4.32, pluggy-0.4.0
benchmark: 3.0.0 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=5.00us max_time=1.00s calibration_precision=10 warmup=False warmup_iterations=100000)
rootdir: /tmp/tmppsvy8zby, inifile: 
plugins: hypothesis-3.6.1, pylint-0.6.0, mock-1.3.0, cov-2.4.0, benchmark-3.0.0
collected 0 items / 1 errors

==================================================================================================== ERRORS =====================================================================================================
________________________________________________________________________________________ ERROR collecting _ipytesttmp.py ________________________________________________________________________________________
_ipytesttmp.py:6: in <module>
    ((a, d, r) for a in algorithms for d, r in dataset))
E   NameError: name 'algorithms' is not defined
============================================================================================ pytest-warning summary =============================================================================================
WP1 None Module already imported so can not be re-written: hypothesis
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 1 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
================================================================================== 1 pytest-warnings, 1 error in 0.26 seconds ===================================================================================

Clearly things appear to start well, but then things go awry. Is it just that all the test code must be in a single cell, that none of the symbols used in a test can be defined in a different cell?

Setting/Emulating nested conftest.py folder structure?

Gret project. I am trying to prototype individual tests without waiting the 15s to spin up our entire app with necessary db connections etc - ours is a large project. It looks like a notebook would be great for this.

How can I get my notebook to behave as if it is in a certain subfolder in our test suite? I need to gain access to all the fixtures in the current folder and all folders above, as pytest normally does. Example:

project_root/tests/conftest.py
project_root/tests/module_a/conftest.py
project_root/tests/module_a/component_1/conftest.py
project_root/tests/module_a/component_1/test_mymethod.py <-- I want my notebook to run as if it's in this folder, inheriting fixtures from all three conftest.py.

How to do that?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.