Github user pvillard31 commented on the issue: https://github.com/apache/nifi/pull/2614 To provide more details here: after the release of 1.6.0 (with #2205), we deprecated the use of ``expressionLanguageSupported(boolean)`` in favor of ``expressionLanguageSupported(ExpressionLanguageScope)``. Using the deprecated method does not break anything in the code itself, the only difference is just in the test framework where we are more strict checking if the appropriate scope has been set on the property description. If not, the unit test will fail. Most of the existing opened PRs introducing new properties that support expression language without using the new scope might introduce unit test failures. The only thing required is to update the property with the proper scope. Hope this clarifies things a bit.