diff options
| author | Treehugger Robot <android-test-infra-autosubmit@system.gserviceaccount.com> | 2023-11-14 12:23:54 +0000 |
|---|---|---|
| committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | 2023-11-14 12:23:54 +0000 |
| commit | 565b7577d581f2cb01e98686e98864d114262298 (patch) | |
| tree | 1e7e6c35d33e098d350d6ef8bb1508ebdc2a6549 | |
| parent | 4dda59a86ebf61202d4208b813a922d9b81e3553 (diff) | |
| parent | f7cbf9d72aad31d262028867e4c644e060493965 (diff) | |
| download | docs-565b7577d581f2cb01e98686e98864d114262298.tar.gz | |
Merge "Link to go/api-test-coverage from go/android-api-guidelines#basics-tested" into main
| -rw-r--r-- | api-guidelines/index.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/api-guidelines/index.md b/api-guidelines/index.md index 0fcfa77..e6fa91a 100644 --- a/api-guidelines/index.md +++ b/api-guidelines/index.md @@ -63,6 +63,9 @@ Testing API surfaces provides a base guarantee that the API surface is usable and we've exposed all the necessary aspects. Testing for existence is not sufficient; the API functionality itself must be tested. +A change that adds a new API should include corresponding CTS tests in the same +Gerrit topic. This is enforced by go/api-test-coverage presubmit. + APIs should also be _testable_. You should be able to answer the question, "How will an app developer test code that uses your API?" |