200a14ec66
We write our tests alongside the production code that our tests test, so the current styleguide guidance around using a `test/` subdirectory is a bit confusing. In Chromium we only appear to use this for support code in `testonly` targets, so this CL clarifies that and provides a brief example. R=danakj@chromium.org Bug: N/A Change-Id: I75b7cf5db6338e9cb84ec6af6e2bffd8995eb7f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3041161 Commit-Queue: Dominic Farolino <dom@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#903512}