Show More
@@ -66,6 +66,8 b' the full test suite. You can then run the suite with:' | |||
|
66 | 66 | |
|
67 | 67 | iptest [args] |
|
68 | 68 | |
|
69 | By default, this excludes the relatively slow tests for ``IPython.parallel``. To | |
|
70 | run these, use ``iptest --all``. | |
|
69 | 71 | |
|
70 | 72 | Regardless of how you run things, you should eventually see something like: |
|
71 | 73 | |
@@ -139,6 +141,23 b' point of the error or failure respectively.' | |||
|
139 | 141 | |
|
140 | 142 | and include the resulting information in your query. |
|
141 | 143 | |
|
144 | Testing pull requests | |
|
145 | --------------------- | |
|
146 | ||
|
147 | We have a script that fetches a pull request from Github, merges it with master, | |
|
148 | and runs the test suite on different versions of Python. This uses a separate | |
|
149 | copy of the repository, so you can keep working on the code while it runs. To | |
|
150 | run it:: | |
|
151 | ||
|
152 | python tools/test_pr.py -p 1234 | |
|
153 | ||
|
154 | The number is the pull request number from Github; the ``-p`` flag makes it post | |
|
155 | the results to a comment on the pull request. Any further arguments are passed | |
|
156 | to ``iptest``. | |
|
157 | ||
|
158 | This requires the `requests <http://pypi.python.org/pypi/requests>`_ and | |
|
159 | `keyring <http://pypi.python.org/pypi/keyring>`_ packages. | |
|
160 | ||
|
142 | 161 | For developers: writing tests |
|
143 | 162 | ============================= |
|
144 | 163 |
General Comments 0
You need to be logged in to leave comments.
Login now