beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [1/3] beam-site git commit: Reword RunnableOnService to ValidatesRunner
Date Mon, 27 Mar 2017 22:37:07 GMT
Repository: beam-site
Updated Branches:
  refs/heads/asf-site e3423939c -> 0ee032422

Reword RunnableOnService to ValidatesRunner


Branch: refs/heads/asf-site
Commit: 81bafde575cebe7de6a9c083f556d54ff80d3e92
Parents: e342393
Author: Kenneth Knowles <>
Authored: Mon Mar 27 11:36:10 2017 -0700
Committer: Kenneth Knowles <>
Committed: Mon Mar 27 11:36:10 2017 -0700

 src/contribute/ | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/src/contribute/ b/src/contribute/
index ee40a88..868c04c 100644
--- a/src/contribute/
+++ b/src/contribute/
@@ -160,11 +160,11 @@ details on those testing types.
-   <td>E2E Test, <a href="">@RunnableonService</a>
+   <td>E2E Test, <a href="">@ValidatesRunner</a>
    <td><a href="">WordCountIT</a>,
<a href="">ParDoTest</a>
-   <td>E2E, @RunnableonService
+   <td>E2E, @ValidatesRunner
@@ -279,7 +279,7 @@ viewed.
 Running in postcommit removes as stringent of a time constraint, which gives us
 the ability to do some more comprehensive testing. In postcommit we have a test
-suite running the RunnableOnService tests against each supported runner, and
+suite running the ValidatesRunner tests against each supported runner, and
 another for running the full set of E2E tests against each runner.
 Currently-supported runners are Dataflow, Flink, Spark, and Gearpump, with
 others soon to follow. Work is ongoing to enable Flink, Spark, and Gearpump in
@@ -304,9 +304,9 @@ importance of testing, Beam has a robust set of unit tests, as well as
 coverage measurement tools, which protect the codebase from simple to moderate
 breakages. Beam Java unit tests are written in JUnit.
-### RunnableOnService (Working Title)
+### ValidatesRunner (Working Title)
-RunnableOnService tests contain components of both component and end-to-end
+ValidatesRunner tests contain components of both component and end-to-end
 tests. They fulfill the typical purpose of a component test - they are meant to
 test a well-scoped piece of Beam functionality or the interactions between two
 such pieces and can be run in a component-test-type fashion against the
@@ -316,7 +316,7 @@ functionality, but runner functionality as well. They are more lightweight
 a traditional end-to-end test and, because of their well-scoped nature, provide
 good signal as to what exactly is working or broken against a particular runner.
-The name “RunnableOnService” is an artifact of when Beam was still the Google
+The name “ValidatesRunner” is an artifact of when Beam was still the Google
 Cloud Dataflow SDK and [will be
 changing]( to something more
 indicative of its use in the coming months.
@@ -364,9 +364,9 @@ environments. We currently provide the ability to run against the DirectRunner,
 against a local Spark instance, a local Flink instance, and against the Google
 Cloud Dataflow service.
-### RunnableOnService Tests
+### ValidatesRunner Tests
-RunnableOnService tests are tests built to use the Beam TestPipeline class,
+ValidatesRunner tests are tests built to use the Beam TestPipeline class,
 which enables test authors to write simple functionality verification. They are
 meant to use some of the built-in utilities of the SDK, namely PAssert, to
 verify that the simple pipelines they run end in the correct state.
@@ -394,7 +394,7 @@ due to the one of the following scenarios:
 Abandoned node detection is *automatically enabled* when a real pipeline 
 runner (i.e. not a `CrashingRunner`) and/or a 
-`@NeedsRunner` / `@RunnableOnService` annotation are detected. 
+`@NeedsRunner` / `@ValidatesRunner` annotation are detected. 
 Consider the following test:

View raw message