Github user JPercivall commented on a diff in the pull request:
    --- Diff: nifi-mock/src/main/java/org/apache/nifi/util/ ---
    @@ -290,4 +291,18 @@ public long getLineageStartIndex() {
         public long getQueueDateIndex() {
             return 0;
    +    public boolean isAttributeEqual(final String attributeName, final 
String expectedValue) {
    +        // unknown attribute name, so cannot be equal.
    +        if (attributes.containsKey(attributeName) == false)
    +            return false;
    +        String value = attributes.get(attributeName);
    +        return Objects.equals(expectedValue, value);
    +    }
    +    public boolean isContentEqual(String excpected) {
    +        final String value = new String(, 
    +        return Objects.equals(excpected, value);
    --- End diff --
    Ah sorry, you are totally right, isContentEqual is perfectly valid.
    Yup, I agree that going with a couple overloaded methods (like 
assertContentEquals does) would be the right way to go.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to