You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2023/06/21 20:07:00 UTC
[jira] [Created] (NIFI-11737) Refactor FlowSynchronizationIT to avoid restarting the nifi instances between each test
Mark Payne created NIFI-11737:
---------------------------------
Summary: Refactor FlowSynchronizationIT to avoid restarting the nifi instances between each test
Key: NIFI-11737
URL: https://issues.apache.org/jira/browse/NIFI-11737
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework
Reporter: Mark Payne
Assignee: Mark Payne
When the FlowSynchronizationIT was created it had a handful of tests. TO ensure that each of them was starting with a clean slate, we override {{isDestroyEnvironmentAfterEachTest}} to return {{{}true{}}}. However, more tests have been added to this class over time. As a result, the amount of time that the class takes to run has gotten longer and longer. At this point it typically takes over 20 minutes in Github Actions to complete just this one test class.
This is because each of these tests has to start a two-node cluster, wait for both nodes to start, perform the test, and shutdown the nodes. With some slight refactoring of the tests, though, we should be able to avoid shutting down and tearing down the cluster for each test. This should significantly improve the amount of time needed for the tests to run.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)