|
- Get Started — pytest documentation
pytest will run all files of the form test_* py or *_test py in the current directory and its subdirectories More generally, it follows standard test discovery rules
- Full pytest documentation
pytest features in unittest TestCase subclasses Mixing pytest fixtures into unittest TestCase subclasses using marks Using autouse fixtures and accessing other fixtures How to run tests written for nose Usage Supported nose Idioms Unsupported idioms known issues Migrating from nose to pytest How to implement xunit-style set-up Module level
- Usage and Invocations — pytest documentation
Usage and Invocations Calling pytest through python -m pytest ¶ You can invoke testing through the Python interpreter from the command line: python -m pytest [ ] This is almost equivalent to invoking the command line script pytest [ ] directly, except that calling via python will also add the current directory to sys path
- How-to guides - pytest documentation
pytest and other test systems ¶ How to use pytest with an existing test suite How to use unittest -based tests with pytest How to implement xunit-style set-up
- How to invoke pytest
In general, pytest is invoked with the command pytest (see below for other ways to invoke pytest) This will execute all tests in all files whose names follow the form test_* py or \*_test py in the current directory and its subdirectories More generally, pytest follows standard test discovery rules Specifying which tests to run ¶ Pytest supports several ways to run and select tests from
- How to invoke pytest
In general, pytest is invoked with the command pytest (see below for other ways to invoke pytest) This will execute all tests in all files whose names follow the form test_* py or \*_test py in the current directory and its subdirectories More generally, pytest follows standard test discovery rules
- Typing in pytest - pytest documentation
Incorporating typing into pytest tests enhances clarity, improves debugging and maintenance, and ensures type safety These practices lead to a robust, readable, and easily maintainable test suite that is better equipped to handle future changes with minimal risk of errors
|
|
|