Commits

Baiju Muthukadan committed d7449b7

include one more step: Clone the pypy repository

Comments (0)

Files changed (1)

How to run lib-python tests.wiki

 == How to run lib-python tests ==
 
-1. get the latest translated PyPy from the [[http://buildbot.pypy.org/nightly/trunk/|nightly build]]
+1. Clone the pypy repository
+{{{
+hg clone https://bitbucket.org/pypy/pypy
+}}}
 
-2. run the failing test from inside a checkout with a pre-built PyPy, e.g.:
+2. get the latest translated PyPy from the [[http://buildbot.pypy.org/nightly/trunk/|nightly build]]
+
+3. run the failing test from inside a clone with a pre-built PyPy, e.g.:
 {{{
 $ ./pypy/test_all.py lib-python/2.7.0/test/test_complex.py --pypy=/path/to/pypy-c
 }}}
 
-3. pick something you think you can fix
+4. pick something you think you can fix
 
-4. add an app level test that highlights the *specific* failure (that will be in somewhere like pypy/objspace/std/test/test_something.py )
+5. add an app level test that highlights the *specific* failure (that will be in somewhere like pypy/objspace/std/test/test_something.py )
 
-5. running app level tests with py.test is fast - so you can see when you fix it. Running the test you have written (on top of CPython) will be a command like:
+6. running app level tests with py.test is fast - so you can see when you fix it. Running the test you have written (on top of CPython) will be a command like:
 {{{
 $ py/bin/py.test pypy/objspace/std/test/test_something.py
 }}}
 
-6. *eventually* run a full translate so you can see that you didn't break pypy and if you really fixed the problem.
+7. *eventually* run a full translate so you can see that you didn't break pypy and if you really fixed the problem.