flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Schmidt (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9020) Move test projects of end-to-end tests in separate modules
Date Mon, 19 Mar 2018 11:09:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-9020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404638#comment-16404638

Florian Schmidt commented on FLINK-9020:

Sure [~kkl0u]
The new structure will look like the following

|-- pom.xml (flink-end-to-end-tests, pom packaging)
|-- some_testcase
|     |
|     |-- pom.xml
|     |-- src/....
|-- another_testcase
|     |
|     |-- pom.xml
|     |-- src/....
|-- test-scripts
|    |
|    |-- run_some_testcase.sh
|    |-- run_another_testcase.sh
|    |-- run_yet_another_testcase.sh (might not need a module, e.g. because it doesn't bring
its own sources)
|-- run_nightly-tests.sh
|-- run-pre-commit-tests.sh

Motivation is that a couple of the examples that I am planning to integrate in the future
use specific ways of packaging, often based on the quickstart example to sketch up a quick
PoC for some test case. In the previous structure we would define a custom way of packing
our jars, whereas now we use the "advertised" way. 

This should lead to 
a.) clearer project structure 
b.) PoCs that are more similar to the way a user would pack its app (instead of having custom

> Move test projects of end-to-end tests in separate modules
> ----------------------------------------------------------
>                 Key: FLINK-9020
>                 URL: https://issues.apache.org/jira/browse/FLINK-9020
>             Project: Flink
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 1.5.0
>            Reporter: Florian Schmidt
>            Assignee: Florian Schmidt
>            Priority: Major
> I would like to propose to move each test case in the end-to-end tests into it's own
module. Reason is that currently we are building all jars for the tests from one pom.xml,
which makes it hard to have specific tests for certain build types (e.g. examples derived
from the flink quickstart archetype).
> For the current state this would mean
> - change packaging from flink-end-to-end-tests from jar to pom
> - refactor the classloader example to be in its own module

This message was sent by Atlassian JIRA

View raw message