You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Florian Schmidt (JIRA)" <ji...@apache.org> on 2018/03/13 15:17:00 UTC

[jira] [Commented] (FLINK-8937) Refactor flink end-to-end test skeleton

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

Florian Schmidt commented on FLINK-8937:
----------------------------------------

[~aljoscha] any opinions on this?

> Refactor flink end-to-end test skeleton
> ---------------------------------------
>
>                 Key: FLINK-8937
>                 URL: https://issues.apache.org/jira/browse/FLINK-8937
>             Project: Flink
>          Issue Type: Improvement
>          Components: Tests
>            Reporter: Florian Schmidt
>            Assignee: Florian Schmidt
>            Priority: Major
>
> I was thinking about refactoring the end-to-end tests skeleton. The following ideas came to mind:
> - Allow each individual test script to specify some setup and cleanup method that gets executed before and after each test, especially also if that test fails and the EXIT trap is triggered
> - Refactor adding a new test script into a function that provides uniform error handling
> - Add helper methods for common tasks like waiting for a pattern to appear in some log file (e.g. to ensure that a task is running)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)