[
https://issues.apache.org/jira/browse/NUTCH-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059100#comment-18059100
]
ASF GitHub Bot commented on NUTCH-3154:
---------------------------------------
lewismc commented on PR #895:
URL: https://github.com/apache/nutch/pull/895#issuecomment-3915605496
PR updated. i think this is a cleaner implementation. The proposed indexer
integration tests reuse the protocol-test pattern (abstract base in core,
plugins extend and plug in specifics), but use integration tests (real
backends), a separate Ant target, and more configuration via the interface.
I also intentionally chose to NOT include integration tests in the existing
`ant test` execution to retain existing behavior. The CI will take care of
integration testing is any changes are made to the relevant indexer plugins.
> Implement integration testing framework for Nutch IndexWriter plugins using
> Testcontainers
> ------------------------------------------------------------------------------------------
>
> Key: NUTCH-3154
> URL: https://issues.apache.org/jira/browse/NUTCH-3154
> Project: Nutch
> Issue Type: New Feature
> Components: indexer, test
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Major
> Fix For: 1.23
>
>
> I recently came across NUTCH-3003 which reminded me of a stale thought I had
> regarding integration testing for the indexer plugins using
> [https://java.testcontainers.org/. |https://java.testcontainers.org/]
> Such an initiative would deliver a comprehensive integration testing
> framework for Nutch indexer plugins (implementations of IndexWriter
> interface) using Testcontainers. This would enable real-world testing against
> actual database/search engine containers rather than mocking... or nothing
> which is what we currently have.
> *Scope*
> * Add Testcontainers support to Ant build system
> * Configure integration test targets separate from unit tests
> * Enable inegration testing for individual and all indexer plugins
> (elasticsearch, kafka, rabbitmq, solr, opensearch, etc.)
> * Ensure CI/CD compatibility with GitHub Actions
> This ticket will encourage any discussion around this issue. Thanks in
> advance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
