Skip to content

3.1.0

If a test adds some mock or prophecy revelation to the
GeneralUtility::makeInstance() stack using addInstance(),
it is important the test subject actually consumes that
instance. Otherwise, the dangling instance can have
side effects on other tests run afterwards.

The patch adds a test to tearDown() to verifies the
instance stack is empty and lets the test in question
fail with a descriptive message if not.
Assets 2