aboutsummaryrefslogtreecommitdiff
path: root/content/subtests.article
diff options
context:
space:
mode:
Diffstat (limited to 'content/subtests.article')
-rw-r--r--content/subtests.article4
1 files changed, 0 insertions, 4 deletions
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