Mercurial > kallithea
changeset 5959:e6fafb5ed70d
docs: make the default method for running tests more visible
Sometimes, users found the convoluted and risky method of testing without
recreating the database before spotting the simple method.
| author | Mads Kiilerich <madski@unity3d.com> |
|---|---|
| date | Fri, 10 Jun 2016 01:19:58 +0200 |
| parents | bf0a587334ea |
| children | 5262c498b3a0 |
| files | docs/contributing.rst |
| diffstat | 1 files changed, 6 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/docs/contributing.rst Fri Jun 10 01:19:58 2016 +0200 +++ b/docs/contributing.rst Fri Jun 10 01:19:58 2016 +0200 @@ -49,8 +49,12 @@ ------------- After finishing your changes make sure all tests pass cleanly. You can run -the testsuite running ``py.test`` from the project root, or if you use tox -run ``tox`` for Python 2.6--2.7 with multiple database test. +the testsuite by running ``py.test`` from the project root:: + + py.test + +You can also use ``tox`` to run the tests with all supported Python versions +(currently Python 2.6--2.7). When running tests, Kallithea uses `kallithea/tests/test.ini` and populates the SQLite database specified there.