This is an automated email from the ASF dual-hosted git repository. mergebot-role pushed a commit to branch mergebot in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit 2c256fdbce6da684d173e955c326197744df47f1 Author: Stephen Sisk <s...@google.com> AuthorDate: Wed Jul 19 13:33:06 2017 -0700 fixup! Add initial text for I/O Integration Test documentation --- src/documentation/io/testing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/documentation/io/testing.md b/src/documentation/io/testing.md index 8846dc1..26ebc55 100644 --- a/src/documentation/io/testing.md +++ b/src/documentation/io/testing.md @@ -112,7 +112,7 @@ If your I/O transform allows batching of reads/writes, you must force the batchi ## I/O Transform Integration Tests {#i-o-transform-integration-tests} -### Goals {#goals} +### Goals {#it-goals} * Allow end to end testing of interactions between data stores, I/O transforms, and runners, simulating real world conditions. * Allow both small scale and large scale testing. @@ -297,8 +297,8 @@ Guidelines for creating a Beam data store Kubernetes script: #### Integrate with PerfKit Benchmarker {#integrate-with-perfkit-benchmarker} To allow developers to easily invoke your I/O integration test, perform the following steps: -1. Create a PerfKit benchmark configuration file for the data store. Each pipeline option needed by the integration test should have a configuration entry. See [Defining I/O test configuration](#defining-the-benchmark-configuration-file) for information about what to include. -1. Modify the pom of the I/O to set the [correct PerfKit parameters](#per-i-o-mvn-pom-configuration). +1. Create a PerfKit benchmark configuration file for the data store. Each pipeline option needed by the integration test should have a configuration entry. See [Defining the benchmark configuration file](#defining-the-benchmark-configuration-file) for information about what to include. +1. Modify the [Per-I/O mvn pom configuration](#per-i-o-mvn-pom-configuration). The goal is that a checked in config has defaults such that other developers can run the test without changing the configuration. -- To stop receiving notification emails like this one, please contact "commits@beam.apache.org" <commits@beam.apache.org>.