CN112905439A - Terminal test method, terminal test device and storage medium - Google Patents
Terminal test method, terminal test device and storage medium Download PDFInfo
- Publication number
- CN112905439A CN112905439A CN201911223403.1A CN201911223403A CN112905439A CN 112905439 A CN112905439 A CN 112905439A CN 201911223403 A CN201911223403 A CN 201911223403A CN 112905439 A CN112905439 A CN 112905439A
- Authority
- CN
- China
- Prior art keywords
- test
- test item
- terminal
- system control
- item
- 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 771
- 238000010998 test method Methods 0.000 title claims abstract description 9
- 238000003860 storage Methods 0.000 title claims abstract description 7
- 238000000034 method Methods 0.000 claims abstract description 16
- 230000006870 function Effects 0.000 claims description 24
- 230000007246 mechanism Effects 0.000 claims description 7
- 230000008569 process Effects 0.000 claims description 7
- 230000000694 effects Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000020169 heat generation Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013100 final test Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization 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
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The disclosure relates to a terminal testing method, a terminal testing device and a storage medium. The terminal test method comprises the following steps: after the terminal is determined to finish the test of the current test item, starting the test of the next-level test item connected with the current test item in a test node model, wherein the test node model represents the test item of the terminal and the test flow sequence relation among the test items; and after the terminal finishes testing items corresponding to the terminal in the test node model, determining that the terminal test is finished. By the method and the device, the terminals can be tested by adopting a unified testing method, and the terminal testing efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of mobile communication terminal technologies, and in particular, to a terminal testing method, a terminal testing apparatus, and a storage medium.
Background
In the terminal manufacturing process, after the entire handset is assembled, it is often necessary to test the various components of the terminal. Taking a terminal as an example of a mobile phone, it is necessary to test various components of the mobile phone, such as various acoustic components (a speaker, a microphone, etc.), optical components (a camera, etc.), a motion device (a vibrator), an electromagnetic device (an antenna), and the like.
In the related art, when testing each component of each type of terminal, a test code needs to be written separately for each type of terminal to perform the test. For example, each of the various parts to be tested is treated as a test item, and the test item is written as some function, or class (e.g., Android Activity). The test items are combined into a test sequence by modifying the code. The test items are usually executed sequentially, and if the test time is found to be too long, the code of the test item needs to be modified manually for the purpose of optimization.
Test codes are independently written for each type of terminal, and the codes need to be modified every time a product is changed, so that the development period is influenced. And the writing of test items also affects the overall test flow. The coupling degree of the test items and the test process is high, the parallel relation does not exist between the test items, and the test efficiency is low.
Disclosure of Invention
To overcome the problems in the related art, the present disclosure provides a terminal testing method, a terminal testing apparatus, and a storage medium.
According to a first aspect of the embodiments of the present disclosure, there is provided a terminal testing method, including: after the terminal is determined to finish the test of the current test item, starting the test of the next-level test item connected with the current test item in a test node model, wherein the test node model represents the test item of the terminal and the test flow sequence relation among the test items; and after the terminal finishes testing items corresponding to the terminal in the test node model, determining that the terminal test is finished.
In one example, the test node model is predetermined as follows: determining test items of the terminal and a test flow sequence relation among the test items; respectively corresponding each test item of the terminal to a test item node; carrying out sequential cascade connection on every two test item nodes with the test sequence to obtain a test node model which comprises the test items and represents the sequential relation of the test process among the test items; among the test item nodes which are connected in a pairwise sequential cascade manner, the test item which is tested in advance corresponds to the test item node at the upper level, and the test item which is tested in the later level corresponds to the test item node at the lower level.
In an example, after it is determined that the terminal completes the test of the current test item, starting a next-level test item connected to the current test item in the test node model, including: after the terminal is determined to finish the test of the current test item, deleting the next-level cascade relation taking the current test item as the previous-level test item node; and in the test node model deleting the next-level cascade relation, starting the test of the test item corresponding to the test item node without the previous-level cascade relation.
In one example, a test item is tested, comprising: determining the types of the test items, wherein the types comprise a system control test item type and a non-system control test item type; for a test item of a non-system control test item type, testing on running resources of the non-system control test item type in parallel; and aiming at the test item of the system control test item type, binding the parallel running resource of the system control test item type into the running resource of the non-system control test item type, and testing the test item of the system control test item type by utilizing the bound system control test item type running resource.
In one example, the running resources by using the bound system control test item type to perform parallel testing on the test items of the system control test item type includes: providing the parallel running resource function of the system control test item type to the running resource of the non-system control test item type; calling a parallel running resource function of the non-system control test item type for the test item of the system control test item type through a reflection mechanism; and testing the test items of the system control test item types in parallel by using the called parallel running resource function.
According to a second aspect of the embodiments of the present disclosure, there is provided a terminal test apparatus including: the test unit is configured to start the test of a next-level test item connected with a current test item in a test node model after the terminal completes the test of the current test item, wherein the test node model represents the test item of the terminal and the test flow sequence relation among the test items; and the determining unit is configured to determine that the terminal test is finished after the terminal completes each test item corresponding to the terminal in the test node model.
In an example, the determining unit is further configured to: determining test items of the terminal and a test flow sequence relation among the test items; respectively corresponding each test item of the terminal to a test item node; carrying out sequential cascade connection on every two test item nodes with the test sequence to obtain a test node model which comprises the test items and represents the sequential relation of the test process among the test items; among the test item nodes which are connected in a pairwise sequential cascade manner, the test item which is tested first is the previous-level test item node, and the test item which is tested later is the next-level test item node.
In one example, the test unit starts the next level test item connected to the current test item in the test node model as follows: after the determining unit determines that the terminal completes the test of the current test item, deleting the next-level cascade relation taking the current test item as the previous-level test item node; and in the test node model deleting the next-level cascade relation, starting the test of the test item corresponding to the test item node without the previous-level cascade relation.
In an example, the test unit is configured to test the test item in the following manner: determining the types of the test items, wherein the types comprise a system control test item type and a non-system control test item type; for a test item of a non-system control test item type, testing on running resources of the non-system control test item type in parallel; and aiming at the test item of the system control test item type, binding the parallel running resource of the system control test item type into the running resource of the non-system control test item type, and testing the test item of the system control test item type by utilizing the bound system control test item type running resource.
In an example, the test unit is configured to run the resource with the bound system control test item type and test the test items of the system control test item type in parallel in the following manner: providing the parallel running resource function of the system control test item type to the running resource of the non-system control test item type; calling a parallel running resource function of the non-system control test item type for the test item of the system control test item type through a reflection mechanism; and testing the test items of the system control test item types in parallel by using the called parallel running resource function.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the terminal testing is carried out through the testing node model, the testing node model represents the testing items of the terminal and the testing flow sequence relation among the testing items, the testing of the terminals is realized by adopting a unified testing method, and the testing efficiency of the terminals is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a flow chart illustrating a method of terminal testing according to an exemplary embodiment.
FIG. 2 is a flowchart illustrating a method of determining a test node model in accordance with an exemplary embodiment.
Fig. 3 is a flow chart illustrating a method of terminal testing according to an example embodiment.
FIG. 4 is an exemplary diagram illustrating a test item node model in accordance with one illustrative embodiment.
Fig. 5 is a flow chart illustrating a method of terminal testing according to an example embodiment.
FIG. 6 is a block diagram illustrating a terminal testing device according to an exemplary embodiment.
FIG. 7 is a block diagram illustrating an apparatus in accordance with an example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
In the related art, when testing hardware of a terminal, because each type of terminal has different structures and the design of each hardware of the terminal is different, some hardware can be tested in parallel and some hardware needs sequential testing when testing the terminal hardware.
Currently, when various terminals are tested, the test sequence of terminal hardware is determined first, and test codes are independently written for the terminals according to the test sequence of the hardware. When testing hardware of each type of terminal, test codes need to be independently written for the terminal, so that the coupling degree of test items and a test flow is high, and the test efficiency is low.
Therefore, in order to overcome the problems that when testing terminals in the related art, test codes need to be independently written for each type of terminal, and the coupling degree of test items and test flows is high, the terminal testing method capable of uniformly testing each type of terminal is provided.
Fig. 1 is a flowchart illustrating a terminal testing method according to an exemplary embodiment, where the terminal testing method, as shown in fig. 1, includes the following steps.
In step S11, after it is determined that the terminal completes the test of the current test item, the test of the next-level test item connected to the current test item in the test node model is started, and the test node model represents the test item of the terminal and the test flow sequence relationship between the test items.
In the present disclosure, a test item may be understood as hardware in a terminal that needs to be tested.
For example, the hardware in the terminal that needs to be tested may include, but is not limited to, a display, a speaker, a camera, an earpiece, and the like.
The test node model can be a model for representing the test items to be tested of the terminal and the test flow sequence relation among the test items to be tested.
In actual testing, the terminal testing method applying the present disclosure may be implemented by, for example, a terminal hardware testing system including a parser and a planner. For example, the test node model representing the test items of the terminal and the test flow sequence relation among the test items can be input into the test system in the form of json or xml, and the test system analyzes the files in the form of json or xml through the analyzer to obtain the test flow sequence relation among the test items of the terminal. And planning the test sequence among the test items by using a planner according to the test flow sequence relation among the test items, and sequentially testing the test items with the test sequence after planning.
In the embodiment of the disclosure, if the test sequence of the terminal test items changes, the terminal test can be realized only by changing the test items representing the terminal in the json or xml file and the test flow sequence relationship among the test items. Without requiring the test code to be rewritten according to the order of the test items.
In one embodiment, after the terminal completes the test of the current test item, the next-level test item connected to the current test item is tested according to the test flow sequence relation among the test items in the test node model.
In step S12, after the terminal completes each test item corresponding to the terminal in the test node model, it is determined that the terminal test is ended.
In the disclosure, the test items of the terminal are tested according to the test flow sequence relation among the test items in the test node model, and when the terminal completes all the test items corresponding to the terminal in the test node model, it is determined that the terminal test is finished.
In an exemplary embodiment of the present disclosure, test items of a terminal and a test flow sequence relationship between the test items may be described by a test node model. In the test of the terminal, if the test items or the test sequence of the test items changes, the test of each terminal can be realized only by changing the test items or the test flow sequence of each test item in the test node model. Therefore, the terminals are tested by adopting the uniform test node model, and the terminal test efficiency is improved.
The present disclosure will be described in detail below with reference to practical applications.
In the present disclosure, the test node model may be predetermined, and the terminal may be tested by using the test items representing the terminal in the test node model and the test flow sequence relationship among the test items. In the embodiment of the present disclosure, an implementation process of determining a test node model may be as shown in fig. 2.
FIG. 2 is a flowchart illustrating a method of determining a test node model, as shown in FIG. 2, according to an exemplary embodiment, including the following steps.
In step S211, the test items of the terminal and the test flow sequence relationship between the test items are determined.
Because the hardware structures of each type of terminal are different, before testing the hardware of the terminal, the hardware needing to be tested in the terminal, namely the test items, needs to be determined. And determining the test flow sequence relation among the hardware, and further testing the terminal according to the test items of each type of terminal and the test flow sequence relation among the test items.
For example, terminal a includes a main camera and terminal B includes both a main camera and a sub camera. When testing the main camera of the terminal a, since the heat generation of the main camera is high, in order to prevent the hardware from being burned out due to the high temperature, the hardware cannot be tested simultaneously with the hardware with the same high heat generation as that of the terminal a, for example, the hardware of the main camera and the hard disk of the terminal cannot be tested simultaneously. When testing the terminal B, since the heat generation of the sub-camera is relatively small, the test can be performed simultaneously with the hardware having relatively high heat generation in the terminal B, for example, the test can be performed simultaneously with the sub-camera and the hard disk of the terminal.
In step S212, each test item of the terminal is associated with a test item node.
In the present disclosure, after determining the test items of the terminal and the test flow sequence relationship among the test items, each test item may be described in a test item node manner according to a manner that the test item corresponds to the test item node.
In step S213, the test item nodes with the test sequence are connected in cascade in sequence to obtain a test node model including the test items and representing the test flow sequence relationship between the test items.
In the embodiment of the disclosure, after the test items are described in a test item node manner, every two test item nodes with a test sequence are sequentially connected in a cascade manner, so as to obtain a test node model including each test item and representing a test flow sequence relation between each test item. Among the test item nodes which are connected in a pairwise sequential cascade manner, the test item which is tested first is the previous-level test item node, and the test item which is tested later is the next-level test item node.
In the embodiment of the disclosure, the terminal test items and the relation between the test items are described by the test node model, so that when the terminal is tested, the test items are tested in parallel or sequentially according to the relation between the test items, and the test efficiency is improved.
Fig. 3 is a flowchart illustrating a terminal testing method according to an exemplary embodiment, and as shown in fig. 3, the terminal testing method includes the following steps.
In step S31, a test node model is predetermined.
In one implementation, the disclosed embodiments may predetermine the test node model. The test node model can be described by the test nodes and the cascade relationship between the test nodes, for example. The test nodes in the test node model represent test items, and the cascade relation among the test nodes represents the test flow sequence relation among the test items. An example graph of a test node model may be as shown in FIG. 4.
The test Node model in fig. 4 may also be referred to as a Computational Node Graph (CNG). The sequence of the test flow of the final test items is described by CNG. In fig. 4, each circle represents a test node, i.e., a test item, and the circles are connected by a directed line segment, i.e., the test item nodes are connected in a sequential cascade manner two by two. Wherein circles of peers that are not connected may be test items that can be tested in parallel. The circle connected with the starting point of the line segment is the upper level test item node, the circle pointed by the arrow of the line segment is the lower level test item node, and the circle are connected through the directed line segment to obtain a single directed acyclic graph, namely CNG, of the directed connecting line connecting the test item nodes.
In step S32, after it is determined that the terminal completes the test of the current test item, the next-level cascade relationship with the current test item as the previous-level test item node is deleted.
For example, in fig. 4, after the test of the test node a is completed, the next cascade relation with the test node a as the previous test node is deleted, that is, the line segment pointing to the test node B with the test node a as the starting point is deleted.
In the actual test, the test sequence among the test items can be planned by using the planner, and the test items are tested according to the test flow sequence relation among the test items after the planning by the planner. For example, in FIG. 4, after the test item node A completes, the planner deletes all segments that begin at test item node A. And when all the line segments pointing to the test item node C are deleted, executing the test on the test item node C.
In step S33, in the test node model with the deleted next-level cascade relationship, the test of the test item corresponding to the test item node without the previous-level cascade relationship is started, and after the terminal completes each test item corresponding to the terminal in the test node model, it is determined that the terminal test is finished.
For example, in fig. 4, in the test node model in which the cascade relationship between the test node a and the test node B is deleted, the test of the test item corresponding to the test item of the test item node B without the previous stage of cascade relationship is started, and when all the cascade relationships are deleted and the test of the test item corresponding to the test item node C is executed, it is determined that the terminal test is ended.
In an actual test, by applying the terminal test method disclosed by the disclosure, for example, CNG representing test items of a terminal and test flow sequence relations among the test items can be input into a test system in a json or xml file, and the test system analyzes the json or xml file through an analyzer to obtain the test flow sequence relations among the test items of the terminal. And planning the test sequence among the test items by using a planner according to the test flow sequence relation among the test items, and sequentially testing the test items with the test sequence after planning.
In the embodiment of the disclosure, if the test sequence of the terminal test items changes, the terminal test can be realized only by changing the test items characterizing the terminal in the json or xml file and the CNG among the test items. Without requiring the test code to be rewritten according to the order of the test items.
In the exemplary embodiment of the present disclosure, when testing each type of terminal by using a predetermined test node model, if a terminal test item or a test sequence of the test item changes, the test of each terminal can be implemented only by changing each test item in the test node model or a test flow sequence of each test item. Therefore, the terminal can be tested by adopting a uniform test node model, and the terminal testing efficiency is improved.
Fig. 5 is a flowchart illustrating a terminal testing method according to an exemplary embodiment, and as shown in fig. 5, the terminal testing method includes the following steps.
In step S51, a test item type is determined.
The test item types comprise a system control test item type and a non-system control test item type.
In the design and implementation of the terminal, since some test items in the terminal are controlled by the operating system of the terminal, the system control test item type is referred to in this disclosure. While other test items are not controlled by the terminal's operating system, referred to in this disclosure as non-system controlled test item types. In the terminal test, the types of the test items need to be determined, and then the test methods are respectively adopted for the different types of test items according to the different types of test items.
Taking a terminal as an example of a mobile phone, in an android system, for example, a test item "bluetooth" and a test item "camera" control the type of the test item for a system controlled by the android system. For example, the test item "memory" test item "antenna" is a non-system control test item type that is not controlled by the android system. In the test of the mobile phone test items, test methods respectively adopted by different types of test items need to be tested according to the types of the test items.
In step S52, for the test item of the non-system control test item type, a test is performed in parallel on the run resource of the non-system control test item type.
In step S53, for the test item of the system control test item type, the parallel running resource of the system control test item type is bound to the running resource of the non-system control test item type, and the test item of the system control test item type is tested in parallel by using the bound system control test item type running resource.
In the present disclosure, the parallel running resource function of the system control test item type is provided to the running resource of the non-system control test item type, and the parallel running resource function of the non-system control test item type is called for the test item of the system control test item type through a reflection mechanism. And testing the test items of the system control test item types in parallel by using the called parallel running resource function.
In the following, the terminal is taken as an android mobile phone as an example, and the terminal testing method related to the present disclosure is described in detail.
In the android operating system, the test item types can be divided into a system control test item type and a non-system control test item type according to the characteristics of the android system.
Specifically, in the android system, the test item node may be understood as being composed of a non-system control test item node HTNode and a system control test item node ActivityNode.
For the test item which is an HTNode, the test can be performed on the running resource pool (for example, the resource pool of HandleThread) of the non-system control test item in parallel.
For the test items of the ActivityNode, the ActivityNode needs to operate in the Android Activity due to the known characteristics of the Android system, the Android Activity is unique, and the ActivityNode can only operate one test item at a time by operating the Android Activity, so that the requirement of parallel test on a plurality of system control test items cannot be met. In order to solve the problem that a plurality of system control test items cannot be tested in parallel, the ActivityNode can be operated in an Android.
Further, in order to combine the HTNode and the ActivityNode, and implement a unified test on the test item, that is, implement a test on the terminal by using the test item node model, the ActivityNode may be bound (bind) to the HTNode, thereby implementing a function of providing a control system for controlling the test item function by the ActivityNode to the HTNode. When the HTNode calls the android.View through the Android Activity to realize the parallel test of the system control test items, the Android Activity returns the called android.View to the called HTNode through a reflection mechanism, so that a plurality of non-system control test items can be operated in parallel through the HTNode, and the Android Activity can be called through the HTNode to realize the purpose of operating a plurality of system control test items in parallel.
Therefore, the terminal based on the android system realizes the test of the terminal test items by using the test node model.
In an exemplary embodiment of the present disclosure, a test item node model may be obtained by determining test items and a test flow order relationship between the test items. According to the test item node model, in the terminal test, the non-system control test items are subjected to parallel test through the running resources of the non-system control test items, the system control test items and the parallel running resources of the system control test items are bound to the running resources of the non-system control test items, and the bound system control test item running resources are utilized to carry out parallel test on the test items of the type of the system control test items. Therefore, in actual test, test deployment of a test item node model matched with the terminal system can be realized according to the characteristics of the terminal system, and further, various types of terminals can be tested according to the test node model.
Based on the same inventive concept, the disclosure also provides a terminal testing device.
It is understood that, in order to implement the above functions, the application control device provided in the embodiments of the present disclosure includes a hardware structure and/or a software module corresponding to each function. The disclosed embodiments can be implemented in hardware or a combination of hardware and computer software, in combination with the exemplary elements and algorithm steps disclosed in the disclosed embodiments. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
FIG. 6 is a block diagram illustrating a terminal testing device according to an exemplary embodiment. Referring to fig. 6, the apparatus includes a test unit 601 and a determination unit 602.
The test unit 601 is configured to start a test of a next-level test item connected to a current test item in the test node model after the terminal completes the test of the current test item, and the test node model represents the test item of the terminal and a test flow sequence relation among the test items; the determining unit 602 is configured to determine that the terminal test is finished after the terminal completes each test item corresponding to the terminal in the test node model.
In an example, the determining unit 602 is further configured to: determining test items of the terminal and a test flow sequence relation among the test items; respectively corresponding each test item of the terminal to a test item node; carrying out sequential cascade connection on every two test item nodes with the test sequence to obtain a test node model which comprises each test item and represents the sequential relation of the test process among the test items; among the test item nodes which are connected in a pairwise sequential cascade manner, the test item which is tested first is the previous-level test item node, and the test item which is tested later is the next-level test item node.
In one example, the test unit 601 opens the next level test item connected to the current test item in the test node model as follows: after the determining unit 602 determines that the terminal completes the test of the current test item, deleting the next-level cascade relation taking the current test item as the previous-level test item node; and in the test node model deleting the next-stage cascade relation, starting the test of the test item corresponding to the test item node without the previous-stage cascade relation.
In one example, the test unit 601 is configured to test the test items in the following manner: determining the types of the test items, wherein the test types comprise a system control test item type and a non-system control test item type; for the test items of the non-system control test item types, testing is carried out on the running resources of the non-system control test item types in parallel; and aiming at the test items of the system control test item type, binding the parallel running resources of the system control test item type into the running resources of the non-system control test item type, and testing the test items of the system control test item type by utilizing the bound system control test item type running resources.
In one example, the test unit 601 is configured to run the resources with the bound system control test item type and test the test items of the system control test item type in parallel in the following manner: providing the parallel running resource function of the system control test item type to the running resource of the non-system control test item type; calling a parallel running resource function of the type of the non-system control test item for the test item of the type of the system control test item through a reflection mechanism; and testing the test items of the system control test item types in parallel by using the called parallel running resource function.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
A non-transitory computer readable storage medium having instructions therein that, when executed by a processor of a mobile terminal, enable the mobile terminal to perform a terminal testing method.
Fig. 7 is a block diagram illustrating an apparatus 700 for terminal testing in accordance with an example embodiment. For example, the apparatus 700 may be provided as a server. Referring to fig. 7, apparatus 700 includes a processing component 722 that further includes one or more processors and memory resources, represented by memory 732, for storing instructions, such as applications, that are executable by processing component 722. The application programs stored in memory 732 may include one or more modules that each correspond to a set of instructions. Further, the processing component 722 is configured to execute instructions to perform the above-described terminal test method.
The apparatus 700 may also include a power component 726 configured to perform power management of the apparatus 700, a wired or wireless network interface 750 configured to connect the apparatus 700 to a network, and an input output (I/O) interface 758. The apparatus 700 may operate based on an operating system stored in memory 732, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
It is further understood that the use of "a plurality" in this disclosure means two or more, as other terms are analogous. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. The singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It will be further understood that the terms "first," "second," and the like are used to describe various information and that such information should not be limited by these terms. These terms are only used to distinguish one type of information from another and do not denote a particular order or importance. Indeed, the terms "first," "second," and the like are fully interchangeable. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure.
It is further to be understood that while operations are depicted in the drawings in a particular order, this is not to be understood as requiring that such operations be performed in the particular order shown or in serial order, or that all illustrated operations be performed, to achieve desirable results. In certain environments, multitasking and parallel processing may be advantageous.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (12)
1. A terminal test method is characterized by comprising the following steps:
after the terminal is determined to finish the test of the current test item, starting the test of the next-level test item connected with the current test item in a test node model, wherein the test node model represents the test item of the terminal and the test flow sequence relation among the test items;
and after the terminal finishes testing items corresponding to the terminal in the test node model, determining that the terminal test is finished.
2. The terminal test method of claim 1, wherein the test node model is predetermined as follows:
determining test items of the terminal and a test flow sequence relation among the test items;
respectively corresponding each test item of the terminal to a test item node;
carrying out sequential cascade connection on every two test item nodes with the test sequence to obtain a test node model which comprises the test items and represents the sequential relation of the test process among the test items;
among the test item nodes which are connected in a pairwise sequential cascade manner, the test item which is tested in advance corresponds to the test item node at the upper level, and the test item which is tested in the later level corresponds to the test item node at the lower level.
3. The method according to claim 2, wherein after the terminal is determined to complete the test of the current test item, starting a next-level test item connected to the current test item in the test node model, including:
after the terminal is determined to finish the test of the current test item, deleting the next-level cascade relation taking the current test item as the previous-level test item node;
and in the test node model deleting the next-level cascade relation, starting the test of the test item corresponding to the test item node without the previous-level cascade relation.
4. A terminal testing method according to any one of claims 1 to 3, wherein the testing of the test items comprises:
determining the types of the test items, wherein the types comprise a system control test item type and a non-system control test item type;
for a test item of a non-system control test item type, testing on running resources of the non-system control test item type in parallel;
and aiming at the test item of the system control test item type, binding the parallel running resource of the system control test item type into the running resource of the non-system control test item type, and testing the test item of the system control test item type by utilizing the bound system control test item type running resource.
5. The terminal testing method according to claim 4, wherein the running of the resource by the bound system control test item type and the parallel testing of the test item of the system control test item type comprises:
providing the parallel running resource function of the system control test item type to the running resource of the non-system control test item type;
calling a parallel running resource function of the non-system control test item type for the test item of the system control test item type through a reflection mechanism;
and testing the test items of the system control test item types in parallel by using the called parallel running resource function.
6. A terminal test apparatus, characterized in that the terminal test apparatus comprises:
the test unit is configured to start the test of a next-level test item connected with a current test item in a test node model after the terminal completes the test of the current test item, wherein the test node model represents the test item of the terminal and the test flow sequence relation among the test items;
and the determining unit is configured to determine that the terminal test is finished after the terminal completes each test item corresponding to the terminal in the test node model.
7. The terminal test device according to claim 6, wherein the determination unit is further configured to:
determining test items of the terminal and a test flow sequence relation among the test items;
respectively corresponding each test item of the terminal to a test item node;
carrying out sequential cascade connection on every two test item nodes with the test sequence to obtain a test node model which comprises the test items and represents the sequential relation of the test process among the test items;
among the test item nodes which are connected in a pairwise sequential cascade manner, the test item which is tested first is the previous-level test item node, and the test item which is tested later is the next-level test item node.
8. The terminal test device according to claim 7, wherein the test unit starts the next level test item connected to the current test item in the test node model as follows:
after the determining unit determines that the terminal completes the test of the current test item, deleting the next-level cascade relation taking the current test item as the previous-level test item node;
and in the test node model deleting the next-level cascade relation, starting the test of the test item corresponding to the test item node without the previous-level cascade relation.
9. The terminal testing device according to any one of claims 6 to 8, wherein the testing unit is configured to test the test item in the following manner:
determining the types of the test items, wherein the types comprise a system control test item type and a non-system control test item type;
for a test item of a non-system control test item type, testing on running resources of the non-system control test item type in parallel;
and aiming at the test item of the system control test item type, binding the parallel running resource of the system control test item type into the running resource of the non-system control test item type, and testing the test item of the system control test item type by utilizing the bound system control test item type running resource.
10. The terminal test apparatus according to claim 9, wherein the test unit is configured to run resources using the bound system control test item type in parallel to test the test items of the system control test item type in the following manner:
providing the parallel running resource function of the system control test item type to the running resource of the non-system control test item type;
calling a parallel running resource function of the non-system control test item type for the test item of the system control test item type through a reflection mechanism;
and testing the test items of the system control test item types in parallel by using the called parallel running resource function.
11. A terminal testing device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to: performing the terminal testing method of any one of claims 1-5.
12. A non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by a processor, perform the terminal testing method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911223403.1A CN112905439A (en) | 2019-12-03 | 2019-12-03 | Terminal test method, terminal test device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911223403.1A CN112905439A (en) | 2019-12-03 | 2019-12-03 | Terminal test method, terminal test device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112905439A true CN112905439A (en) | 2021-06-04 |
Family
ID=76104320
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911223403.1A Pending CN112905439A (en) | 2019-12-03 | 2019-12-03 | Terminal test method, terminal test device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112905439A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114812695A (en) * | 2022-06-27 | 2022-07-29 | 芯耀辉科技有限公司 | Product testing method and device, computer equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060129891A1 (en) * | 2004-11-23 | 2006-06-15 | Microsoft Corporation | Software test framework |
| CN101551777A (en) * | 2009-05-08 | 2009-10-07 | 刘志方 | Apparatus of mobile terminal software base on abnormity and interrupt mechanism and test method |
| CN108829609A (en) * | 2018-07-27 | 2018-11-16 | 深圳智芯数据服务有限公司 | A kind of test method and system of blue tooth products |
-
2019
- 2019-12-03 CN CN201911223403.1A patent/CN112905439A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060129891A1 (en) * | 2004-11-23 | 2006-06-15 | Microsoft Corporation | Software test framework |
| CN101551777A (en) * | 2009-05-08 | 2009-10-07 | 刘志方 | Apparatus of mobile terminal software base on abnormity and interrupt mechanism and test method |
| CN108829609A (en) * | 2018-07-27 | 2018-11-16 | 深圳智芯数据服务有限公司 | A kind of test method and system of blue tooth products |
Non-Patent Citations (1)
| Title |
|---|
| 王汝言;王鹏;张炎;: "一种基于ABBET的通信设备RF ATS架构", 自动化与仪表, no. 11 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114812695A (en) * | 2022-06-27 | 2022-07-29 | 芯耀辉科技有限公司 | Product testing method and device, computer equipment and storage medium |
| CN114812695B (en) * | 2022-06-27 | 2022-10-28 | 芯耀辉科技有限公司 | Product testing method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8527938B2 (en) | Worklet modeling | |
| CN112947935A (en) | Operation method and device, electronic device and storage medium | |
| CN112463634B (en) | Software testing method and device under micro-service architecture | |
| CN108255585B (en) | SDK abnormal control and application program operation method, device and equipment thereof | |
| CN109618315A (en) | A kind of control method of lighting apparatus, device, storage medium and intelligent terminal | |
| CN111061551A (en) | Node merging and scheduling method, device, equipment and storage medium | |
| CN104539476A (en) | Data package obtaining method and device | |
| US10716021B1 (en) | Minimization of drive test (MDT) data donor device selection | |
| CN111679811B (en) | Web service construction method and device | |
| CN113553257A (en) | Test method, test device, storage medium and electronic equipment | |
| Kamaludeen et al. | Guideline-based approach for IoT home application development | |
| CN112905439A (en) | Terminal test method, terminal test device and storage medium | |
| CN107844363B (en) | Business transaction processing method, device, storage medium and equipment | |
| CN111367561B (en) | Remote development method and device for software program | |
| CN111767316A (en) | Target task processing method and device and electronic equipment | |
| CN108733468A (en) | Timed task Dynamic Configuration and device, storage medium and server cluster | |
| US20230018802A1 (en) | Graphical user interface to configure parameters of an api based on user inputs | |
| CN109508193A (en) | A kind of application deployment operation method, device, terminal device and medium | |
| CN113050936B (en) | Front-end data processing method and device based on integrated development environment | |
| CN110427260B (en) | Host job scheduling method, device and system | |
| US20130124553A1 (en) | Flexible interface module | |
| US10466974B2 (en) | Independent expression animations | |
| CN105743929B (en) | A kind of method and device of terminal interaction | |
| CN111327472A (en) | Method and device for acquiring target network | |
| CN113886053B (en) | Task scheduling method and device for task scheduling |
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 |