add missed edits to contributing guide for new tests location

Author: kandersolar

docs/sphinx/source/contributing/testing.rst

@@ -20,13 +20,13 @@ typically more efficient to run and debug the tests in your own local
 environment.
 
 To run the tests locally, install the ``test`` dependencies specified in the
-`setup.py <https://github.com/pvlib/pvlib-python/blob/main/setup.py>`_
+`pyproject.toml <https://github.com/pvlib/pvlib-python/blob/main/pyproject.toml>`_
 file. See :ref:`installation` instructions for more information.
 
 pvlib's unit tests can easily be run by executing ``pytest`` on the
-pvlib directory::
+tests directory::
 
-    pytest pvlib
+    pytest tests
 
 or, for a single module::
 
@@ -39,7 +39,7 @@ or, for a single test::
 We suggest using pytest's ``--pdb`` flag to debug test failures rather
 than using ``print`` or ``logging`` calls. For example::
 
-    pytest pvlib --pdb
+    pytest tests --pdb
 
 will drop you into the
 `pdb debugger <https://docs.python.org/3/library/pdb.html>`_ at the
@@ -50,7 +50,7 @@ to the test suite (with rare exceptions).
 To include all network-dependent tests, include the ``--remote-data`` flag to
 your ``pytest`` call::
 
-    pytest pvlib --remote-data
+    pytest tests --remote-data
 
 And consider adding ``@pytest.mark.remote_data`` to any network dependent test
 you submit for a PR.