Skip to content

CLN: update test paths in contributing guide #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 10, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions docs/source/contributing.rst
Original file line number Diff line number Diff line change
Expand Up @@ -250,21 +250,22 @@ Running the test suite
The tests can then be run directly inside your Git clone (without having to
install *pandas-gbq*) by typing::

pytest pandas_gbq
pytest tests/unit
pytest tests/system.py

The tests suite is exhaustive and takes around 20 minutes to run. Often it is
worth running only a subset of tests first around your changes before running the
entire suite.

The easiest way to do this is with::

pytest pandas_gbq/path/to/test.py -k regex_matching_test_name
pytest tests/path/to/test.py -k regex_matching_test_name

Or with one of the following constructs::

pytest pandas_gbq/tests/[test-module].py
pytest pandas_gbq/tests/[test-module].py::[TestClass]
pytest pandas_gbq/tests/[test-module].py::[TestClass]::[test_method]
pytest tests/[test-module].py
pytest tests/[test-module].py::[TestClass]
pytest tests/[test-module].py::[TestClass]::[test_method]

For more, see the `pytest <http://doc.pytest.org/en/latest/>`_ documentation.

Expand Down