[jira] [Updated] (BEAM-655) Rename @RunnableOnService to something more descriptive

["Daniel Halperin (JIRA)" <ji...@apache.org>]

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

Daniel Halperin updated BEAM-655:
---------------------------------
    Component/s: sdk-py
                 sdk-java-core
                 beam-model

> Rename @RunnableOnService to something more descriptive
> -------------------------------------------------------
>
>                 Key: BEAM-655
>                 URL: https://issues.apache.org/jira/browse/BEAM-655
>             Project: Beam
>          Issue Type: Bug
>          Components: beam-model, sdk-java-core, sdk-py
>            Reporter: Jason Kuster
>            Assignee: Mark Liu
>
> There are currently two categories for unit tests in the Core Beam Java SDK: {{NeedsRunner}} and {{RunnableOnService}}. These categories are insufficiently descriptive for describing the tests that they categorize.
> There are two goals for these tests:
> * Demonstrate that a runner conforms with the Beam model and the Capability Matrix. These capabilities are described at [Capability Matrix Testing|https://docs.google.com/document/d/1fICxq32t9yWn9qXhmT07xpclHeHX2VlUyVtpi2WzzGM/edit]
> * Demonstrate that a PTransform, when executed on a {{PipelineRunner}}, performs as specified
> NeedsRunner tests should either:
> * Be converted into a runner-independent test (for example, via use of DoFnTester to test that a DoFn throws on invalid input)
> * Be converted into a RunnableOnService test
> RunnableOnService tests that explicitly test the capabilities of a Model primitive should be categorized into that specific capability. Existing RunnableOnService tests that test the execution of a PTransform should remain RunnableOnService.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)