Google is committed to advancing racial equity for Black communities. See how.

CTS Testing Guidelines

Follow Fuchsia's best practices.

Test must use the cts_* rule variants found in //sdk/cts/build.

CTS tests target API and ABI available through SDKs. Build support ensures that tests only depend on API elements that are available via an SDK, or allowlisted for use within the CTS. All build targets must use the cts_ rule variants found in //sdk/cts/build instead of the standard fuchsia.git rules (i.e., use cts_fuchsia_component, cts_executable, and so on). The allowlist for non-SDK code can be found in //sdk/cts/build/allowed_cts_deps.gni. Test authors who believe they need an additional inclusion should file a bug in the CTS bug component.

Tests may depend on anything released via the SDK.

Depending on software that is not released via the SDK makes a CTS test more subject to failure due to unrelated changes in Fuchsia platform internals. We make exceptions for dependencies on a case-by-case basis. (e.g., internal test frameworks that would work just as well out of tree).

Test should not have flaky dependencies.

Tests must not depend on things that may go away, are intermittently available or are specific to a particular platform where the test isn't always run. Examples of such things include internet servers and operating system specific filepath.

Tests must be implemented in //sdk/cts/tests.

If this is a concern, please reach out to fuchsia-cts-team@google.com

Tests should serve as examples of how to use an API.

Informally, if an end developer were to see the test, and copy its usage of the API, the test author would believe that developer would be using the API correctly. Tests should, to the extent possible, not depend on undocumented, application-specific invariants. In the future, in the case of widespread use of undocumented usages outside of the Fuchsia tree, we may need to support use cases that do not follow recommended usages.

Tests should not have timeouts.

Instead, timeouts should be enforced by the test infrastructure.

Tests should not be stress or performance tests.

We do not encourage developers to submit stress tests or performance tests to the CTS. Such tests will be examined closely for coverage value.

Tests should target one element of the platform surface area.

CTS tests typically target elements of the platform surface area directly. If one fails, it should be clear which parts of the platform surface area were triggered, and what the changed outcome is. As a result of this rule, typically, the amount of application logic in a test is small.

Tests should not sleep.

Sleeps are common causes of flakiness in tests, as timing can vary wildly between runs depending on target hardware and system load. We recommend that developers structure code so that an explicit signal is sent when a given condition is met, rather than having part of a test wait an arbitrary amount of time for other code to finish.

Tests should avoid mocking or faking the internal state of the target device.

The intent of the CTS is to make sure the entire device behaves correctly, not to make sure that a particular component behaves correctly in isolation.

Tests should exercise edge cases as well as typical inputs and outputs.

Examples include values of 0 and MAXINT for integers, and null pointers for pointer values.

Tests should restore the state of the system when the test has completed.

For example, a test that makes a system-wide change to set the background color of text should reset the color to its original value at the end of the test. This prevents tests from affecting one another.