diff --git a/config/testgrids/README.md b/config/testgrids/README.md index fa6d6882989c..b11ca850370f 100644 --- a/config/testgrids/README.md +++ b/config/testgrids/README.md @@ -14,10 +14,8 @@ Any file put in this directory or a subdirectory will be picked up by [testgrid. ## Testing -Run `bazel test //testgrid/...` to ensure the configuration is valid. +Run `bazel test //config/jobs/tests/...` to ensure these configurations are valid. This finds common problems such as malformed yaml, a tab referring to a -non-existent test group, a test group never appearing on any tab, etc. - -Run `bazel test //...` for slightly more advanced testing, such as ensuring that -every job in our CI system appears somewhere in testgrid, etc. \ No newline at end of file +non-existent test group, a test group never appearing on any tab, etc. It also enforces some +repository-specific conventions. \ No newline at end of file diff --git a/testgrid/build_test_update.md b/testgrid/build_test_update.md index ca7a862ae8d7..d1f55452e4a5 100644 --- a/testgrid/build_test_update.md +++ b/testgrid/build_test_update.md @@ -41,8 +41,8 @@ to verify. ## Testing -Run `bazel test //testgrid/...` to run all unit tests in TestGrid. Note that this also validates -the [testgrid.k8s.io config]. +Run `bazel test //testgrid/...` to run all unit tests in TestGrid. Note that this does not validate +the [testgrid.k8s.io config]; those tests are in `bazel test //config/tests/testgrids/...` Run `bazel test //...` for repository-wide testing, such as ensuring that every job in our CI system appears somewhere in testgrid, etc. diff --git a/testgrid/config.md b/testgrid/config.md index d98bb3a99f14..a79c61db0248 100644 --- a/testgrid/config.md +++ b/testgrid/config.md @@ -117,10 +117,7 @@ dashboard_groups: ## Testing your configuration -Run `bazel test //testgrid/...` to ensure the configuration is valid. - -This finds common problems such as malformed yaml, a tab referring to a -non-existent test group, a test group never appearing on any tab, etc. +Run [`bazel test //config/tests/testgrids/..`](/config/tests/testgrids) to ensure the configuration is valid. ## Advanced configuration See [`config.proto`] for an extensive list of configuration options. Here are some commonly-used ones.