This is the correct way, but in my experience less-traveled programmers start striving for that elusive 100% coverage and end up writing unit tests for completely obvious stuff like constructors (which do nothing else than setting values) or setters/getters.