Add a table explaining which test suites are appropriate for each API surface.
Obviously this is useless in its current form. If anyone knows the answers for the other API surfaces lmk.
PiperOrigin-RevId: 692301217
Change-Id: I9d5c749d95aa961294be66edbeab03393405cb8d
diff --git a/api-guidelines/ndk.md b/api-guidelines/ndk.md
index d91c3b2..04be47b 100644
--- a/api-guidelines/ndk.md
+++ b/api-guidelines/ndk.md
@@ -218,10 +218,18 @@
[apiLevelsMap]: https://cs.android.com/android/_/android/platform/build/soong/+/309a1acb276343be05d103103c7a1ea8570ef4c8:android/api_levels.go;l=275-292;drc=852edc147a4924ba3cce3ec7ff246f29dcf227b8
-### NDK APIs must have CTS tests <a name="compatibilty-cts"></a>
+### APIs must have tests <a name="compatibilty-cts"></a>
-1. All APIs must be covered by the appropriate test suite (e.g. CTS for NDK
- APIs).
+| API surface | Test suite |
+| ----------- | ------------------------------------------------------------- |
+| NDK | CTS |
+| LL-NDK | VTS |
+| APEX | MTS |
+| SystemAPI | CTS (APIs currently only callable via `dlsym()`: b/376759605) |
+| Platform | `cc_test` with `TEST_MAPPING`. Not required, but you wouldn't |
+: : really skip writing tests, would you? :
+
+1. All APIs must be covered by the appropriate test suite. See the table above.
1. Make a best-effort attempt to cover the API behavior thoroughly.
