beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BEAM-1763) TestPipeline should ensure that all assertions succeeded
Date Wed, 26 Apr 2017 18:26:04 GMT

     [ https://issues.apache.org/jira/browse/BEAM-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Davor Bonaci updated BEAM-1763:
-------------------------------
    Fix Version/s: First stable release

> TestPipeline should ensure that all assertions succeeded
> --------------------------------------------------------
>
>                 Key: BEAM-1763
>                 URL: https://issues.apache.org/jira/browse/BEAM-1763
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-java-core
>            Reporter: Thomas Groh
>            Assignee: Aviem Zur
>
> This doesn't need to be part of each {{PipelineRunner}} implementation if it goes through
the {{PipelineResult}} APIs. The assertion can be of the form that if the Pipeline is finished,
then the number of successful assertions is equal to the total number of assertions.
> Suggested solution:
> For runners which support metrics, use the counters for successful/failed assertions
and compare them to expected number of assertions.
> Runners which do not support metrics should either implement metrics or override {{PAssert}}
in a way that verifies its execution.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message