A good microtest sets up an Interesting Solo Object
and probes the behavior of that
object to determine that it works
the way the programmer wanted it to.
It's just one object, which is interesting (worth testing), and works solo (doesn't rely on others).
Imagine the mechanics needed if the microtest inspected how the object works inside an application.
The application is full
of objects, each with various requirements and collaborations and interactions
which need to be set up in the right way at the right time.
Can you see how NOT testing in isolation would be a problem?
||use this markup:
(Supported languages: java, cpp, csharp, c, python.)
|a method or class name