I will personally not write unit tests for situations where:

1. The code has no branches is trivial. A getter that returns 0 doesn't need tested, and changes will be covered by tests for its consumers.

2. The code simply passes through into a stable API. I'll assume that the standard library works properly.

3. The code needs to interact with other deployed systems; then an integration test is called for.

4. If the test of success/fail is something that is so difficult to quantify as to not be reliably measurable, such as stenography being not noticeable to humans.

5. If the test itself is an order of magnitude more difficult to write than the code.

6. If the code is throw-away or placeholder code. If there's any doubt, test.

I will personally not write unit tests for situations where:

1. The code has no branches is trivial. A getter that returns 0 doesn't need to be tested, and changes will be covered by tests for its consumers.

2. The code simply passes through into a stable API. I'll assume that the standard library works properly.

3. The code needs to interact with other deployed systems; then an integration test is called for.

4. If the test of success/fail is something that is so difficult to quantify as to not be reliably measurable, such as steganography being unnoticeable to humans.

5. If the test itself is an order of magnitude more difficult to write than the code.

6. If the code is throw-away or placeholder code. If there's any doubt, test.

I will personally not write unit tests for situations where:

1. The code has no branches. A getter that returns 0 doesn't need tested, and changes will be covered by tests for its consumers.

2. The code simply passes through into a stable API. I'll assume that the standard library works properly.

3. The code needs to interact with other deployed systems; then an integration test is called for.

4. If the test of success/fail is something that is so difficult to quantify as to not be reliably measurable, such as stenography being not noticeable to humans.

5. If the test itself is an order of magnitude more difficult to write than the code.

6. If the code is throw-away or placeholder code.

I will personally not write unit tests for situations where:

1. The code has no branches is trivial. A getter that returns 0 doesn't need tested, and changes will be covered by tests for its consumers.

2. The code simply passes through into a stable API. I'll assume that the standard library works properly.

3. The code needs to interact with other deployed systems; then an integration test is called for.

4. If the test of success/fail is something that is so difficult to quantify as to not be reliably measurable, such as stenography being not noticeable to humans.

5. If the test itself is an order of magnitude more difficult to write than the code.

6. If the code is throw-away or placeholder code. If there's any doubt, test.