From 7fd29cb024126de10a90c54427e050e7928c54b4 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Mon, 9 Mar 2020 23:23:49 -0400 Subject: content: make spacing consistent + remove comments Remove repeated blank lines, trailing spaces, trailing blank lines Remove comments from survey2018.article (only article using them). Remove blank lines between successive ".commands". For golang/go#33955. Change-Id: I90cae37a859a8e39549520569d5f10bc455415d3 Reviewed-on: https://go-review.googlesource.com/c/blog/+/222841 Reviewed-by: Ian Lance Taylor --- content/subtests.article | 4 ---- 1 file changed, 4 deletions(-) (limited to 'content/subtests.article') diff --git a/content/subtests.article b/content/subtests.article index 7edbc78..e3c212d 100644 --- a/content/subtests.article +++ b/content/subtests.article @@ -111,8 +111,6 @@ and consistent with the table-driven approach commonly used for testing. Moreover, common setup code is now shared between runs while eliminating the need to reset the timer. - - * Table-driven tests using subtests Go 1.7 also introduces a `Run` method for creating subtests. @@ -169,7 +167,6 @@ identify the test again within the error messages. There are several other benefits to using subtests or sub-benchmarks, as clarified by the following sections. - * Running specific tests or benchmarks Both subtests and sub-benchmarks can be singled out on the command line using @@ -306,7 +303,6 @@ As a result, no other parallel tests can run in parallel to these parallel tests Note that we need to capture the range variable to ensure that `tc` gets bound to the correct instance. - ** Cleaning up after a group of parallel tests In the previous example we used the semantics to wait on a group of parallel -- cgit v1.2.3