summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndroid API Council <no-reply@android.com>2023-10-25 14:37:13 -0700
committerAndroid API Council <copybara-worker@google.com>2023-10-25 14:37:44 -0700
commit8f9e1d05f3f6c72e3b11758046e72973f7e2580b (patch)
tree450cfd6ab7ee8aa9aa9dd0ec3f08134774901b4a
parentb7ccaf290ee65de1f2bb9750ee3faade9c0656c6 (diff)
downloaddocs-8f9e1d05f3f6c72e3b11758046e72973f7e2580b.tar.gz
Clarify the rules about direct testing of the API.
The existing rule covered the case where the C API was covered indirectly by a wrapper, but not the case where the C API was a wrapper around a tested API. PiperOrigin-RevId: 576648062 Change-Id: I01d9ad4802ff6faf9f1e75bbb753772f5fc8e8ed
-rw-r--r--api-guidelines/ndk.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/api-guidelines/ndk.md b/api-guidelines/ndk.md
index 0516467..c71615a 100644
--- a/api-guidelines/ndk.md
+++ b/api-guidelines/ndk.md
@@ -230,7 +230,8 @@ not need any annotations; the guidelines in this section do not apply.
3. Tests must exercise the C APIs themselves, in addition to the C++ wrapper if
one is present. The C API is the interface to the system and needs to work
- as documented, and the C++ wrapper could alter behavior.
+ as documented, and the C++ wrapper could alter behavior. All exposed APIs
+ must be tested directly.
4. Add query APIs if needed to test flag-setting APIs. This is not a strict
requirement, but is preferred without a good reason not to.
@@ -247,7 +248,8 @@ Even
2. Tests must exercise the C APIs themselves, in addition to the C++ wrapper if
one is present. The C API is the interface to the system and needs to work
- as documented, and the C++ wrapper could alter behavior.
+ as documented, and the C++ wrapper could alter behavior. All exposed APIs
+ must be tested directly.
### Prefer new APIs to changing API behavior <a name="behavior-changes"></a>