You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2016/12/20 19:08:58 UTC
[jira] [Resolved] (BEAM-1186) Migrate the remaining tests to use
TestPipeline as a JUnit rule.
[ https://issues.apache.org/jira/browse/BEAM-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles resolved BEAM-1186.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.5.0-incubating
> Migrate the remaining tests to use TestPipeline as a JUnit rule.
> ----------------------------------------------------------------
>
> Key: BEAM-1186
> URL: https://issues.apache.org/jira/browse/BEAM-1186
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Stas Levin
> Assignee: Stas Levin
> Priority: Minor
> Fix For: 0.5.0-incubating
>
>
> Following up on [BEAM-1176|https://issues.apache.org/jira/browse/BEAM-1176], the following tests still have direct calls to {{TestPipeline.create()}}:
> * {{AvroIOGeneratedClassTest#runTestRead}}
> * {{ApproximateUniqueTest#runApproximateUniqueWithDuplicates}}
> * {{ApproximateUniqueTest#runApproximateUniqueWithSkewedDistributions}}
> * {{SampleTest#runPickAnyTest}}
> * {{BigtableIOTest#runReadTest}}
> Consider using [parametrised tests|https://github.com/Pragmatists/junitparams] as suggested by [~lcwik].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)