NIFI-10834 Fixed Flaky Test failing with NonDex

[priyanka-28]

Summary

NIFI-10834
Tests under TestPutSplunkHTTP express non-deterministic behavior as the order of the query parameters in the URL changes. The fix is generating all possible permutations of the query parameter and then checking the generated permutations with the value passed in the 'Assert' function to ensure deterministic behavior.

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• Build completed using mvn clean install -P contrib-check
  • JDK 8
  • JDK 11
  • JDK 17

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[exceptionfactory]

Thanks for the contribution @priyanka-28. Although the proposed changes provide one potential solution, the additional swap and permute methods add some complexity to the unit test class. The check for the path attribute is helpful, but it seems like it would be simpler to just check that the path starts with the expected URL path, instead of attempting to check the entire string. This would avoid the need for the complex string parsing.

[exceptionfactory]

Suggested change

	assertTrue(returnPermuations("/services/collector/raw?sourcetype=test%3Fsource%3Ftype&source=test_source").contains(path.getValue()));
	assertTrue(path.getValue().startsWith("/services/collector/raw"));

[exceptionfactory]

Suggested change

	assertTrue(returnPermuations("/services/collector/raw?host=test_host&index=test_index&sourcetype=test%3Fsource%3Ftype&source=test_source").contains(path.getValue()));
	assertTrue(path.getValue().startsWith("/services/collector/raw"));

[priyanka-28]

Thanks for the contribution @priyanka-28. Although the proposed changes provide one potential solution, the additional swap and permute methods add some complexity to the unit test class. The check for the path attribute is helpful, but it seems like it would be simpler to just check that the path starts with the expected URL path, instead of attempting to check the entire string. This would avoid the need for the complex string parsing.

Thank you for your reply! I have added the updated changes

[exceptionfactory]

Thanks for making the adjustments @priyanka-28, the latest version looks good! +1 merging