From c1f4c999e8bce7c1d3fb4fcff32190c13666f4cf Mon Sep 17 00:00:00 2001 From: Marcia Ramos Date: Wed, 24 Jul 2019 12:33:08 +0000 Subject: Grammar: "table driven" to "table-driven". --- doc/development/go_guide/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/development/go_guide/index.md b/doc/development/go_guide/index.md index c78f10510b8..9f0ac8cc753 100644 --- a/doc/development/go_guide/index.md +++ b/doc/development/go_guide/index.md @@ -173,9 +173,9 @@ func Test(t *testing.T) { } ``` -### Table Driven Tests +### Table-Driven Tests -Using [Table Driven Tests](https://github.com/golang/go/wiki/TableDrivenTests) +Using [Table-Driven Tests](https://github.com/golang/go/wiki/TableDrivenTests) is generally good practice when you have multiple entries of inputs/outputs for the same function. Below are some guidelines one can follow when writing table-driven test. These guidelines are mostly @@ -206,7 +206,7 @@ to make the test output easily readable. #### Variable names -- Each table driven test map/slice of struct can be named `tests`. +- Each table-driven test map/slice of struct can be named `tests`. - When looping through `tests` the anonymous struct can be referred to as `tt` or `tc`. - The description of the test can be referred to as -- cgit v1.2.1