Terminal Application Testing via Embedded Debugging Codes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for testing terminal applications, such as mobile phones, require repeated manual operations when offline, leading to tedious and time-consuming processes, increased testing costs, and lack of portability, especially when using external PCs to simulate click operations.
Innovation Solution
A method and device that implant a test component into the source code of a terminal application, write preset debugging codes, register function addresses, and generate an application test page on the terminal user interface, allowing for automatic testing by calling debugging codes via function addresses in response to client instructions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual clicking operations are used for repeated testing on mobile phone, then testing can be performed offline, but the testing process becomes tedious and time-consuming
Solution Approach 1:
The terminal application performs testing operations autonomously through implanted test components and debugging codes, eliminating the need for manual user intervention. The system automatically executes test scenarios, clicks, and operations based on pre-configured test cases, making the terminal serve itself for testing purposes.
Solution Approach 2:
The patent replaces manual mechanical clicking operations with automated software-based testing mechanisms. Test components and debugging codes substitute human hand operations with automated programmatic control, eliminating the tedious manual interaction while maintaining testing functionality.
2Productivity
If test software is downloaded from external PC to simulate manual click operations, then repeated testing can be automated, but testing cost increases and portability is reduced
Solution Approach 1:
The patent extracts the testing functionality from external PC-based test software and embeds it directly into the terminal application. Test components and debugging codes are integrated within the terminal's own codebase, removing the dependency on external testing systems and reducing overall system complexity.
Solution Approach 2:
The terminal application gains multi-functionality by incorporating testing capabilities directly into its code. The same terminal that runs the application also performs testing functions, eliminating the need for separate dedicated testing devices and reducing system complexity while maintaining automation capability.
3Productivity
If PC-based testing tools are used, then automated testing can be performed, but the tools lack portability
Solution Approach 1:
The patent segments testing functionality into modular test components that can be independently configured and executed. These test components are embedded within the terminal application code, allowing the testing capability to be divided into manageable units that enhance portability while maintaining automated testing functionality.
Solution Approach 2:
The patent merges the testing tool functionality with the terminal application itself. By combining the application code with embedded test components and debugging codes, the system achieves portability since the terminal device carries its own testing capabilities internally, eliminating the need for separate external testing tools.
Data Source
AI summary
Systems, devices and methods are provided for testing a terminal application. For example, a test component is implanted into a source code program of a terminal application to be tested; one or more preset debugging codes are written into the source code program of the terminal application; one or more function addresses of the debugging codes in the source code program of the terminal application are acquired and registered; compiling and executing the source code program; an application test page is generated on a terminal user interface; and in response to a test execution instruction being triggered by a client on the application test page, the debugging codes is called via the function addresses in the test component to test the terminal application.