TYPO3 Core

I think you got i wrong. The Presentation said:

Method has() in ObjectAccess
For the usage in Fluid, object.property and object.isProperty already support the following methods:
- isProperty() # is isn't working too
- getProperty() # only this works with object.property
New since TYPO3 CMS 7.1: hasProperty()
This calls method $object->hasProperty() if object.hasProperty is used in Fluid

from reading the code (not the presentation) I take these possibilities:

$getterMethodName = 'has' . ucfirst($propertyName);
if (is_callable(array($subject, $getterMethodName))) {
    return $subject->{$getterMethodName}();
}

To me it seems that the propertyName is "test" and the respective getter is build to be "hasTest"

if (substr($methodName, 0, 3) === 'has') {
    $declaredPropertyNames[] = lcfirst(substr($methodName, 3));
}

The other way around.
You go "hasTest" and the code builds (mind the substr) "test" from that.

You need a property declared to be returned by the method. So judging by the example you gave, I guess you missed the property declaration. Try this:

protected $property = TRUE;

protected $anotherProperty = array();

public function isProperty() {
  return $this->property();
}

public function hasAnotherProperty() {
  return $this->anotherProperty();
}

Finally I got the failure here. In fluid, you always request the property, the inner implementation is not known. You do <f:debug>{property}</f:debug> and this is it. The system will find out what kind of getter to call, by simly looking up the provided methods. This is not known and not needed in fluid.

Thx, now i know what Mathias mean. You are both right! I tested it and it works, but it didn't feel right and i think this behavior differs from what is describe in #56529 or what stands in the official TYPO3 CMS 7.1 - What's New presentation.