Starting March 27, 2025, we recommend using android-latest-release instead of aosp-main to build and contribute to AOSP. For more information, see Changes to AOSP.

ISystemStatusChecker

public interface ISystemStatusChecker

com.android.tradefed.suite.checker.ISystemStatusChecker

Known indirect subclasses

ActivityStatusChecker, DeviceAvailableChecker, DeviceBaselineChecker, DeviceSettingChecker, DeviceStorageStatusChecker, EnforcedSeLinuxChecker, FilesystemRootChecker, KeyguardStatusChecker, LeakedThreadStatusChecker, ShellStatusChecker, SystemServerFileDescriptorChecker, SystemServerStatusChecker, TimeStatusChecker, UserChecker

ActivityStatusChecker	Status checker for left over activities running at the end of a module.
DeviceAvailableChecker	Checker to ensure a module doesn't leave the device in an offline state.
DeviceBaselineChecker	Set device baseline settings before each module.
DeviceSettingChecker	Check if device settings have changed during a module run.
DeviceStorageStatusChecker	Check if device has enough disk space for the given partitions.
EnforcedSeLinuxChecker	Status checker that ensures the status of Selinux.
FilesystemRootChecker
KeyguardStatusChecker	Checks the keyguard status after module execution.
LeakedThreadStatusChecker	Status checker to ensure a module does not leak a running Thread.
ShellStatusChecker	Check if the shell status is as expected before and after a module run.
SystemServerFileDescriptorChecker	Checks if system server appears to be running out of FDs.
SystemServerStatusChecker	Check if the pid of system_server has changed from before and after a module run.
TimeStatusChecker	Status checker to ensure that the device and host time are kept in sync.
UserChecker	Checks if users have changed during the test.

An checker that performs checks on system status and returns a boolean to indicate if the system is in an expected state. Such check maybe performed either prior to or after a module execution.

Note: the checker must be reentrant: meaning that the same instance will be called multiple times for each module executed, so it should not leave a state so as to interfere with the checks to be performed for the following modules.

The return StatusCheckerResult describing the results. May have an error message set in case of failure.

Summary

Public methods
`default StatusCheckerResult`	`postExecutionCheck(ITestDevice device)` Check system condition after test module execution.
`default StatusCheckerResult`	`preExecutionCheck(ITestDevice device)` Check system condition before test module execution.

Public methods

postExecutionCheck

public StatusCheckerResult postExecutionCheck (ITestDevice device)

Check system condition after test module execution. Subclass should override this method if a check is desirable here. Implementation must return a boolean value to indicate if the status check has passed or failed.

Parameters
`device`	`ITestDevice`: The `ITestDevice` on which to run the checks.

Returns
`StatusCheckerResult`	result of system status check

Throws
	com.android.tradefed.device.DeviceNotAvailableException
`DeviceNotAvailableException`

preExecutionCheck

public StatusCheckerResult preExecutionCheck (ITestDevice device)

Check system condition before test module execution. Subclass should override this method if a check is desirable here. Implementation must return a boolean value to indicate if the status check has passed or failed.

It's strongly recommended that system status be checked after module execution, and this method may be used for the purpose of caching certain system state prior to module execution.

Parameters
`device`	`ITestDevice`: The `ITestDevice` on which to run the checks.

Returns
`StatusCheckerResult`	result of system status check

Throws
	com.android.tradefed.device.DeviceNotAvailableException
`DeviceNotAvailableException`