Such a situation normally occurs when the unit tests are using shared resources/data in some way.
- It can also happen if your system under test has static fields/properties which are being leveraged to compute the output on which you are asserting.
- It can happen if the system under test is being shared (static) dependencies.