CN111611156B - Function test method, function test device, and computer-readable storage medium - Google Patents
Function test method, function test device, and computer-readable storage medium Download PDFInfo
- Publication number
- CN111611156B CN111611156B CN202010348165.3A CN202010348165A CN111611156B CN 111611156 B CN111611156 B CN 111611156B CN 202010348165 A CN202010348165 A CN 202010348165A CN 111611156 B CN111611156 B CN 111611156B
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- function
- core
- functions
- 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.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 676
- 238000010998 test method Methods 0.000 title claims abstract description 8
- 230000006870 function Effects 0.000 claims abstract description 188
- 238000000034 method Methods 0.000 claims abstract description 38
- 238000011990 functional testing Methods 0.000 claims description 29
- 238000012544 monitoring process Methods 0.000 claims description 7
- 230000005055 memory storage Effects 0.000 claims 1
- 230000008569 process Effects 0.000 abstract description 7
- 230000009286 beneficial effect Effects 0.000 abstract description 5
- 238000004904 shortening Methods 0.000 abstract description 4
- 238000004891 communication Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 10
- 230000008859 change Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 230000008439 repair process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000001133 acceleration Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000003064 k means clustering Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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
Abstract
The present disclosure relates to a function test method, a function test device, and a computer-readable storage medium. The function test method comprises the following steps: determining a test function to be tested, and calling a test case group corresponding to the test function; determining a test module corresponding to the test function, and determining the priority corresponding to each test case in the test case group and the test module; and testing the test functions one by one based on the priorities of the test cases in the test module. By the method, the test case group corresponding to the test function can be called when the test function is tested. Thereby being beneficial to reducing the test range and shortening the test time. According to the determined test module and the priority of each test case in the matched test case group, the method is beneficial to defining the test key points of each test function in each module, and further can have targeted test during test, thereby accelerating the test process and shortening the test time.
Description
Technical Field
The disclosure relates to the technical field of mobile terminals, and in particular relates to a function test method, a function test device and a computer readable storage medium.
Background
In the related art, in order to facilitate testing of certain functions of a terminal, related test information of a module is acquired. The document can be described in advance according to the requirements of the test functions, and test cases in the aspects of basic function test cases, stability, performance, power consumption and the like are written. When the test is required, each test case is tested one by one according to the requirement, and the test period is long because the test key point is not needed and the test range is wider.
Disclosure of Invention
To overcome the problems in the related art, the present disclosure provides a function test method, a function test apparatus, and a computer-readable storage medium.
According to a first aspect of embodiments of the present disclosure, there is provided a functional test method, including: determining a test function to be tested, and calling a test case group corresponding to the test function, wherein a plurality of test cases in the test case group correspond to different priorities in different test modules, and the use frequency of a high-priority test case is greater than that of a low-priority test case; determining a test module corresponding to the test function, and determining the priority corresponding to each test case in the test case group and the test module; and testing the test functions one by one based on the priorities of the test cases in the test module.
In an embodiment, determining a priority of each test case in the test case group corresponding to the test module includes: determining a core test case group corresponding to the test function, wherein the core test case group characterizes a plurality of test cases used for testing main functions of the test function in the test case group; counting the use frequency of each test case in the core test case group in a test module corresponding to the test function; and determining the priority of each test case in the core test case group in the test module corresponding to the test function according to the use frequency.
In another embodiment, determining a core test case group corresponding to a test function includes: and the test cases meeting the test requirements in the test case results fed back by the MQS of the quality monitoring system aiming at the test cases corresponding to the test functions are used as core test case groups corresponding to the test functions.
In yet another embodiment, determining a core test case group corresponding to a test function includes: and determining the test cases matched with the test functions through a back gate test, and taking the test cases matched with the test functions as core test case groups corresponding to the test functions.
In yet another embodiment, determining a core test case group corresponding to a test function includes: and taking the test case selected by the user from the test cases corresponding to the test functions as a core test case group corresponding to the test functions.
In yet another embodiment, the functional test method further comprises: based on the test results of executing each test case in the test case group, the priority of the test case corresponding to the test module is dynamically adjusted.
According to a second aspect of embodiments of the present disclosure, there is provided a functional test apparatus, comprising: the calling unit is used for determining a test function to be tested and calling a test case group corresponding to the test function, wherein a plurality of test cases in the test case group correspond to different priorities in different test modules, and the use frequency of the high-priority test cases is greater than that of the low-priority test cases; the matching unit is used for determining a test module corresponding to the test function and determining the priority corresponding to each test case in the test case group and the test module; and the test unit is used for testing the test functions one by one based on the priorities of the test cases in the test module.
In an embodiment, the matching unit determines the priority corresponding to each test case in the test case group and the test module by adopting the following manner: determining a core test case group corresponding to the test function, wherein the core test case group characterizes a plurality of test cases used for testing main functions of the test function in the test case group; counting the use frequency of each test case in the core test case group in a test module corresponding to the test function; and determining the priority of each test case in the core test case group in the test module corresponding to the test function according to the use frequency.
In another embodiment, the matching unit determines the core test case group corresponding to the test function by using the following manner: and the test cases meeting the test requirements in the test case results fed back by the MQS of the quality monitoring system aiming at the test cases corresponding to the test functions are used as core test case groups corresponding to the test functions.
In yet another embodiment, the matching unit determines the core test case group corresponding to the test function by: and determining the test cases matched with the test functions through a back gate test, and taking the test cases matched with the test functions as core test case groups corresponding to the test functions.
In yet another embodiment, the matching unit determines the core test case group corresponding to the test function by: and taking the test case selected by the user from the test cases corresponding to the test functions as a core test case group corresponding to the test functions.
In a further embodiment, the calling unit is further configured to: based on the test results of executing each test case in the test case group, the priority of the test case corresponding to the test module is dynamically adjusted.
According to a third aspect of embodiments of the present disclosure, there is provided a functional test apparatus, comprising: a memory for storing instructions; a processor; the instructions for invoking the memory store perform any of the functional test methods described above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, perform any one of the above-described functional test methods.
The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects: in the functional test method, all test cases are integrated in advance, a test case group corresponding to the test function is obtained according to the corresponding relation between all test cases and the test function, and the priority of the test cases in all test case groups in all test modules is determined. And after determining the test function to be tested or the loophole exists, calling the related test case group according to the test module corresponding to the test function, thereby being beneficial to reducing the test range and further shortening the test time. And according to different priorities of each test case in each test case group in each test module, the method is beneficial to defining the testing key points of each test function in each module, and further can have targeted test during testing, thereby accelerating the test process and shortening the test time.
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 disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a flow chart illustrating a functional test method according to an exemplary embodiment.
Fig. 2 is a flow chart illustrating a functional test method according to an exemplary embodiment.
Fig. 3 is a block diagram illustrating a functional test device according to an exemplary embodiment.
Fig. 4 is a block diagram illustrating a functional test device according to an exemplary embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
It is further understood that the terms "first," "second," and the like are used to describe various information, but such information should not be limited to 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 expressions "first", "second", etc. may be used entirely interchangeably. 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.
In the related art, when testing the test function, test cases in aspects of test cases, stability, performance, power consumption and the like of each basic function of the test module are tested on a test module by test case basis. Resulting in long test cycles and no emphasis on the test. When some small test functions are required to be tested, the test is performed according to test experience of a tester, and the test is too subjective and is easy to cause incomplete test.
Aiming at the situation, the disclosure provides a functional test method, which integrates all test cases according to the corresponding relation between the test cases and the test functions to form test case groups corresponding to the test functions, and obtains the test priorities of all the test cases in all the test case groups in different test modules. And when the test module is tested, the test module can be tested in a targeted manner, so that the test range is reduced, and the test period is shortened. And the priority of each test case in each test module is favorable for defining the testing key points of each test function in each test module, so that the test process is accelerated.
Fig. 1 is a flowchart of a functional test method according to an exemplary embodiment, and as shown in fig. 1, a functional test method 10 includes the following steps S11 to S13.
In step S11, a test function to be tested is determined, and a test case group corresponding to the test function is called.
In the embodiment of the disclosure, the test function to be tested can be determined according to the requirement of a tester, and then the test case group corresponding to the test function is called. Or in the quality monitoring system (MIUI Quality System, MQS), data dotting is carried out through log logs, and whether the current system has loopholes or the business functions have loopholes is judged. When the loopholes exist, determining the test functions with the loopholes according to the MQS, and further calling the test case groups corresponding to the test functions.
In the present disclosure, each test case in the test case group is a test case corresponding to the test function. When testing is performed, different test cases can test the test work for different purposes, and whether the corresponding test module can meet the purpose or not is further verified. In the same test case group, aiming at different test modules, the priorities of the tests performed by the test cases are different. When testing the test function of the test module, the higher the priority of the test case is, the more preferably the test is performed; conversely, the lower the priority, the later the test order.
In an embodiment, the priority of testing each test case in the test case set in each test module may be determined according to the history repairing record of each test case in the test case set under the test module. In an implementation scenario, according to the multiple historical repair records of the test function under the test module, the use frequency of each test case in the test case group can be determined, namely, the number of times that the test purpose of the test case can be successfully repaired by the test module under the test case. And further, according to the repeated history repairing records, the use frequency of the test module for testing each test case under the test function is determined. Therefore, the priority of each test case under the test module is determined according to the repaired use frequency, and the use frequency of the high-priority test case is greater than that of the low-priority test case. The higher the test case frequency, the test module will detect the test function under the test case
Because the importance of the test function is different in different test modules, the priority order of the test cases in each test case group is also different. The priority order of each test case in each test case group is determined according to different test modules, so that when the test is conducted again, the test key points can be clarified, the test cases frequently conducted in the test can be called according to the historical repair conditions, and further the test process is accelerated. And through determining the priority of each test case in each test case group under each test module, a tester can conduct targeted test without experience limitation, and objective test is conducted.
In step S12, a test module corresponding to the test function is determined, and a priority between each test case in the test case group and the matching test module is determined.
In the embodiment of the disclosure, according to a test function with a vulnerability, one or more test modules corresponding to the test function are determined. According to the determined test module, the priority of each test case in the current test module under the test function is obtained, so that the test can be conducted by preferentially adopting the test cases with high priority under the test module when the test is conducted, the test cases corresponding to the loopholes can be conveniently and rapidly determined, the test time is shortened, and the test process is accelerated.
In an embodiment, in order to facilitate defining a testing key point, a plurality of test cases in a test case group are screened to obtain a plurality of core cases for executing a main test function, so as to form a core test case group, and the core test case group characterizes test cases for executing the main test function in the test case group. For example: when the screen locking function is tested, whether the screen can display the rendering interface during unlocking belongs to the normal test case of the screen locking function is tested, and the main test function of the screen locking function is whether the screen can be unlocked, so that whether the screen can be unlocked without considering the test case of other factors is tested, and the screen locking function is the main core case of the screen locking function. According to the test functions which can be executed by each test module, the core test case groups corresponding to the test functions are associated according to the modules, so that when the test modules are tested, each core test case which needs to be tested can be rapidly determined, and the test range is reduced.
In order to accelerate the test process and improve the test efficiency, the priority of each core test case in each core test case group in each test module is predetermined. According to the historical bug repairing records of the test modules, the repairing times of the functions corresponding to the core test cases under the core test cases are counted, namely the using frequency of the test cases in the core test case group in the test modules corresponding to the core test case test functions. In an embodiment, the use frequency of each test case in the core test case group in the same test module is counted, and regular expressions can be adopted for counting, so that the statistics is more flexible and logical. And then, the priority of each core test case in each test module is determined through a clustering algorithm, so that the priority division of each core test case is more objective. The clustering algorithm may employ K-means (K-means clustering algorithm), and is not limited in this disclosure. By dividing the priority of each core test case in each test module, when the loopholes happen again, key tests can be carried out according to the priorities of the test modules where the loopholes happen and each core test case, and therefore the loopholes can be solved quickly. In an implementation scenario, the use frequency of each core test case in the same test module may be divided into four echelons by K-means to form 4 priority levels, where the higher the use frequency is, the higher the corresponding priority level is.
In step S13, the test functions are tested piece by piece based on the priorities of the test cases in the test modules.
In the embodiment of the disclosure, according to the determined priorities of the test cases in the test module and the test case group under the test module, the test module is tested under each test case one by one, so that the repair of the test module is completed rapidly, and the problem of verification is solved more efficiently.
Through the embodiment, the use frequency of each test case under each test module can be accurately obtained through big data collection and data analysis, and then the priority of each test case in each test case group under different test modules can be objectively obtained, so that the test can be more efficiently and pointedly performed during the test, and the test time is shortened. And the priority of each test case in each test case group under different test modules is predetermined, so that a tester is helped not to be limited by experience when testing, the testing key point is more accurate, and the condition that the test case is missed is helped to be avoided.
In an embodiment, in test case results fed back by the quality monitoring system MQS aiming at the test cases corresponding to the test functions, the test cases meeting the test requirements are used as core test case groups corresponding to the test functions. The core test case can be obtained according to the developed test result and the feedback of the MQS system. In an implementation scenario, when a problem occurs in a test function, a specific vulnerability can be determined by dotting data in log logs, and then repairing the vulnerability by a developer or a code auditing system (Code Review System, CRS). By automatic packaging, the test flow is automatically triggered according to the repair jira module information (an item and transaction tracking tool). And verifying research and development tests, and judging whether the vulnerability can be repaired according to the test result under each test case by combining the feedback of the MQS system. If the repair is complete, the test case is a core test case. And further, each core test case is subjected to the corresponding test function to obtain a core test case group corresponding to the test function.
In another embodiment, the test cases matching the test functions are determined through a back gate test, and the test cases matching the test functions are used as core test case groups corresponding to the test functions. And through entering a back door operated by the module, back door testing is carried out on the back door, the application range of each test case is determined one by one, the application range comprises applicable test functions, and further the core test case is determined. And further, each core test case is subjected to the corresponding test function to obtain a core test case group corresponding to the test function.
In yet another embodiment, a test case selected by a user from the test cases corresponding to the test functions is used as the core test case group corresponding to the test functions. The method can include judging whether each test case is a core test case according to test experience of a tester. And further, each core test case is subjected to the corresponding test function to obtain a core test case group corresponding to the test function.
In order to facilitate the acceleration of the test process and improve the test accuracy, the priority of the test case is more in line with the actual test application of the module. Another functional test method is also provided in the present disclosure.
Fig. 2 is a flowchart of another functional test method according to an exemplary embodiment, and as shown in fig. 2, the functional test method 20 includes the following steps S21 to S24.
In step S21, a test function to be tested is determined, and a test case group corresponding to the test function is called.
In step S22, a test module corresponding to the test function is determined, and priorities of each test case in the test case group corresponding to the test module are determined.
In step S23, the test functions are tested piece by piece based on the priorities of the test cases in the test modules.
In the present disclosure, the implementation manners of step S21 to step S23 are the same as the implementation manners of step S11 to step S13 in the distance determining method 10, and specific reference may be made to the related descriptions of the above embodiments, which are not repeated here.
In step S24, the priorities of the test cases corresponding to the test modules are dynamically adjusted based on the test results of executing each test case in the test case group.
In the embodiment of the disclosure, because of factors such as system upgrade or continuous evolution and adjustment of functions of each module, vulnerabilities generated by each test module under different test functions may change, so that the use frequency of each test case in each test case group in each test module may change, which results in that the priority of each test case in each test module also changes. In order to facilitate improvement of key accuracy, the priority of each test case can be dynamically adjusted according to the historical test record of the test module and the current change after test, and the priority of each test case in the test module is reclassified through a clustering algorithm, so that when a certain test function of the test module is modified, the test and the verification problem can be more efficiently carried out.
Based on the same conception, the embodiment of the disclosure also provides a function test device.
It will be appreciated that, in order to implement the above-described functions, the functional test device provided in the embodiments of the present disclosure includes corresponding hardware structures and/or software modules that perform the respective functions. The disclosed embodiments may be implemented in hardware or a combination of hardware and computer software, in combination with the various example elements and algorithm steps disclosed in the embodiments of the disclosure. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application, but such implementation is not to be considered as beyond the scope of the embodiments of the present disclosure.
Fig. 3 is a block diagram of a functional test apparatus according to an exemplary embodiment, and as shown in fig. 3, the functional test apparatus 100 includes: call unit 110, match unit 120, test unit 130.
The calling unit 110 is configured to determine a test function to be tested, and call a test case group corresponding to the test function, where multiple test cases in the test case group correspond to different priorities in different test modules, and a frequency of use of a high-priority test case is greater than a frequency of use of a low-priority test case.
The matching unit 120 is configured to determine a test module corresponding to the test function, and determine priorities of each test case in the test case group corresponding to the test module.
The test unit 130 is configured to test the test functions strip by strip based on the priorities of the test cases in the test module.
In one embodiment, the matching unit 120 determines the priority of each test case in the test case group corresponding to the test module in the following manner: determining a core test case group corresponding to the test function, wherein the core test case group characterizes a plurality of test cases used for testing main functions of the test function in the test case group; counting the use frequency of each test case in the core test case group in a test module corresponding to the test function; and determining the priority of each test case in the core test case group in the test module corresponding to the test function according to the use frequency.
In another embodiment, the matching unit 120 determines the core test case group corresponding to the test function in the following manner: and the test cases meeting the test requirements in the test case results fed back by the MQS of the quality monitoring system aiming at the test cases corresponding to the test functions are used as core test case groups corresponding to the test functions.
In yet another embodiment, the matching unit 120 determines the core test case group corresponding to the test function in the following manner: and determining the test cases matched with the test functions through a back gate test, and taking the test cases matched with the test functions as core test case groups corresponding to the test functions.
In yet another embodiment, the matching unit 120 determines the core test case group corresponding to the test function in the following manner: and taking the test case selected by the user from the test cases corresponding to the test functions as a core test case group corresponding to the test functions.
In a further embodiment, the calling unit 110 is further configured to: based on the test results of executing each test case in the test case group, the priority of the test case corresponding to the test module is dynamically adjusted.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 4 is a block diagram illustrating an apparatus 200 for functional testing, according to an exemplary embodiment. For example, apparatus 200 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, exercise device, personal digital assistant, or the like.
Referring to fig. 4, the apparatus 200 may include one or more of the following components: a processing component 202, a memory 204, a power component 206, a multimedia component 208, an audio component 210, an input/output (I/O) interface 212, a sensor component 214, and a communication component 216.
The processing component 202 generally controls overall operation of the apparatus 200, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 202 may include one or more processors 220 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 202 can include one or more modules that facilitate interactions between the processing component 202 and other components. For example, the processing component 202 may include a multimedia module to facilitate interaction between the multimedia component 208 and the processing component 202.
The memory 204 is configured to store various types of data to support operations at the device 200. Examples of such data include instructions for any application or method operating on the device 200, contact data, phonebook data, messages, pictures, videos, and the like. The memory 204 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power component 206 provides power to the various components of the device 200. The power components 206 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 200.
The multimedia component 208 includes a screen between the device 200 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 208 includes a front-facing camera and/or a rear-facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 200 is in an operational mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 210 is configured to output and/or input audio signals. For example, the audio component 210 includes a Microphone (MIC) configured to receive external audio signals when the device 200 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 204 or transmitted via the communication component 216. In some embodiments, audio component 210 further includes a speaker for outputting audio signals.
The I/O interface 212 provides an interface between the processing assembly 202 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 214 includes one or more sensors for providing status assessment of various aspects of the apparatus 200. For example, the sensor assembly 214 may detect the on/off state of the appliance 200, the relative positioning of the components, such as the display and keypad of the device 200, the sensor assembly 214 may also detect a change in position of the device 200 or a component of the device 200, the presence or absence of user contact with the device 200, the orientation or acceleration/deceleration of the device 200, and a change in temperature of the device 200. The sensor assembly 214 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 214 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 214 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 216 is configured to facilitate communication between the apparatus 200 and other devices in a wired or wireless manner. The device 200 may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In one exemplary embodiment, the communication component 216 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 216 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 200 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for performing any of the above-described functional test methods.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 204, comprising instructions executable by processor 220 of apparatus 200 to perform any of the functional test methods described above. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
It is further understood that the term "plurality" in this disclosure means two or more, and other adjectives are similar thereto. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is 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 although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, 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 adaptations, 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 is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (12)
1. A functional test method, characterized in that the functional test method comprises:
determining a test function to be tested, and calling a test case group corresponding to the test function, wherein a plurality of test cases in the test case group correspond to different priorities in different test modules, and the use frequency of a high-priority test case is greater than that of a low-priority test case;
determining a test module corresponding to the test function, and determining the priority of each test case in the test case group corresponding to the test module;
testing the test functions one by one based on the priorities of the test cases in the test module;
the determining the priority of each test case in the test case group corresponding to the test module includes:
determining a core test case group corresponding to the test function, wherein the core test case group characterizes a plurality of test cases used for testing main functions of the test function in the test case group;
counting the use frequency of each test case in the core test case group in a test module corresponding to the test function;
and determining the priority of each test case in the core test case group in the test module corresponding to the test function according to the use frequency.
2. The method for testing functions according to claim 1, wherein the determining the core test case group corresponding to the test function includes:
and taking the test cases meeting the test requirements in the test case results fed back by the MQS of the quality monitoring system aiming at the test cases corresponding to the test functions as core test case groups corresponding to the test functions.
3. The method of claim 1, wherein the determining the core test case group corresponding to the test function comprises:
and determining the test cases matched with the test functions through a back gate test, and taking the test cases matched with the test functions as core test case groups corresponding to the test functions.
4. The method for testing functions according to claim 1, wherein the determining the core test case group corresponding to the test function includes:
and taking the test case selected by the user from the test cases corresponding to the test functions as a core test case group corresponding to the test functions.
5. The function test method according to claim 1, characterized in that the function test method further comprises:
and dynamically adjusting the priority of the test case corresponding to the test module based on the test result of executing each test case in the test case group.
6. A functional test device, characterized in that the functional test device comprises:
the calling unit is used for determining a test function to be tested and calling a test case group corresponding to the test function, wherein a plurality of test cases in the test case group correspond to different priorities in different test modules, and the use frequency of the high-priority test cases is greater than that of the low-priority test cases;
the matching unit is used for determining a test module corresponding to the test function and determining the priority corresponding to each test case in the test case group and the matching test module;
the testing unit is used for testing the testing functions one by one based on the priorities of the testing cases in the testing module;
the matching unit determines the priority of each test case in the test case group corresponding to the test module by adopting the following mode:
determining a core test case group corresponding to the test function, wherein the core test case group characterizes a plurality of test cases used for testing main functions of the test function in the test case group;
counting the use frequency of each test case in the core test case group in a test module corresponding to the test function;
and determining the priority of each test case in the core test case group in the test module corresponding to the test function according to the use frequency.
7. The function test device according to claim 6, wherein the matching unit determines the core test case group corresponding to the test function by:
and taking the test cases meeting the test requirements in the test case results fed back by the MQS of the quality monitoring system aiming at the test cases corresponding to the test functions as core test case groups corresponding to the test functions.
8. The apparatus of claim 6, wherein the matching unit determines the core test case group corresponding to the test function by:
and determining the test cases matched with the test functions through a back gate test, and taking the test cases matched with the test functions as core test case groups corresponding to the test functions.
9. The function test device according to claim 6, wherein the matching unit determines the core test case group corresponding to the test function by:
and taking the test case selected by the user from the test cases corresponding to the test functions as a core test case group corresponding to the test functions.
10. The function test device according to claim 6, wherein the calling unit is further configured to:
and dynamically adjusting the priority of the test case corresponding to the test module based on the test result of executing each test case in the test case group.
11. A functional test device, comprising:
a memory for storing instructions; and
a processor; instructions for invoking the memory storage perform the functional test method of any of claims 1-5.
12. A computer readable storage medium storing computer executable instructions which, when executed by a processor, perform the functional test method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010348165.3A CN111611156B (en) | 2020-04-28 | 2020-04-28 | Function test method, function test device, and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010348165.3A CN111611156B (en) | 2020-04-28 | 2020-04-28 | Function test method, function test device, and computer-readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111611156A CN111611156A (en) | 2020-09-01 |
| CN111611156B true CN111611156B (en) | 2024-01-30 |
Family
ID=72204543
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010348165.3A Active CN111611156B (en) | 2020-04-28 | 2020-04-28 | Function test method, function test device, and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111611156B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101227350A (en) * | 2008-02-03 | 2008-07-23 | 中兴通讯股份有限公司 | System for parallel executing automatization test based on priority level scheduling and method thereof |
| WO2014049104A1 (en) * | 2012-09-27 | 2014-04-03 | Siemens Aktiengesellschaft | A method, apparatus and system for optimizing test cases in fuzz testing |
| CN108073505A (en) * | 2016-11-17 | 2018-05-25 | 富士通株式会社 | Data processing equipment and data processing method |
| CN108388509A (en) * | 2018-02-07 | 2018-08-10 | 平安科技（深圳）有限公司 | A kind of method for testing software, computer readable storage medium and terminal device |
-
2020
- 2020-04-28 CN CN202010348165.3A patent/CN111611156B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101227350A (en) * | 2008-02-03 | 2008-07-23 | 中兴通讯股份有限公司 | System for parallel executing automatization test based on priority level scheduling and method thereof |
| WO2014049104A1 (en) * | 2012-09-27 | 2014-04-03 | Siemens Aktiengesellschaft | A method, apparatus and system for optimizing test cases in fuzz testing |
| CN108073505A (en) * | 2016-11-17 | 2018-05-25 | 富士通株式会社 | Data processing equipment and data processing method |
| CN108388509A (en) * | 2018-02-07 | 2018-08-10 | 平安科技（深圳）有限公司 | A kind of method for testing software, computer readable storage medium and terminal device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111611156A (en) | 2020-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109359056B (en) | Application program testing method and device | |
| US20160029419A1 (en) | Methods and devices for connecting to wireless network | |
| CN111274131A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN108427618B (en) | Method and device for determining stuck state and computer readable storage medium | |
| CN116069612A (en) | Abnormality positioning method and device and electronic equipment | |
| CN112256563A (en) | Android application stability testing method and device, electronic equipment and storage medium | |
| US10671827B2 (en) | Method and device for fingerprint verification | |
| CN111611156B (en) | Function test method, function test device, and computer-readable storage medium | |
| CN106446827B (en) | Iris recognition function detection method and device | |
| CN112333233B (en) | Event information reporting method and device, electronic equipment and storage medium | |
| CN108427582B (en) | Method and device for determining stuck state and computer readable storage medium | |
| CN111104014B (en) | Method, device, terminal and storage medium for starting application program | |
| CN109981406B (en) | Test method, device, system and computer readable storage medium | |
| CN113138888A (en) | Function detection method and device, electronic equipment and storage medium | |
| CN107193622B (en) | Code compiling processing method and device and terminal | |
| CN107526683B (en) | Method and device for detecting functional redundancy of application program and storage medium | |
| CN111198800B (en) | CPU occupancy rate detection method, CPU occupancy rate detection device and electronic equipment | |
| CN113645695B (en) | Method, device and storage medium for processing radio resource control link configuration signaling | |
| CN112363917B (en) | Application program debugging exception processing method and device, electronic equipment and medium | |
| CN113206772B (en) | Method, device, equipment, medium and product for judging correctness of response message | |
| CN111104297B (en) | Multi-process data dotting method and device, electronic equipment and storage medium | |
| CN117149742A (en) | Data migration testing method and electronic equipment | |
| CN116127525A (en) | Data processing method, device, equipment, storage medium and product | |
| CN117093486A (en) | Interface testing method, device, equipment and storage medium | |
| CN114579433A (en) | Page parameter checking method, device, electronic equipment, medium and program product |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |