This is a followup on JBEAP-20356.

In order to make sure there are no undetected problems of the kind described in JBEAP-20356, there should be a mechanism, which will allow for relatively simple testing of properties which have expression-allowed set to true.

Currently, the only known reliable way of testing this, is to write a runtime test per property/small set of properties. Since there are about 2000 properties which are currently set to be resolvable, this is not realistic.