more details around the testdata directory

6 years ago · 65efc4a52a
parent a474161592
commit 65efc4a52a
2 changed files with 2 additions and 2 deletions
--- a/README.md
+++ b/README.md
@ -90,7 +90,7 @@ IaaS, PaaS, system and container orchestration deployment configurations and tem

 ### `/test`

-Additional external test apps and test data. Feel free to structure the `/test` directory anyway you want. For bigger projects it makes sense to have a data subdirectory (e.g., `/test/data`).
+Additional external test apps and test data. Feel free to structure the `/test` directory anyway you want. For bigger projects it makes sense to have a data subdirectory. For example, you can have `/test/data` or `/test/testdata` if you need Go to ignore what's in that directory. Note that Go will also ignore directories or files that begin with "." or "_", so you have more flexibility in terms of how you name your test data directory.

 See the [`/test`](test/README.md) directory for examples.

--- a/test/README.md
+++ b/test/README.md
@ -1,6 +1,6 @@
 # `/test`

-Additional external test apps and test data. Feel free to structure the `/test` directory anyway you want. For bigger projects it makes sense to have a data subdirectory (e.g., `/test/data`).
+Additional external test apps and test data. Feel free to structure the `/test` directory anyway you want. For bigger projects it makes sense to have a data subdirectory. For example, you can have `/test/data` or `/test/testdata` if you need Go to ignore what's in that directory. Note that Go will also ignore directories or files that begin with "." or "_", so you have more flexibility in terms of how you name your test data directory.

 Examples: