py.test reference documentation

• Pytest builtin helpers
  • builtin pytest.* functions and helping objects
  • Builtin function arguments
• Basic test configuration
  • Command line options and configuration file settings
  • How test configuration is read from configuration INI-files
  • How to change command line options defaults
  • Builtin configuration file options
• The writing and reporting of assertions in tests
  • Asserting with the assert statement
  • Assertions about expected exceptions
  • Making use of context-sensitive comparisons
  • Defining your own assertion comparison
  • Advanced assertion introspection
• Injecting objects into test functions (funcargs)
  • Dependency injection through function arguments
  • The funcarg request object
  • Parametrizing multiple calls to a test function
• Extended xUnit style setup fixtures
  • Module level setup/teardown
  • Class level setup/teardown
  • Method and function level setup/teardown
• Capturing of the stdout/stderr output
  • Default stdout/stderr/stdin capturing behaviour
  • Setting capturing methods or disabling capturing
  • Using print statements for debugging
  • Accessing captured output from a test function
• Monkeypatching/mocking modules and environments
  • Simple example: patching os.path.expanduser
  • Method reference of the monkeypatch function argument
• xdist: pytest distributed testing plugin
  • Installation of xdist plugin
  • Usage examples
• Temporary directories and files
  • The ‘tmpdir’ test function argument
  • The default base temporary directory
• Skip and xfail: dealing with tests that can not succeed
  • Marking a test function to be skipped
  • Skip all test functions of a class
  • Mark a test function as expected to fail
  • Evaluation of skipif/xfail expressions
  • Imperative xfail from within a test or setup function
  • Skipping on a missing import dependency
  • Imperative skip from within a test or setup function
• Marking test functions with attributes
  • Marking a single function
  • Marking whole classes or modules
  • Using -k TEXT to select tests
  • API reference for mark related objects
• Asserting deprecation and other warnings.
  • The recwarn function argument
  • Ensuring a function triggers a deprecation warning
• Support for unittest.TestCase
• Running tests written for nose
  • Usage
  • Supported nose Idioms
  • Unsupported idioms / known issues
• Doctest integration for modules and test files