From 691c1470babc0d0bceebb01d4a2f8e803f0a7e2d Mon Sep 17 00:00:00 2001 From: Harmon Date: Wed, 20 Nov 2019 08:12:52 -0600 Subject: [PATCH] Remove duplicate documentation for running tests --- docs/running_tests.rst | 29 ----------------------------- 1 file changed, 29 deletions(-) delete mode 100644 docs/running_tests.rst diff --git a/docs/running_tests.rst b/docs/running_tests.rst deleted file mode 100644 index 3131751..0000000 --- a/docs/running_tests.rst +++ /dev/null @@ -1,29 +0,0 @@ -.. _running_tests: - -************* -Running Tests -************* - -These steps outline how to run tests for Tweepy: - -1. Download Tweepy's source code to a directory. - -2. Install from the downloaded source with the ``test`` extra, e.g. - ``pip install .[test]``. Optionally install the ``dev`` extra as well, for - ``tox`` and ``coverage``, e.g. ``pip install .[dev,test]``. - -3. Run ``python setup.py nosetests`` or simply ``nosetests`` in the source - directory. With the ``dev`` extra, coverage will be shown, and ``tox`` can - also be run to test different Python versions. - -To record new cassettes, the following environment variables can be used: - -``TWITTER_USERNAME`` -``CONSUMER_KEY`` -``CONSUMER_SECRET`` -``ACCESS_KEY`` -``ACCESS_SECRET`` -``USE_REPLAY`` - -Simply set ``USE_REPLAY`` to ``False`` and provide the app and account -credentials and username. -- 2.25.1