[ https://issues.apache.org/jira/browse/BEAM-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862327#comment-15862327 ]
Stas Levin edited comment on BEAM-298 at 2/11/17 9:23 AM: ---------------------------------------------------------- You're right, test scope seems to fall short since {{TestPipeline}} is part of the production code API. Let me take a deeper look a it. Meanwhile, could you please provide some more info regarding your scenario? Are you running {{TestPipeline}} as part of a unit test or production code on your end? was (Author: staslev): Could you please provide some more info regarding your scenario and how I can reproduce it? Are you running {{TestPipeline}} as part of a unit test or production code? > Make TestPipeline implement the TestRule interface > -------------------------------------------------- > > Key: BEAM-298 > URL: https://issues.apache.org/jira/browse/BEAM-298 > Project: Beam > Issue Type: Improvement > Components: sdk-java-core > Reporter: Thomas Groh > Assignee: Stas Levin > Priority: Minor > Fix For: 0.5.0 > > > https://github.com/junit-team/junit4/wiki/Rules > A JUnit Rule allows a test to use a field annotated with @Rule to wrap > executing tests. Doing so allows the TestPipeline to, at the time the test > completes, assert that all applied transforms have been executed. This > ensures that all unit tests that utilize a TestPipeline rule either are > declared to explicitly not expect to execute or have executed the pipeline. -- This message was sent by Atlassian JIRA (v6.3.15#6346)