You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:02 UTC

[jira] [Updated] (BEAM-8941) Create a common place for Load Tests configuration

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

Kenneth Knowles updated BEAM-8941:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Create a common place for Load Tests configuration
> --------------------------------------------------
>
>                 Key: BEAM-8941
>                 URL: https://issues.apache.org/jira/browse/BEAM-8941
>             Project: Beam
>          Issue Type: Sub-task
>          Components: testing
>            Reporter: Kamil Wasilewski
>            Priority: P3
>             Fix For: Not applicable
>
>          Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> The Apache Beam community maintains different versions of each Load Test. For example, right now, there are two versions of all Python Load Tests: the first one runs on Dataflow runner, and the second one runs on Flink. With the lack of a common place where configuration for the tests can be stored, the configuration is duplicated many times with minimal differences.
> The goal is to create a common place for the configuration, so that it could be passed to different files with tests (.test-infra/jenkins/*.groovy) and filtered according to needs.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)