rfellows commented on PR #9716: URL: https://github.com/apache/nifi/pull/9716#issuecomment-2690715503
> @rfellows the counter to that argument is that it's how the checks work for all other modules currently (i.e. a change runs the tests for everything), and omitting the UI tests comes with risk of things breaking unknowingly > > How about adding the UI tests into the integration or system test workflows, or creating a separate UI test workflow, if adding a little extra time to the standard ci workflow is deemed too much? @ChrisSamo632 It is fair to question this, it just isn't something we've prioritized. I've captured this in a JIRA [1] to get tests turned back on in CI. [1] https://issues.apache.org/jira/browse/NIFI-14302 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
