Unveiling the CNAS Inspection Report for the Special Test of Mobile Apps

In recent years, APP-specific testing has drawn increasing attention. As a CNAS-qualified intermediate service provider, it is crucial to issue a qualified CNAS testing report. Let's focus on APP-specific testing and the testing report below.

Apart from the UI of the APPFunctional testingIn addition to compatibility testing (APP adaptation), security testing, stability testing (monkey), and other types of testing, app-specific testing is also of great concern to many enterprises and individual APP developers. The test content mainly includes power consumption test, data traffic test, weak network test, CPU utilization test, memory utilization test, UI page lag test, response time, experience, and crash probability. Among them, the weak network test mainly simulates the tests of access points of operators such as China Mobile, China Unicom, and China Telecom (requiring the use of actual SIM cards) in weak network environments, including the delay and packet loss of apps on mobile terminals, APP crashes, ANR, and data loss.

Background of the APP-specific testing requirements

Defect Rating description

Fatal: The program fails to run normally or cannot run smoothly, cannot start normally, exits abnormally, crashes, has insufficient resources, enters an infinite loop, crashes or is severely short of resources, etc

Serious: Core functions cannot be completed, function errors occur, data errors, etc., but it will not affect the program's operation

General: Common functional bugs, defects in the product that do not meet product requirements or user usage

UI: Issues related to usability such as inconvenient operation and unreasonable layout

Suggestion: Suggestions for improving and optimizing the product

Analysis of test result data

Do not describe this part in pure text. You can use line charts, pie charts, or bar charts. Visual chart forms are the best choice and the strongest presentation form, which can better highlight the test result data. This is what enterprises and individual APP developers pay more attention to. Strictly speaking, every data report is bound to consist of a large part of text and numbers. But can you guarantee that when submitting such a black paper with white characters and a heavy, gloomy report document, the enterprise leaders can read it calmly despite their busy schedules? Of course, the test report issued also includes screenshots of various interface errors on the mobile phone. But each time, can such random and arbitrary pictures vividly and graphically illustrate the conclusion of the test data? It doesn't matter. We will provide the enterprise with a CNAS inspection report for data visualization.

The problem occurred in the module data statistics

Problem statistics description, risk level assessment, and high-risk areas marked with bright colors

The problem statistics description should have detailed test conditions such as "test equipment", "network", "preconditions", "test steps", "expected results", "actual results", "remarks", "problem screenshots/screenshots", and "reproducibility rate".

Defect conclusion

In the conclusion, the remaining issues, modification suggestions, defect coverage rate, and technical indicators of each special test are analyzed one by one, and reasonable avoidance methods are proposed for the existing risks.