I guess it also depends on the nature of tech stack and business domain. For e.g., if you develop a standard CRUD application without much complexity, and use a

I guess it also depends on the nature of tech stack and business domain. For e.g., if you develop a standard CRUD application without much complexity, and use a static lang like Java, you probably need less unit tests. If you use framework features, annotations, validation expressions, then most of the simple data validations (like numbers, dates, future date check, etc) are automatically handled at framework level. In those scenarios, you would generally need a very little unit test case coverage. On the other side, if you use dynamic lang (Ruby, Javascript, etc), or if you are developing a library or framework, then a good coverage for unit tests is a must. I guess the developer's context (whether he/she is developing a framework, library or a simple CRUD app) plays a bigger role.