Timeline for Is static universally "evil" for unit testing and if so why does Resharper recommend it?
Current License: CC BY-SA 2.5
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 30, 2012 at 3:25 | comment | added | Loren Pechtel | Accessing instance variables inherently means it can't be static. The only state a static method can possibly have is class variables and the only reason that should happen is if you're dealing with a singleton and thus don't have a choice. | |
| Sep 21, 2010 at 15:52 | comment | added | Vaccano | I am referring to when you have a method under test (not static) that calls a static method in another class. That dependency can only be isolated with one the three tools listed above. If you do not isolate it then you are integration testing, not unit testing. | |
| Sep 21, 2010 at 3:38 | history | answered | aqwert | CC BY-SA 2.5 |