Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #59474 > unrolled thread

Re: Running python's own unit tests?

Started byZachary Ware <zachary.ware+pylist@gmail.com>
First post2013-11-14 14:13 -0600
Last post2013-11-14 14:13 -0600
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Running python's own unit tests? Zachary Ware <zachary.ware+pylist@gmail.com> - 2013-11-14 14:13 -0600

#59474 — Re: Running python's own unit tests?

FromZachary Ware <zachary.ware+pylist@gmail.com>
Date2013-11-14 14:13 -0600
SubjectRe: Running python's own unit tests?
Message-ID<mailman.2621.1384460013.18130.python-list@python.org>
On Thu, Nov 14, 2013 at 1:12 PM, Russell E. Owen <rowen@uw.edu> wrote:
> I'm building python from source and trying to figure out how to test the
> result. I must be overlooking something obvious, but I looked through
> the documentation and source and tried some google searches (which turn
> up plenty about writing unit tests in python, but nothing about testing
> a python distribution).
>
> Any hints?

`python -m test -uall` will test everything (where 'python' invokes
the interpreter you built, which may be "python_d.exe" on Windows if
you built in Debug mode, or "python.exe" on OSX).  If you're testing
2.7, '-m test' needs to be '-m test.regrtest'.

For any further detail, check Tim's link to the devguide, specifically
the chapter on running tests.

-- 
Zach

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web