Write them in terms of user requirements. When someone does X, they expect Y to happen. If a test breaks, it should mean that a user somewhere would think there

Write them in terms of user requirements. When someone does X, they expect Y to happen. If a test breaks, it should mean that a user somewhere would think there's a problem. See for instance this: http://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf 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.