TYPO3 Core

Phew.. two years later.. if I remember correctly its like this:

In extbase you have supportedOptions defined in a Validator

protected $supportedOptions = array(
        'minimum' => array(0, 'The minimum value to accept', 'integer'),
        'maximum' => array(PHP_INT_MAX, 'The maximum value to accept', 'integer'),
        'startRange' => array(0, 'The minimum value to accept', 'integer'),
        'endRange' => array(PHP_INT_MAX, 'The maximum value to accept', 'integer')
    );

If you do not provide all supportedOptions in your validate annotation like here

* @validate NumberRange (endRange = 2)

(minimum, maximum and startRange not provided) all is well in Extbase itself as the supportedOptions will get merged with your given annotation in $this->options -
but in the current tests for this (which are apparently (only?) Unit Tests) $this->options only contains the values from the annotation (so minimum, maximum and startRange would be missing here).

Whether the correct way to test/solve this is to use functionals instead I can't say - I bet you can ;-)

I found this issue when searching for the bug in #72047 and I was wondering why (although this area is covered) the tests did not find the issue of the no longer working startRange/endRange annotation (which was fixed separately in https://review.typo3.org/#/c/45109/)