---
title: "Comment by Roman Izosimov on \"Unit Tests Done Right\" | Hashnode"
description: "Test Strategy for Example 2 maybe should contain checking that we don&#39;t change any other user&#39;s entity field but only password. But this could mess up t"
url: "https://hashnode.com/posts/unit-tests-done-right/626ef1d7a2d355d4df441063/comment/62bb2af67131dfe7a8b5964b"
---

[Discussion](https://hashnode.com/posts/unit-tests-done-right/626ef1d7a2d355d4df441063)

Comment [Unit Tests Done Right](https://hashnode.com/posts/unit-tests-done-right/626ef1d7a2d355d4df441063)

[Roman Izosimov](https://hashnode.com/@RomanIzosimov)

[Jun 28, 2022](https://hashnode.com/posts/unit-tests-done-right/626ef1d7a2d355d4df441063/comment/62bb2af67131dfe7a8b5964b)

Test Strategy for Example 2 maybe should contain checking that we don't change any other user's entity field but only password. But this could mess up the test. What do you think? What is your assessing path to decide whether include or not anything to test?

[Aleksei Zagoskin](https://hashnode.com/@azagoskin)

[Jul 8, 2022](https://hashnode.com/posts/unit-tests-done-right/626ef1d7a2d355d4df441063/comment/62bb2af67131dfe7a8b5964b#reply-62c86bfce62bf98e0fb06148)

We may consider these things for testing:

1.  Happy path e.g. return value is correct / expected exception gets thrown / messages get published etc.
2.  All if-else-switch branches.
3.  Edge cases such as awkward input parameters (int.MaxValue/MinValue/0, long strings, nulls, empty strings etc).
4.  The order of method calls (e.g. validation goes before we save data to the database).
