http://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste....
You can write integration tests with the same tools as unit tests.
Personally, I try to make sure all major paths are covered, but I won't test every little UI detail. It's faster to test those manually. But YMMV.
2) From the doc [1]:
> Named tuples assign meaning to each position in a tuple and allow for more readable, self-documenting code. They can be used wherever regular tuples are used, and they add the ability to access fields by name instead of position index.
They do act as immutable containers for related data. They are usually used to replace classes that don't have any behavior/methods.
They avoid confusion by having a name, and named attributes.
[1] https://docs.python.org/2/library/collections.html#collectio...
2) `from collections import namedtuple` reinforces 1
3) nice lighweight tests, py.test or nose
4) integration tests so you can actually refactor w/o having to recode 100 unit tests
5) write as little code as possible