[
https://issues.apache.org/jira/browse/METRON-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471790#comment-16471790
]
ASF GitHub Bot commented on METRON-1549:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1009
I think this is good. My work on the builder/Processor stuff was a decent
attempt to reduce duplicate code in the integration tests without a total
rethink. I think what we see across the integration tests is so much
commonality that it is apparent that some re-think could be useful to have more
standardize test classes and use cases structured such that there is less
overhead of duplicated code required.
As I have done some work on other projects and seen other approaches this
has only become more clear. commons-vfs for example runs the same tests
against every provider, with each provider providing specialization of it's
suites.
It would seem that we should be able to have a more generic suite or
testing harness for *n* topologies/topics working together, as a next step
refactoring of my prior `Process` work.
I don't think this is the PR for that though
> Add empty object test to WriterBoltIntegrationTest implementation
> -----------------------------------------------------------------
>
> Key: METRON-1549
> URL: https://issues.apache.org/jira/browse/METRON-1549
> Project: Metron
> Issue Type: Test
> Reporter: Michael Miklavcic
> Assignee: Michael Miklavcic
> Priority: Major
>
> Verify expected output when empty objects returned by custom parsers.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
