Unit Testing - What not to test

Question

I have gone through a number posts on stackoverflow and numerous articles about Unit Tests. I am just trying to figure out that what I have understood is right.

Answer 1

Simple Answer - nothing

Complex Answer - you should not test things you do not have the time for. Testing is driven by a complex planning of the needed and affordable tests, prioritized for the most significant parts and workflows of the softwaresystem. The more time is left for testing, the more sidecases can be tested.

In UnitTesting is simply, every unit, in OOP every class has its own test. Test simply everything with values min, max, average usecases and do negativ tests - tests that have to fail if the software works correct. Test errorhandling as well.

See ITSQB for more details on that topic

Answer 2

Wait, by JS you mean JavaScript? I assume you are referring to client side validation then? You should never assume the client validates anything when building a website. JavaScript can be disabled, pages can be altered or faked, etc.

Answer 3

Don't unit test the .NET framework. By that, I mean, don't test things that are Microsoft's responsibility.

For example, don't bother to test setters and getters - unless there is actually code included there.