Check System Status

System status checkers (SSCs) are defined at the suite-level configuration and
run between each module. They perform checks to determine if the module changed
and didn't restore some given states, for example changing a system property
value.

SSCs are mainly used to ensure that module writers do not forget to clean up
after their tests; but if they do, provide a trace of it so it can be addressed.

A secondary use is to also restore the original state when possible, for
example dismissing the keyguard if it was left open.

Where are they defined in CTS?

How to find checker failures

By default, system checker failures show only in the logs and as bugreports
captured for the invocation with name following the format:
bugreport-checker-post-module-<module name>.zip

This allows you to find out after which module the bugreport was generated.

It is possible to make the system checker report as a test failure itself by
setting the --report-system-checkers option to true. This will result in
a test run showing as failed with the reason for failure being the status
checker particular check.

Content and code samples on this page are subject to the licenses described in the Content License. Java is a registered trademark of Oracle and/or its affiliates.