Deeplight | Google GMS Testing - Introduction to Manual Testing CTS Verifier Test

1. Introduction to CTS Verifier

1.1 CTS Verifier testing is to ensure the compatibility of Android devices with the Android platform. Due to the openness and diversity of the Android system, various manufacturers may customize and modify the Android system, which may lead to compatibility issues when running Android applications on devices. To address these issues, Google has introduced the CTS (Compatibility Test Suite) and CTS Verifier tools to ensure that devices comply with the standards of the Android platform and ensure that applications run smoothly on different Android devices.
 

1.2 Due to the need for a large number of auxiliary test devices and customized UI from different manufacturers during the testing process, CTS Verifier requires manual testing to be completed.

2. Main Testing Modules and Functions of CTS Verifier

2.1Audio
 

Test the audio input and output functions of the device, compatibility testing with 3.5mm headphone jack or USB interface adapter devices. Some issues may be difficult to modify due to the need to simultaneously satisfy subjective and objective effects.
 

2.2 Camera
 

This module tests the camera function of the device, including taking photos, recording videos, etc. Camera ITS requirements are relatively strict and also need to consider camera performance.
 

2.3 Hardware
 

USB interface testing, such as MTP functionality, NFC functionality, screen touch.
 

2.4 Sensors
 

Test all sensor functions of the device, such as accelerometer, gyroscope, etc. If it is a virtual gyroscope, debugging is not easy relying on algorithm simulation.
 

2.5 Connectivity
 

Test the connectivity functions of the device, such as Wi-Fi, Bluetooth, GPS, etc. The basic functions of the prototype can basically meet the testing requirements.

2.6 Managed Provisioning

Mainly test enterprise application functions and multi-user testing, which can allow applications to work independently for individual users. It is easy to encounter problems where the product UI design does not meet the requirements. After completing one project, subsequent projects can basically pass stably.

3. Testing Process

3.1 Select the modules to be tested, then follow the prompts to execute the tests. During the testing process, interaction between the user and the device may be required, such as taking photos, moving the device, etc. After the testing is completed, selecting save will generate a test report displaying the test results.
 

3.2 As some tests may modify permissions, testing does not need to be performed sequentially; the order of testing can be chosen based on experience.

4. Problem Analysis

The test report will not display specific sub-item test failures. Developers can reproduce specific issues based on the test feedback, inspect the reasons for the issues, and proceed with fixes.

5. Necessity of CTS Verifier Testing

5.1 By performing CTS Verifier testing, the functionality of the device can be verified to comply with the specifications of the Android system, checking whether the device‘s camera, sensors, audio, connectivity, and other functions are normal. This ensures stable operation of applications on various devices, reducing compatibility issues encountered by users on different devices.
 

5.2 CTS Verifier testing is also part of GMS certification testing. Certification approval can enhance the market competitiveness of devices.

Feel free to contact us for inquiries about Google GMS testing and certification. We use a combination of automated and manual testing to ensure that devices meet both Android hardware and software standards, thereby achieving Google certification. We can also handle other Google-related projects including EDLA, MADA, Lens, ARCore, TADA, Android Wear, earphones, Google TV, and Android TV.