CN114661581A - Terminal testing method and device, electronic equipment and computer readable storage medium - Google Patents
Terminal testing method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN114661581A CN114661581A CN202210194235.3A CN202210194235A CN114661581A CN 114661581 A CN114661581 A CN 114661581A CN 202210194235 A CN202210194235 A CN 202210194235A CN 114661581 A CN114661581 A CN 114661581A
- Authority
- CN
- China
- Prior art keywords
- test
- factory production
- production subsystem
- program
- starting
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 247
- 238000004519 manufacturing process Methods 0.000 claims abstract description 105
- 238000000034 method Methods 0.000 claims abstract description 80
- 238000012545 processing Methods 0.000 claims abstract description 27
- 238000004590 computer program Methods 0.000 claims description 5
- 238000010998 test method Methods 0.000 claims 5
- 230000006870 function Effects 0.000 abstract description 18
- 238000012423 maintenance Methods 0.000 abstract description 6
- 238000004891 communication Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 239000003795 chemical substances by application Substances 0.000 description 8
- 238000001514 detection method Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000007796 conventional method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 239000011230 binding agent Substances 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a terminal testing method, a terminal testing device, electronic equipment and a computer readable storage medium. The method comprises the steps of firstly obtaining a mode environment variable, starting a first user level process after a kernel program is started, then starting a factory production subsystem when the first user level process judges that the mode environment variable meets a preset factory mode starting condition, processing a received test instruction based on the factory production subsystem to obtain a test result, and finally displaying the test result through an interface display module of the factory production subsystem. According to the method, the factory production subsystem is directly started after the kernel program is started, the android upper frame layer does not need to be started, and the factory production subsystem is used for performing modular testing, so that the factory production efficiency is improved, and the maintenance and the expansion of subsequent functions are facilitated.
Description
Technical Field
The present application relates to the field of automated testing technologies, and in particular, to a terminal testing method and apparatus, an electronic device, and a computer-readable storage medium.
Background
With the development of television terminals, more and more functions are provided. Most of the existing television terminals are based on an android system, and before leaving a factory, in order to ensure stability, reliability and integrity of the television terminals, the television terminals need to test various modules of a machine, such as a screen, a key, an LED lamp, an HDMI data interface, Bluetooth, WIFI and the like.
In the prior art, a method for performing factory testing on a television terminal is to start a whole Android system and then start a corresponding Android Application Package (APK) for testing, however, the disadvantage of this implementation method is that starting the Android system is time-consuming, so that factory production efficiency is not improved.
Therefore, the current terminal testing method has the technical problem of low factory production efficiency, and needs to be improved.
Disclosure of Invention
The application provides a terminal testing method, a terminal testing device, electronic equipment and a computer readable storage medium, which are used for relieving the technical problem that the current terminal testing method is low in factory production efficiency.
In order to solve the technical problem, the present application provides the following technical solutions:
the application provides a terminal testing method, which comprises the following steps:
acquiring a mode environment variable, and starting a first user level process after the kernel program is started;
when the first user-level process judges that the mode environment variable meets a preset factory mode starting condition, a factory production subsystem is started;
processing the received test instruction based on the factory production subsystem to obtain a test result;
and displaying the test result through an interface display module of the factory production subsystem.
Correspondingly, this application still provides a terminal testing arrangement, includes:
the variable acquisition unit is used for acquiring the mode environment variable and starting the first user level process after the kernel program is started;
the subsystem starting unit is used for starting the factory production subsystem when the first user-level process judges that the mode environment variable meets the preset factory mode starting condition;
the test unit is used for processing the received test instruction based on the factory production subsystem to obtain a test result;
and the display unit is used for displaying the test result through an interface display module of the factory production subsystem.
Meanwhile, the application provides an electronic device, which comprises a processor and a memory, wherein the memory is used for storing a computer program, and the processor is used for operating the computer program in the memory so as to execute the steps in the terminal testing method.
In addition, the present application also provides a computer-readable storage medium, where a plurality of instructions are stored in the computer-readable storage medium, and the instructions are suitable for being loaded by a processor to execute the steps in the terminal testing method.
Has the advantages that: the application provides a terminal testing method, a terminal testing device, electronic equipment and a computer readable storage medium. Specifically, the method includes the steps of firstly obtaining a mode environment variable, starting a first user level process after a kernel program is started, then starting a factory production subsystem when the first user level process judges that the mode environment variable meets a preset factory mode starting condition, processing a received test instruction based on the factory production subsystem to obtain a test result, and finally displaying the test result through an interface display module of the factory production subsystem. Compared with the method for testing the APK corresponding to the starting of the whole Andriod system in the current terminal testing method, the method does not need to start the Andriod upper-layer framework layer, shows the testing result through the factory production subsystem, and does not need to walk the Andriod upper-layer framework layer and the virtual machine, so that the factory production efficiency is improved; in addition, the method realizes all functions related to factory production in the factory production subsystem, and is more convenient for maintenance and expansion of subsequent functions compared with the conventional method of passing production tests among different APKs.
Drawings
The technical solutions and other advantages of the present application will become apparent from the following detailed description of specific embodiments of the present application when taken in conjunction with the accompanying drawings.
Fig. 1 is a scene schematic diagram of a terminal test system provided in an embodiment of the present application.
Fig. 2 is a schematic flowchart of a terminal testing method according to an embodiment of the present application.
FIG. 3 is a system framework diagram of a factory production subsystem provided in an embodiment of the present application.
Fig. 4 is an interface schematic diagram of a display interface provided in an embodiment of the present application.
Fig. 5 is a schematic structural diagram of a terminal testing apparatus according to an embodiment of the present application.
Fig. 6 is a schematic structural diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "including" and "having," and any variations thereof, in the description and claims of this application are intended to cover non-exclusive inclusions; the division of the modules presented in this application is only a logical division, and may be implemented in other ways in practical applications, for example, a plurality of modules may be combined or integrated into another system, or some features may be omitted, or not executed.
In this application, the mode environment variable refers to an environment variable factor _ mode in a boot loader (Bootloader) in the starting process of the android system, and the environment variable factor _ mode is customized in the system by a manufacturer. Specifically, the default value of the environment variable factor _ mode in the normal-case user mode is 0, and the value of the environment variable factor _ mode in the factory production mode is 1.
In this application, the kernel program refers to a Linux kernel in the startup process of the Andriod system.
In this application, the first user level process refers to an init process in the starting process of the Andriod system.
In the present application, a plant production subsystem refers to a plant production minimal system (TclFactoryOs) implemented by concentrating all plant production related functions into one system.
The application provides a terminal testing method, a terminal testing device, electronic equipment and a computer readable storage medium.
Referring to fig. 1, fig. 1 is a schematic view of a scenario of a terminal test system provided in the present application, as shown in fig. 1, the terminal test system at least includes a control terminal 101 and a test terminal 102, where:
a communication link is arranged between the control terminal 101 and the test terminal 102 to realize information interaction. The type of communication link may include a wired, wireless communication link, or fiber optic cable, etc., and the application is not limited thereto.
The control terminal 101 may be a PC computer, a smart tablet, a smart phone, or other terminal that can send a test instruction; the test terminal 102 may be a television terminal or the like.
The application provides a terminal test system, which comprises a control terminal 101 and a test terminal 102. Specifically, the test terminal 102 starts a power supply and an android system, then loads a boot program Bootloader, obtains a mode environment variable from the boot program Bootloader, then starts an initial user level process (init process) after the Linux kernel program is started, then judges whether the mode environment variable meets a preset factory mode starting condition through the initial user process, starts a factory production subsystem if the mode environment variable meets the preset factory mode starting condition, then processes a test instruction sent by the control terminal 101 based on the factory production subsystem to obtain a test result, and finally displays the test result through an interface display module of the factory production subsystem.
In the terminal testing process, the testing terminal 102 directly starts the factory production subsystem after the Linux kernel program is started in the starting process of the android system, compared with a method for testing by starting a corresponding APK after the whole android system is started in the current terminal testing method, the method does not need to start an android upper-layer framework layer, the terminal testing system also shows a testing result through the factory production subsystem, and the android upper-layer framework layer and a virtual machine do not need to be run, so that the method improves the factory production efficiency; in addition, the method realizes all functions related to factory production in the factory production subsystem, and is more convenient for maintenance and expansion of subsequent functions compared with the conventional method of passing production tests among different APKs.
It should be noted that the scenario diagram shown in fig. 1 is only an example, and the terminal and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person having ordinary skill in the art knows, with the evolution of the system and the occurrence of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems. The following are detailed below. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.
By combining the scene schematic diagram of the terminal testing system, the following will describe the terminal testing method in the present application in detail, please refer to fig. 2, and fig. 2 is a flowchart of the terminal testing method provided in the embodiment of the present application. The following will describe in detail a terminal testing method in the present application, which includes at least the following steps:
s201: and acquiring a mode environment variable, and starting a first user level process after the kernel program is started.
In an embodiment, a test terminal (Android device) needs to be started first, and the step of starting the Android system includes: after detecting the power supply is started, loading a bootstrap program into a random access memory; running a bootstrap program, acquiring a mode environment variable from the bootstrap program, and searching and loading a kernel program into a memory; starting the kernel program after the boot program is started; and starting the first user level process after the kernel program is started.
Specifically, after the test terminal is powered on, a chip code is guided to be executed from a predefined place (ROM), a bootstrap program Bootloader is searched and loaded into a Random Access Memory (RAM), and the step is designed and realized by a chip manufacturer; then operating a bootstrap program Bootloader, firstly completing initialization of hardware, acquiring mode environment variables from the bootstrap program Bootloader, then finding out a Linux kernel program, and loading the Linux kernel program into a memory, wherein the step is designed and realized by a device manufacturer; then, a Linux kernel is started, various software and hardware environments are initialized, a driver is loaded, a root file system is mounted, and a first user level process (init process) is executed, so that the world of Android is started.
The mode environment variable refers to an environment variable factor _ mode in a boot loader (Bootloader) in the starting process of the android system, and the environment variable factor _ mode is customized in the system by a manufacturer.
S202: and when the first user level process judges that the mode environment variable meets the preset factory mode starting condition, starting the factory production subsystem.
Since the default value of the mode environment variable factor _ mode is 0 in the normal case user mode, the value of the mode environment variable factor _ mode is 1 in the factory production mode. Therefore, in the starting process, if the value of the mode environment variable factor _ mode at the moment is judged to be 1 by the first user level process (init process), the preset factory mode starting condition is met, and the factory production subsystem can be started.
As shown in fig. 3, fig. 3 is a schematic diagram of a framework of a factory production subsystem according to an embodiment of the present application. This plant production subsystem, which may be referred to as a plant production minimal system (TclFactoryOs), essentially comprises: the test tool runs at the PC end, and can send a test instruction to the test terminal through the serial port; serial port data processing module (serial) for receiving command sent from PC end; a parse configuration file module (config) for parsing a configuration file (e.g., mmi.xml/main.xml); the hardware platform configuration module (board) is used for configuring different hardware platform characteristics, particularly different hardware platform board configurations mainly configure a chip ID and a software platform version, wherein the chip ID is used for distinguishing different hardware platforms, the related underlying test logics of the different hardware platforms are not very same (related to chip manufacturers), the software versions of Linux kernels of the different platforms are different, interfaces of the Linux kernels of the different versions are also different, and programs are subjected to differential adaptation through the different software versions; the interface drawing module (draw) can call a libmmi library to draw a display interface, wherein the libmmi library is used for packaging specific implementation of UI controls (such as Button, TextView, ListView and the like), and can call an open source graph drawing library such as libEGL/libGLESv2/libski and the like; an input event processing module (input) which is mainly used for processing input events such as remote controller keys and the like, and performing event scanning through nodes of bottom layer input events such as scanning/dev/eventX and the like (such as key events, touch screen events and the like); a factory test management module (module) which mainly manages a factory test module (such as a system information display test module, a key test module, an LED lamp test module lamp and the like); and a factory test agent module (tclfactoryaagent), all factory test modules (e.g., a system information display test module, a key test module, an LED lamp test module lamp, etc.) communicate through the factory test agent module (tclfactoryaagent) and a factory test management module (module) in a factory production minimum system (tclfactoryas), wherein the communication is mainly performed through a communication interface (Socket).
As can be seen from the above, the system start-up procedure of the present application is as follows: after the test terminal is powered on, a bootstrap program Bootloader is started, then a Linux kernel program is started, then a first user level process (init process) is started, finally a factory production subsystem (TclFactoryOs) is directly started, and a related test target of the test terminal is tested through each module in the factory production subsystem; the system starting process in the prior art is as follows: the method comprises the steps of starting a bootstrap Bootloader after a test terminal is powered on, then starting a Linux kernel program, then starting a first user level process (init process), then starting a Zygote process, creating a java virtual machine and registering a JNI method for the java virtual machine, creating a server Socket, starting a SystemServer process, then starting a Binder thread pool and a SystemServiceManager, starting various system services, and finally starting a laucher. The system starting in the prior art mainly relates to a system layer (Boot), a Linux kernel layer, an Android framework layer and an APP application layer, compared with the prior art, the Android framework layer is saved in starting, and time is consumed for starting the Android framework layer, so that the factory testing efficiency is improved, and the factory production efficiency is also improved.
S203: and processing the received test instruction based on the factory production subsystem to obtain a test result.
Compared with the prior art that the test is carried out through the APK corresponding to the test target, the test target is tested through each test module in the factory production subsystem, the agent design mode of the test target is embodied, and decoupling and modularization tests are achieved.
In one embodiment, before receiving the test instruction, the initial display interface needs to be drawn, and the specific steps include: acquiring and analyzing an initial interface display configuration file from a factory production subsystem, wherein the initial interface display configuration file comprises an initial menu item display configuration file and an initial interface layout file; and drawing and displaying the initial display interface according to the initial interface display configuration file.
Specifically, an initial interface display configuration file is obtained through the configuration file analysis module config, and is analyzed, wherein the initial menu item display configuration file is, for example, mmi. The menu item display configuration file aims to realize adding and deleting display items or changing the picture font size of the display items directly by modifying an mmi.xml file without modifying codes, so that subsequent maintenance is facilitated; and the purpose of the interface layout file is to perform the layout of the display interface.
Finally, an initial display interface is drawn through an interface drawing module in the factory production subsystem based on the analyzed initial interface display configuration file, as shown in fig. 4, fig. 4 is an interface schematic diagram of the display interface provided by the embodiment of the present application. Fig. 4 shows menu items such as system information, LED test, key test, WIFI test, and button layouts such as start of full test, reset, restart, and test report, and by triggering a certain menu item or button, a display interface corresponding to the menu item may be skipped.
In one embodiment, the specific steps of processing the received test instruction include: receiving a test instruction through a factory production subsystem, and determining a test target according to the test instruction; and calling a test program matched with the test target through the factory production subsystem, and testing the test object through the test program to obtain a test result. The test target comprises an LED lamp, a key, system information display and the like.
Specifically, after a serial port data processing module is called to initialize a serial port, serial port data sent by a PC (personal computer) terminal is received through the serial port, when a test tool at the PC terminal sends a test instruction, the test instruction is transmitted to a serial port data processing module in a factory production subsystem through the serial port, and further, the test instruction is analyzed through the serial port data processing module to determine a corresponding test target; then, the factory production subsystem calls a test program matched with the test target, and the test object is tested by the test program to obtain a test result, wherein how to call is described below.
Preferably, before the test target is determined, the test may be triggered by clicking a corresponding control in the initial display interface, and the specific steps include: acquiring bottom layer input event data through an input event processing module in a factory production subsystem; analyzing the bottom input event data, and sending a test instruction when the bottom input event data represents the trigger test. The method comprises the steps that corresponding controls and buttons are arranged in an initial display interface, the corresponding controls can be triggered in a remote controller/touch screen mode, so that a corresponding process is skipped, specifically, if an LED test menu item is triggered in the remote controller/touch screen mode, an input event processing module of a factory production subsystem can acquire remote controller key data by monitoring bottom layer input event data, then the remote controller key data at the moment is analyzed through the input event processing module, the data is used for triggering an LED test, and therefore a test instruction is sent out to enable a test module in the factory production subsystem to work correspondingly. Besides, the concurrent testing of all testing targets can be realized by triggering a button of starting full testing. It should be noted that the display interface can be operated by a remote controller/a touch screen or the like.
In one embodiment, the specific steps of testing the test target include: calling a test program matched with a test target through a factory test management module in a factory production subsystem; loading a test program to a test module through a factory test agent module of a factory production subsystem; and starting a test program through the test module to test the test target to obtain a test result.
When the factory production subsystem is started, each module of the factory production subsystem is initialized, wherein the initialization operation comprises calling a factory test management module to output corresponding programs (system information display, LED lamps, keys and the like) for each test module fork (a system call in a Linux system, a program can be created through the system call), creating a communication interface Socket, and communicating with a factory test agent module through the Socket. When testing the target, directly through the factory test management module in the factory production subsystem call with test target matching test program (if the test target is the button, directly call the button test program), then through the factory test module with test program load to the button test module, through the button test module start button test program to the button test, obtain the test result.
The factory test agent module is mainly used for decoupling the test program from the main program, each test target can be independently operated and tested through the corresponding test module, and multiple test targets can be concurrently tested.
S204: and displaying the test result through an interface display module of the factory production subsystem.
In one embodiment, the test result data of different test modules is sent to the factory production subsystem through the factory test agent module, and the test result is displayed through the interface drawing module, which includes the following steps: calling a graphic drawing control library through an interface drawing module of a factory production subsystem; drawing a first display interface according to the graphic drawing control library and the test result; and displaying the test result based on the first display interface. The graphic drawing control library is mainly an open source graphic drawing library such as libEGL/libGLESv2/libski, and the like, and the graphic drawing control library is used for realizing image drawing operation and displaying feedback of a test result.
It should be noted that, drawing the graph of the present application is directly performed through the bottom libEGL library without going through an Android frame layer and a virtual machine, so that the image interface display speed is faster, and the subsequent development and maintenance are facilitated.
According to the terminal testing method, after the Linux kernel program is started in the Android system starting process, the factory testing program is directly started, and the Android upper Framework layer (including an Android Native layer system library, an Android Framework, an Android virtual machine and an APP application layer) is not started. The method is implemented on the MTP221 Android platform scheme, the factory production mode can be entered in about 18s, the production mode needs 50s when the method is started in the prior art, the starting time of the method is improved by 64% compared with that of the method in the prior art, and the factory production efficiency can be greatly improved. Meanwhile, the functions related to factory production are realized in the factory production subsystem, and compared with the conventional production test among different APKs, the method and the system are more convenient for subsequent function expansion and maintenance.
Based on the content of the foregoing embodiments, an embodiment of the present application provides a terminal testing apparatus, where the terminal testing apparatus is configured to execute a terminal testing method provided in the foregoing method embodiments, and specifically, please refer to fig. 5, the apparatus includes:
a variable acquiring unit 501, configured to acquire a mode environment variable, and start a first user-level process after the kernel program is started;
a subsystem starting unit 502, configured to start a factory production subsystem when the first user-level process determines that the mode environment variable meets a preset factory mode starting condition;
the test unit 503 is configured to process the received test instruction based on the factory production subsystem to obtain a test result;
a display unit 504, configured to display the test result through an interface display module of the factory production subsystem.
In one embodiment, the variable acquiring unit 501 includes:
a program loading unit for loading a boot program into the random access memory after detecting power startup;
the variable acquisition subunit is used for operating the bootstrap program, acquiring a mode environment variable from the bootstrap program, and searching and loading a kernel program into a memory;
the first starting unit is used for starting the kernel program after the boot program is started;
and the second starting unit is used for starting the first user level process after the kernel program is started.
In one embodiment, the terminal test apparatus further comprises:
the system comprises a file analyzing unit, a display unit and a display unit, wherein the file analyzing unit is used for acquiring and analyzing an initial interface display configuration file from a factory production subsystem, and the initial interface display configuration file comprises an initial menu item display configuration file and an initial interface layout file;
and the drawing unit is used for drawing and displaying the initial display interface according to the initial interface display configuration file.
In one embodiment, the test unit 503 includes:
the target determining unit is used for receiving a test instruction through the factory production subsystem and determining a test target according to the test instruction;
and the test program calling unit is used for calling the test program matched with the test target through the factory production subsystem and testing the test target through the test program to obtain a test result.
In one embodiment, the terminal test apparatus further comprises:
the second acquisition unit is used for acquiring bottom layer input event data through an input event processing module in the factory production subsystem;
and the data analysis unit is used for analyzing the bottom layer input event data and sending a test instruction when the bottom layer input event data represents the trigger test.
In one embodiment, the test program calling unit includes:
a program calling subunit, configured to call, through a factory test management module in the factory production subsystem, a test program matched with the test target;
a program loading subunit, configured to load the test program to a test module through a factory test agent module of the factory production subsystem;
and the program starting unit is used for starting the test program to test the test target through the test module to obtain a test result.
In one embodiment, the presentation unit 504 comprises:
the control library calling unit is used for calling a graphic drawing control library through an interface drawing module of the factory production subsystem;
the interface drawing subunit is used for drawing a first display interface according to the graphic drawing control library and the test result;
and the result display unit is used for displaying the test result based on the first display interface.
The terminal testing apparatus of the embodiment of the present application may be configured to implement the technical solutions of the foregoing method embodiments, and the implementation principle and the technical effects are similar, which are not described herein again.
Different from the current technology, the terminal testing device provided by the application is provided with the subsystem starting unit, the factory production subsystem is directly started after the kernel program is started in the starting process of the Andriod system through the subsystem starting unit, and compared with a method for testing the APK corresponding to the starting of the entire Andriod system in the current terminal testing method, the method does not need to start the Andriod upper framework layer, the starting of the Andriod upper framework layer is time-consuming, and the factory production efficiency is improved.
Accordingly, an electronic device may include, as shown in fig. 6, a processor 601 having one or more processing cores, a Wireless Fidelity (WiFi) module 602, a memory 603 having one or more computer-readable storage media, an audio circuit 604, a display unit 605, an input unit 606, a sensor 607, a power supply 608, and a Radio Frequency (RF) circuit 609. Those skilled in the art will appreciate that the configuration of the electronic device shown in fig. 6 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:
the processor 601 is a control center of the electronic device, connects various parts of the whole electronic device by using various interfaces and lines, and performs various functions of the electronic device and processes data by running or executing software programs and/or modules stored in the memory 603 and calling data stored in the memory 603, thereby performing overall monitoring of the electronic device. In one embodiment, processor 601 may include one or more processing cores; preferably, the processor 601 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 601.
WiFi belongs to short-range wireless transmission technology, and the electronic device can help the user send and receive e-mail, browse web pages, access streaming media, etc. through the wireless module 602, and it provides wireless broadband internet access for the user. Although fig. 6 shows the wireless module 602, it is understood that it does not belong to the essential constitution of the terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The memory 603 may be used to store software programs and modules, and the processor 601 executes various functional applications and data processing by running the computer programs and modules stored in the memory 603. The memory 603 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the terminal, etc. Further, the memory 603 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 603 may also include a memory controller to provide the processor 601 and the input unit 606 access to the memory 603.
The audio circuitry 604 includes speakers that can provide an audio interface between the user and the electronic device. The audio circuit 604 may transmit the electrical signal converted from the received audio data to a speaker, and convert the electrical signal into a sound signal for output; on the other hand, the speaker converts the collected sound signal into an electrical signal, which is received by the audio circuit 604 and converted into audio data, and the audio data is processed by the audio data output processor 601 and then transmitted to another electronic device through the radio frequency circuit 609, or the audio data is output to the memory 603 for further processing. The audio circuit 604 may also include an earbud jack to provide communication of peripheral headphones with the electronic device.
The display unit 605 may be used to display information input by or provided to the user and various graphical user interfaces of the terminal, which may be configured by graphics, text, icons, video, and any combination thereof. The Display unit 605 may include a Display panel, and in one embodiment, the Display panel may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The input unit 606 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control. Specifically, in one particular embodiment, input unit 606 may include a touch-sensitive surface as well as other input devices. The touch-sensitive surface, also referred to as a touch display screen or a touch pad, may collect touch operations by a user (e.g., operations by a user on or near the touch-sensitive surface using a finger, a stylus, or any other suitable object or attachment) thereon or nearby, and drive the corresponding connection device according to a predetermined program. In one embodiment, the touch sensitive surface may comprise two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 601, and can receive and execute commands sent by the processor 601. In addition, the touch sensitive surface can be implemented in various types, such as resistive, capacitive, infrared, and surface acoustic wave. The input unit 606 may include other input devices in addition to a touch-sensitive surface. In particular, other input devices may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The electronic device may also include at least one sensor 607, such as an infrared sensor, a light sensor, and other sensors. As for other sensors such as a gyroscope, a barometer, a hygrometer and a thermometer, which can be configured by the electronic device, detailed description is omitted here.
The electronic device also includes a power supply 608 (e.g., a battery) for powering the various components, which may be logically coupled to the processor 601 via a power management system to manage charging, discharging, and power consumption management functions via the power management system. The power supply 608 may also include any component including one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
The radio frequency circuit 609 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, receives downlink information of a base station and then sends the received downlink information to one or more processors 601 for processing; in addition, data relating to uplink is transmitted to the base station. In general, the radio frequency circuitry 609 includes, but is not limited to, an antenna, at least one Amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the radio 609 may also communicate with networks and other devices via wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), and the like.
Although not shown, the electronic device may further include a camera, a bluetooth module, and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 601 in the electronic device loads the executable file corresponding to the process of one or more application programs into the memory 603 according to the following instructions, and the processor 601 runs the application program stored in the memory 603, so as to implement the following functions:
acquiring a mode environment variable, and starting a first user level process after the kernel program is started;
when the first user-level process judges that the mode environment variable meets a preset factory mode starting condition, a factory production subsystem is started;
processing the received test instruction based on the factory production subsystem to obtain a test result;
and displaying the test result through an interface display module of the factory production subsystem.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, where the instructions can be loaded by a processor to implement the functions of the above system performance auxiliary analysis method.
Wherein the computer-readable storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
The terminal testing method, the terminal testing device, the electronic device, and the computer-readable storage medium provided in the embodiments of the present application are described in detail above, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiments is only used to help understanding the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A method for testing a terminal, comprising:
acquiring a mode environment variable, and starting a first user level process after the kernel program is started;
when the first user-level process judges that the mode environment variable meets a preset factory mode starting condition, a factory production subsystem is started;
processing the received test instruction based on the factory production subsystem to obtain a test result;
and displaying the test result through an interface display module of the factory production subsystem.
2. The terminal test method according to claim 1, wherein the step of acquiring the mode environment variable and starting the first user level process after the kernel program is started comprises:
loading a boot program into the random access memory upon detecting a power start;
running the bootstrap program, acquiring a mode environment variable from the bootstrap program, and searching and loading a kernel program into a memory;
starting the kernel program after the boot program is started;
and starting the first user level process after the kernel program is started.
3. The terminal testing method of claim 1, further comprising, before the step of processing the received test command based on the factory production subsystem to obtain the test result:
acquiring and analyzing an initial interface display configuration file from the factory production subsystem, wherein the initial interface display configuration file comprises an initial menu item display configuration file and an initial interface layout file;
and drawing and displaying an initial display interface according to the initial interface display configuration file.
4. The terminal testing method of claim 1, wherein the step of processing the received testing instructions based on the factory production subsystem to obtain the testing result comprises:
receiving a test instruction through the factory production subsystem, and determining a test target according to the test instruction;
and calling a test program matched with the test target through the factory production subsystem, and testing the test target through the test program to obtain a test result.
5. The terminal test method of claim 4, further comprising, prior to the step of receiving a test command by the factory production subsystem and determining a test target based on the test command:
acquiring bottom layer input event data through an input event processing module in the factory production subsystem;
and analyzing the bottom layer input event data, and sending a test instruction when the bottom layer input event data represents the trigger test.
6. The terminal test method according to claim 4, wherein the step of calling a test program matching the test target through the factory production subsystem and testing the test target through the test program to obtain a test result comprises:
calling a test program matched with the test target through a factory test management module in the factory production subsystem;
loading, by a factory test agent module of the factory production subsystem, the test program to a test module;
and starting the test program to test the test target through the test module to obtain a test result.
7. The terminal testing method of claim 1, wherein the step of displaying the test result through the interface display module of the factory production subsystem comprises:
calling a graphic drawing control library through an interface drawing module of the factory production subsystem;
drawing a first display interface according to the graphic drawing control library and the test result;
and displaying the test result based on the first display interface.
8. A terminal testing device, comprising:
the variable acquisition unit is used for acquiring the mode environment variable and starting the first user level process after the kernel program is started;
the subsystem starting unit is used for starting a factory production subsystem when the first user-level process judges that the mode environment variable meets a preset factory mode starting condition;
the test unit is used for processing the received test instruction based on the factory production subsystem to obtain a test result;
and the display unit is used for displaying the test result through an interface display module of the factory production subsystem.
9. An electronic device comprising a processor and a memory, the memory being configured to store a computer program, the processor being configured to execute the computer program in the memory to perform the steps of the method of testing a terminal as claimed in any one of claims 1 to 7.
10. A computer readable storage medium storing instructions adapted to be loaded by a processor to perform the steps of the method of testing a terminal according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210194235.3A CN114661581A (en) | 2022-03-01 | 2022-03-01 | Terminal testing method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210194235.3A CN114661581A (en) | 2022-03-01 | 2022-03-01 | Terminal testing method and device, electronic equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114661581A true CN114661581A (en) | 2022-06-24 |
Family
ID=82027882
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210194235.3A Pending CN114661581A (en) | 2022-03-01 | 2022-03-01 | Terminal testing method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114661581A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116610511A (en) * | 2023-07-18 | 2023-08-18 | 合肥康芯威存储技术有限公司 | Storage test equipment and test method thereof |
| CN116734903A (en) * | 2022-10-20 | 2023-09-12 | 荣耀终端有限公司 | Test method and device |
-
2022
- 2022-03-01 CN CN202210194235.3A patent/CN114661581A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116734903A (en) * | 2022-10-20 | 2023-09-12 | 荣耀终端有限公司 | Test method and device |
| CN116734903B (en) * | 2022-10-20 | 2024-05-14 | 荣耀终端有限公司 | Test method and device |
| CN116610511A (en) * | 2023-07-18 | 2023-08-18 | 合肥康芯威存储技术有限公司 | Storage test equipment and test method thereof |
| CN116610511B (en) * | 2023-07-18 | 2024-04-05 | 合肥康芯威存储技术有限公司 | Storage test equipment and test method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108536594B (en) | Page testing method and device and storage equipment | |
| CN106502906B (en) | A kind of method and apparatus of test application program | |
| CN111142711B (en) | Firmware configuration method and device, storage medium and mobile terminal | |
| WO2018077041A1 (en) | Method and apparatus for running application | |
| WO2015096747A1 (en) | Operation response method, client, browser and system | |
| CN106502703B (en) | Function calling method and device | |
| CN108039963B (en) | Container configuration method and device and storage medium | |
| CN106775833B (en) | Device driver loading method, terminal and system | |
| CN110020293B (en) | Multimedia data display method, device and storage medium | |
| CN114661581A (en) | Terminal testing method and device, electronic equipment and computer readable storage medium | |
| CN106713608B (en) | Application function state modification method and device and terminal | |
| CN109800030B (en) | Application program running method and device and terminal | |
| CN106919458B (en) | Method and device for Hook target kernel function | |
| CN108874653B (en) | Task testing method, tester, shared server and readable storage medium | |
| EP2869604B1 (en) | Method, apparatus and device for processing a mobile terminal resource | |
| CN105955739A (en) | Graphical interface processing method, apparatus and system | |
| CN108431767A (en) | A kind of method, user terminal and the storage medium of load software program | |
| CN112749074B (en) | Test case recommending method and device | |
| WO2014166307A1 (en) | Method for determining performance of process of application and computer system | |
| CN106095423B (en) | Method, terminal and server for providing browsing service | |
| CN105278942B (en) | Component management method and device | |
| CN107861827B (en) | Card screen detection method, mobile terminal and computer readable storage medium | |
| CN109145598B (en) | Virus detection method and device for script file, terminal and storage medium | |
| CN108959062B (en) | Webpage element acquisition method and device | |
| WO2015154700A1 (en) | Method and apparatus for repairing dynamic link library file |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |