You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Chris Sampson (Jira)" <ji...@apache.org> on 2023/10/08 17:04:00 UTC

[jira] [Created] (NIFI-12190) Fix failing Integration Tests

Chris Sampson created NIFI-12190:
------------------------------------

             Summary: Fix failing Integration Tests
                 Key: NIFI-12190
                 URL: https://issues.apache.org/jira/browse/NIFI-12190
             Project: Apache NiFi
          Issue Type: Epic
            Reporter: Chris Sampson
             Fix For: 2.latest


NIFI-12177 adds an {{integraiton-tests}} GitHub Actions Workflow to regularly run the {{integration-tests}} defined throughout the NiFi repo. However, many tests have had to be skipped from the {{failsafe plugin}} execution due to failures within the GitHub runner.

Typically these are caused by:
* the need for external resources to be setup
* incorrect assertions that might have worked during the original IT creation but have not been updated since
* or missing/incompatible OS resources within the GitHub runner

This Epic is to review the failing ITs within NiFi codebase and either:
* fix them, e.g. correct assertions, and/or by using Testcontainers for hosting external resources, such as for the Elasticsearch Processors
* remove them if no longer useful/cannot be reliably executed on developer's/GitHub runners
* annotate them to be skipped in CI environments if the tests are useful and work on a developer machine but won't be able to work in a CI runner, e.g. a [DisabledIfEnvironmentVariable|https://junit.org/junit5/docs/5.7.0/api/org.junit.jupiter.api/org/junit/jupiter/api/condition/DisabledIfEnvironmentVariable.html] to check whether the `CI` env var is present and set to `true`

Once fixed, the appropriate entry from the {{integration-tests}} Workflow's {{MAVEN_FAILSAFE_SKIP_ITS}} env var **must** be removed



--
This message was sent by Atlassian Jira
(v8.20.10#820010)