From 65efc4a52a25f83c2592a320578f1f219e5206e7 Mon Sep 17 00:00:00 2001 From: Kyle Quest Date: Wed, 27 Jun 2018 21:00:58 -0700 Subject: [PATCH] more details around the testdata directory --- README.md | 2 +- test/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1e21fe4..672e3cc 100644 --- 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. diff --git a/test/README.md b/test/README.md index 281f94e..cdcf65f 100644 --- 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: