Mailing-List: contact commits-help@beam.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.apache.org
Date: Thu, 4 May 2017 20:53:05 +0000 (UTC)
From: "Aviem Zur (JIRA)" <jira@apache.org>
To: commits@beam.apache.org
Message-ID: <JIRA.13057625.1490034657000.130557.1493931185256@Atlassian.JIRA>
In-Reply-To: <JIRA.13057625.1490034657000@Atlassian.JIRA>
References: <JIRA.13057625.1490034657000@Atlassian.JIRA> <JIRA.13057625.1490034657800@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (BEAM-1763) TestPipeline should ensure that all
 assertions succeeded
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 04 May 2017 20:53:12 -0000


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

Aviem Zur resolved BEAM-1763.
-----------------------------
    Resolution: Implemented

> 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
>             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
(v6.3.15#6346)