| | |
|---|
| | | |
|---|
| | | $ git clone git://github.com/Pylons/pyramid.git . |
|---|
| | | |
|---|
| | | Alternatively, create a writeable fork on GitHub and check that out. |
|---|
| | | Alternatively, create a writeable fork on GitHub and clone it. |
|---|
| | | |
|---|
| | | Since Pyramid is a framework and not an application, it can be convenient to |
|---|
| | | work against a sample application, preferably in its own virtual environment. A |
|---|
| | |
|---|
| | | - The feature must be documented in both the API and narrative documentation |
|---|
| | | (in ``docs/``). |
|---|
| | | |
|---|
| | | - The feature must work fully on the following CPython versions: 2.7, 3.4, |
|---|
| | | and 3.5 on both UNIX and Windows. |
|---|
| | | - The feature must work fully on the following CPython versions: 2.7, 3.4, 3.5, |
|---|
| | | and 3.6 on both UNIX and Windows. |
|---|
| | | |
|---|
| | | - The feature must work on the latest version of PyPy. |
|---|
| | | |
|---|
| | |
|---|
| | | |
|---|
| | | - PEP8 compliance. Whitespace rules are relaxed: not necessary to put two |
|---|
| | | newlines between classes. But 79-column lines, in particular, are mandatory. |
|---|
| | | See http://docs.pylonsproject.org/en/latest/community/codestyle.html for more |
|---|
| | | See https://docs.pylonsproject.org/en/latest/community/codestyle.html for more |
|---|
| | | information. |
|---|
| | | |
|---|
| | | - Please do not remove trailing whitespace. Configure your editor to reduce |
|---|
| | |
|---|
| | | |
|---|
| | | |
|---|
| | | Running Tests |
|---|
| | | -------------- |
|---|
| | | ------------- |
|---|
| | | |
|---|
| | | - To run all tests for Pyramid on a single Python version from your development |
|---|
| | | virtual environment (See *Using a Development Checkout* above), run |
|---|
| | |
|---|
| | | |
|---|
| | | $ $VENV/bin/nosetests |
|---|
| | | |
|---|
| | | - To run individual tests (i.e., during development) you can use a regular |
|---|
| | | expression with the ``-t`` parameter courtesy of the `nose-selecttests |
|---|
| | | <https://pypi.python.org/pypi/nose-selecttests/>`_ plugin that was installed |
|---|
| | | (along with nose itself) via ``pip install -e .``. The easiest usage is to |
|---|
| | | simply provide the verbatim name of the test you're working on. |
|---|
| | | - To run individual tests (i.e., during development), you can use ``nosetests`` |
|---|
| | | syntax as follows: |
|---|
| | | |
|---|
| | | # run a single test |
|---|
| | | $ $VENV/bin/nosetests pyramid.tests.test_module:ClassName.test_mytestname |
|---|
| | | |
|---|
| | | # run all tests in a class |
|---|
| | | $ $VENV/bin/nosetests pyramid.tests.test_module:ClassName |
|---|
| | | |
|---|
| | | Optionally you can install a nose plugin, `nose-selecttests |
|---|
| | | <https://pypi.org/project/nose-selecttests/>`_, and use a regular |
|---|
| | | expression with the ``-t`` parameter to run tests. |
|---|
| | | |
|---|
| | | # run a single test |
|---|
| | | $ $VENV/bin/nosetests -t test_mytestname |
|---|
| | | |
|---|
| | | - The ``tox.ini`` uses ``nose`` and ``coverage``. As such ``tox`` may be used |
|---|
| | | to run groups of tests or only a specific version of Python. For example, the |
|---|
| | |
|---|
| | | |
|---|
| | | Alternatively: |
|---|
| | | |
|---|
| | | $ tox -e{py27,py34,py35,pypy}-scaffolds, |
|---|
| | | $ tox -e{py27,py34,py35,pypy}-scaffolds |
|---|
| | | |
|---|
| | | |
|---|
| | | Test Coverage |
|---|
