cybercyst/project-layout
1
0
Fork 0
mirror of https://github.com/golang-standards/project-layout.git synced 2025-05-05 15:43:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

more details around the testdata directory

Browse Source
This commit is contained in:
Kyle Quest 2018-06-27 21:00:58 -07:00
parent a474161592
commit 65efc4a52a
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -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.

2
test/README.md
View File

@ -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: