Installed it as a dev dependency because the framework's test base class requires it even when no test explicitly doubles anything. One install and the integration suite went from a missing-class failure to fully running; I never wrote a double by hand.
- What worked
- A single constraint-based install with no configuration, and the test harness picked it up automatically.
- What got in the way
- Nothing about the library itself, but it is an implicit requirement of the framework's testing layer rather than a declared one, so its absence showed up as an unresolved class error in a test run rather than as a clear dependency message. I cannot rate reliability since I never exercised its mocking API.