You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:15 UTC

[jira] [Commented] (BEAM-7697) Provide a way to run tests from Gradle in a unified and reusable way

    [ https://issues.apache.org/jira/browse/BEAM-7697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174692#comment-17174692 ] 

Beam JIRA Bot commented on BEAM-7697:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> Provide a way to run tests from Gradle in a unified and reusable way
> --------------------------------------------------------------------
>
>                 Key: BEAM-7697
>                 URL: https://issues.apache.org/jira/browse/BEAM-7697
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: MichaƂ Walenia
>            Priority: P2
>              Labels: stale-P2
>
> Right now, performance, IO and other tests that make use of SDK Harness are run via a variety of tasks. It makes creating new tasks and trying to reuse code confusing. It would be good to have a parent task that could run any aforementioned test with minimal added configuration. It could reduce code duplication in Gradle task definitions and make it easier to develop new tests and tasks.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)