4 ms·

And what kind of interface do your app have? I'd guess a graphical one or some network endpoints. You should not test code. You should test functionalities. Y

• alanfranz 6y ago
  > You should not test code. You should test functionalities. You're talking about integration tests and/or end-to-end tests. I write those. Usually at the façade level, not at the network endpoint (which usually means the controller level, a shallow layer that often includes some ACL and serialization) but it's just a matter of taste. > You should be able to rewrite all your app in a new language and still be confident your tests will tell you if something broke. "Unit testing" at the class level won't do that. Unit tests, integration tests and e2e tests are different things that solve different concerns. An e2e test will rarely expose an obscure bug within an implementation, and a unit test will rarely expose concerns in the global application flow. Both have their place. And they have nothing to do with the "interface vs not interface", IMHO.