beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mergebot-r...@apache.org
Subject [beam-site] 04/05: fixup! fixup! IO Testing, unit tests: update after readthrough
Date Wed, 19 Jul 2017 19:17:26 GMT
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 970991b7d0052244a15a07d409771f3721ca233e
Author: Stephen Sisk <sisk@google.com>
AuthorDate: Wed Jul 19 10:20:59 2017 -0700

    fixup! fixup! IO Testing, unit tests: update after readthrough
---
 src/documentation/io/testing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/documentation/io/testing.md b/src/documentation/io/testing.md
index 924bbe0..adfde04 100644
--- a/src/documentation/io/testing.md
+++ b/src/documentation/io/testing.md
@@ -99,7 +99,7 @@ Instead of using mocks in your unit tests (pre-programming exact responses
to ea
 
 ### Network failure
 
-To help with testing and separation of concerns, **code that interacts across a network should
be handled in a separate class from your I/O transform**. The suggested design pattern is
that your I/O transform throws exceptions once it determines that a read is no longer possible.
+To help with testing and separation of concerns, **code that interacts across a network should
be handled in a separate class from your I/O transform**. The suggested design pattern is
that your I/O transform throws exceptions once it determines that a read or write is no longer
possible.
 
 This allows the I/O transform's unit tests to act as if they have a perfect network connection,
and they do not need to retry/otherwise handle network connection problems.
 

-- 
To stop receiving notification emails like this one, please contact
"commits@beam.apache.org" <commits@beam.apache.org>.

Mime
View raw message