[
https://issues.apache.org/jira/browse/FLINK-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017152#comment-16017152
]
ASF GitHub Bot commented on FLINK-6539:
---------------------------------------
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/flink/pull/3911#discussion_r117445440
--- Diff: tools/travis_mvn_watchdog.sh ---
@@ -227,5 +227,15 @@ upload_artifacts_s3
# we are going back to
cd ../../
+# run end-to-end tests
+
+echo "Running automated end-to-end tests"
+
+.test-infa/end-to-end-test/test_batch_wordcount.sh build-target cluster
+E2E_WC_EXIT_CODE=$?
+EXIT_CODE=$(($EXIT_CODE+$?))
+.test-infa/end-to-end-test/test_streaming_kafka010.sh build-target cluster
+EXIT_CODE=$(($EXIT_CODE+$?))
--- End diff --
I like the travis integration a lot
> Add automated end-to-end tests
> ------------------------------
>
> Key: FLINK-6539
> URL: https://issues.apache.org/jira/browse/FLINK-6539
> Project: Flink
> Issue Type: Improvement
> Components: Tests
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
>
> We should add simple tests that exercise all the paths that a user would use
> when starting a cluster and submitting a program. Preferably with a simple
> batch program and a streaming program that uses Kafka.
> This would have catched some of the bugs that we now discovered right before
> the release.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
