beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aviem Zur (JIRA)" <>
Subject [jira] [Resolved] (BEAM-1763) TestPipeline should ensure that all assertions succeeded
Date Thu, 04 May 2017 20:53:05 GMT


Aviem Zur resolved BEAM-1763.
    Resolution: Implemented

> TestPipeline should ensure that all assertions succeeded
> --------------------------------------------------------
>                 Key: BEAM-1763
>                 URL:
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-java-core
>            Reporter: Thomas Groh
>            Assignee: Aviem Zur
>             Fix For: First stable release
> 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

View raw message