VirtualTam's bookmarks: quality

Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)

I'm currently looking for more dev-friendly solutions, the key points being:

writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
complete feature set!
- we don't want to just run tests...
- coverage reports (find dead/weak/untested code sections)
- output formatting (JUnit-XML seems to be quite a common format out there)

There seem to be 3 solutions in Python:

stock unittest + project-dependent customizations / test helpers
nosetests
py.test

And 2 ways of gettings things done:

keeping things stock: no external dependency, project-specific implementation...
using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)

Some links:

Python: run specific unit tests

2015-02-13

bug code programming/functional-programming programming/python programming/testing quality unit

Permalink

Given your unittests are in the tests directory:

 1# run a specific test module
 2python -m unittest tests.<module>
 3 
 4# run a specific test suite
 5python -m unittest tests.<module>.<class>
 6 
 7# run a specific test
 8python -m unittest tests.<module>.<class>.<test>
 9 
10# run tests matching a given pattern
11python -m unittest discover -s tests -p <pattern>