Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save bennythejudge/10ecdc88bd3c68665edc7c3b907e062b to your computer and use it in GitHub Desktop.
Save bennythejudge/10ecdc88bd3c68665edc7c3b907e062b to your computer and use it in GitHub Desktop.
O'Reilly Pytest Class

Pytest Introduction

Copyright 2018 - Matt Harrison

@__mharrison__

  • D - Decide
  • R - Relax
  • M - Motivation
  • O - Observe
  • M - Mechanics

Assignment 1

  • Install pytest in a virtual environment
  • Run:

    pytest -h

Assignment 2

  • Create a directory/module Integer/integr.py (note spelling).
    • Create a function, parse, that accepts a string of the form "1,3,5,9" that returns a list of integers ([1, 3, 5, 9])
  • Create a test directory and test file Integer/test/test_integr.py
    • Create a test function, test_basic that asserts that integr.parse works with the input "1,3,5,9"
  • Run pytest on test/test_integr.py

Assignment 3

  • Create a test function, test_bad1 that asserts that an error is raised when integr.parse is called with 'bad input'. Use a context manager (with)
  • Create a test function, test_bad2 that asserts that an error is raised when integr.parse is called with '1-3,12-15'. Use the @pytest.mark.xfail decorator.

Assignment 4

  • Add a __name__ check that will run pytest on test/test_integr.py if it is executed with python
  • Run the command line option to collect the tests (but not execute them).
  • Run only the test_basic test from the command line.

Assignment 5

  • Create a doctest on the integr.py module that shows an example of running the parse function.
  • Run the doctest via pytest with a command line option
  • Create a pytest.ini file. Add an option to the configuration file to run the doctests when pytest is invoked
  • Run the doctest via pytest without a command line option

Assignment 6

  • Run the tests that have bad in the name
  • Mark test_bad1 and test_bad2 with the wrong name.
  • Run only tests that are marked with wrong.
  • Run pytest with --strict
  • Register bad as a marker in pytest.ini
  • Run pytest with --strict
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment