You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2018/03/08 19:04:00 UTC
[jira] [Updated] (BEAM-3750) Integration test will fail when use
TestPipeline.convertToArgs in some special cases
[ https://issues.apache.org/jira/browse/BEAM-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Cwik updated BEAM-3750:
----------------------------
Priority: Minor (was: Major)
> Integration test will fail when use TestPipeline.convertToArgs in some special cases
> ------------------------------------------------------------------------------------
>
> Key: BEAM-3750
> URL: https://issues.apache.org/jira/browse/BEAM-3750
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Mark Liu
> Assignee: Mark Liu
> Priority: Minor
> Fix For: Not applicable
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> ITs(Integration Tests) are using {{TestPipeline.convertToArgs}} to convert well-defined options to list of pipeline-recognizable arguments and pass them to pipeline main function. A example use case is {{WordCountIT}}([https://github.com/apache/beam/blob/master/examples/java/src/test/java/org/apache/beam/examples/WordCountIT.java#L70]).
> However, incorrect format will be generated by this function if the option that we want to convert has attribute type {{List}}.
> Ideally, we want to get rid of this complicated conversion step in testing which can avoid more problematic cases, but also make integration test better understandable.
> Some discussions happened in [https://github.com/apache/beam/pull/4346.] One possible approach is to extract part of pipeline code so that integration test can reference directly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)