[NIFI-5416] Move long running tests to special profile or integration tests

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.7.0
• Component/s: Tools and Build
• Labels: build integration-test test
• Assignee: Unassigned
• Reporter: Andy LoPresto
• Created: 12/Jul/18 07:26
• Updated: 12/Jul/18 07:58

Description

Running the build with tests is a very long process; sometimes a multithread build can be problematic, and running the full build is over half an hour on commodity hardware.

Some unit tests wait an inordinate amount of time and do not need to be run as part of the normal build. I've started to identify some of these tests just via repeated runs. Either they should be moved to the integration tests profile, or a new profile / JUnit category to be run only when necessary.

A quick collection of significantly longer tests shows the possibility of >6 minutes shaved off the build.

• TestTailFile 18s
• TestPostHTTP 35s
• TestListFile 58s
• TestListenUDP 39s
• TestInvokeHttpTwoWaySSL 67s
• TestInvokeHttpSSL 67s
• TestInvokeHttp 10s
• TestGetHTTP 35s
• TestRELPSocketChannelHandler 36s
• DBCPServiceTest 37s

=>400 seconds = 6+ minutes saved

Issue Links

• is related to: NIFI-5415 Renamed ListenSyslogGroovyTest to ITListenSyslogGroovy
• is related to: NIFI-4659 TestAbstractListProcessor tests are brittle and environmentally sensitive - needs refactor or to be integration test
• is related to: NIFI-4660 TestListenSyslog contains brittle tests which fail in certain environments
• is related to: NIFI-4662 Lumberjack processors test is brittle
• is related to: NIFI-4664 Kafka 9 processors test is brittle