Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m about to embark upon extending and modifying PyUnit.
For instance, I will add warnings to it, in addition to failures.
I’m interested in hearing words of advice on how to start,
for instance, subclass every PyUnit class?
What to avoid and misc caveats.
Looking for input from those that have extended PyUnit already.
I recommend studying the nose project, a popular and well designed extension of PyUnit. You can browse its sources online here or get a copy on your machine via Mercurial, aka
hg, a nice distributed version control system in whichnosekeeps its sources on Google Code Hosting.You may well disagree with some of
nose‘s design decisions, but in general they have executed very well on those decisions, so the sources are worth studying anyway even if you decide that your extension will go in completely different directions.