[
https://issues.apache.org/jira/browse/NIFI-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021544#comment-16021544
]
ASF subversion and git services commented on NIFI-3903:
-------------------------------------------------------
Commit 9238fdb493fe56704958dc8fc465d109939a994e in nifi's branch
refs/heads/master from [~jameswing]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=9238fdb ]
NIFI-3903 Unit Tests for AWS Processors
* Added non-integration unit tests for Lambda, S3, SNS, and SQS processors
* Moved non-integration tests out of integration test files
* Moved SQS integration tests to IT* files for clarification
Signed-off-by: Pierre Villard <[email protected]>
This closes #1814.
> Basic Unit Test Coverage for AWS Processors
> -------------------------------------------
>
> Key: NIFI-3903
> URL: https://issues.apache.org/jira/browse/NIFI-3903
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: James Wing
> Priority: Minor
>
> Many of the AWS processors rely heavily on integration tests for coverage of
> major features. While there is no substitute for running the code against a
> live AWS environment, the live environment requirement means that integration
> tests are run infrequently. Regular unit tests should be included:
> * Provide coverage of basic features without integration tests
> * Demonstrate at least one mocking pattern for testing AWS request/response
> * Remove excuses for not providing unit tests with new features
> * Clarify integration tests vs. unit tests
> Processors that need help include:
> * InvokeLambda
> * DeleteS3Object, FetchS3Object, PutS3Object, ListS3
> * PutSNS
> * DeleteSQS, GetSQS, PutSQS
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
