CN109062802B - Software testing method, computer readable storage medium and terminal equipment - Google Patents
Software testing method, computer readable storage medium and terminal equipment Download PDFInfo
- Publication number
- CN109062802B CN109062802B CN201810915660.0A CN201810915660A CN109062802B CN 109062802 B CN109062802 B CN 109062802B CN 201810915660 A CN201810915660 A CN 201810915660A CN 109062802 B CN109062802 B CN 109062802B
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- software
- module
- cases
- 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
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/3688—Test management for test execution, e.g. scheduling of test suites
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
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 invention belongs to the technical field of computers, and particularly relates to a software testing method based on big data analysis, a computer readable storage medium and terminal equipment. The method comprises the steps of obtaining a function module list of software to be tested from a preset configuration file, and reading module identifiers of all function modules of the software to be tested from the function module list; respectively inquiring set identifiers of test case sets corresponding to the functional modules in a preset test case set list according to the module identifiers; respectively inquiring storage addresses corresponding to each test case set in a preset address list according to the set identifier; respectively reading test case sets corresponding to each functional module from the storage addresses; and testing each functional module of the software to be tested by using the test cases in the test case set. The test cases corresponding to each piece of software do not need to be rewritten, so that the time for writing the cases is greatly reduced.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to a software testing method, a computer readable storage medium and terminal equipment.
Background
In the traditional software test, the tests among the software are mutually independent, and the test cases corresponding to each software are required to be rewritten for testing the software, so that a large amount of manpower and material resources are required to be consumed in the test mode, and the test efficiency is extremely low.
Disclosure of Invention
In view of the above, the embodiments of the present invention provide a software testing method, a computer readable storage medium and a terminal device, so as to solve the problem of extremely low testing efficiency of the conventional software testing method.
A first aspect of an embodiment of the present invention provides a software testing method, which may include:
acquiring a function module list of software to be tested from a preset configuration file, and reading module identifiers of all function modules of the software to be tested from the function module list;
respectively inquiring set identifiers of test case sets corresponding to the functional modules in a preset test case set list according to the module identifiers;
respectively inquiring storage addresses corresponding to each test case set in a preset address list according to the set identifier;
respectively reading test case sets corresponding to each functional module from the storage addresses;
and testing each functional module of the software to be tested by using the test cases in the test case set.
A second aspect of embodiments of the present invention provides a computer-readable storage medium storing computer-readable instructions that when executed by a processor perform the steps of:
acquiring a function module list of software to be tested from a preset configuration file, and reading module identifiers of all function modules of the software to be tested from the function module list;
respectively inquiring set identifiers of test case sets corresponding to the functional modules in a preset test case set list according to the module identifiers;
respectively inquiring storage addresses corresponding to each test case set in a preset address list according to the set identifier;
respectively reading test case sets corresponding to each functional module from the storage addresses;
and testing each functional module of the software to be tested by using the test cases in the test case set.
A third aspect of an embodiment of the present invention provides a terminal device, including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor implementing the following steps when executing the computer readable instructions:
acquiring a function module list of software to be tested from a preset configuration file, and reading module identifiers of all function modules of the software to be tested from the function module list;
respectively inquiring set identifiers of test case sets corresponding to the functional modules in a preset test case set list according to the module identifiers;
respectively inquiring storage addresses corresponding to each test case set in a preset address list according to the set identifier;
respectively reading test case sets corresponding to each functional module from the storage addresses;
and testing each functional module of the software to be tested by using the test cases in the test case set.
Compared with the prior art, the embodiment of the invention has the beneficial effects that: the embodiment of the invention is based on modularized software development and test thought, in the modularized software development, the software is formed by combining a plurality of functional modules, and the functional modules can be multiplexed in different software. In the embodiment of the invention, the characteristic of modularized software development is fully considered, the test case sets corresponding to all the functional modules are preset, the functional module list of the software to be tested is obtained through the configuration file when the software is tested, so that all the functional modules forming the software are determined, then the storage addresses of the test case sets corresponding to the functional modules are queried, the test case sets are read, and finally the test cases in the test case sets are used for testing all the functional modules of the software to be tested. Because each functional module can be multiplexed in different software, the test case set corresponding to each functional module can be multiplexed in the software test process by the modularized test method, and the test case corresponding to each software does not need to be rewritten, so that the time for writing the case is greatly reduced, and the test efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of an embodiment of a software testing method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a functional module repository;
FIG. 3 is a schematic diagram of a correspondence between functional modules and a test case set;
FIG. 4 is a schematic flow chart of selecting a preferred test case for testing;
FIG. 5 is a block diagram of an embodiment of a software testing apparatus according to an embodiment of the present invention;
fig. 6 is a schematic block diagram of a terminal device in an embodiment of the present invention.
Detailed Description
In order to make the objects, features and advantages of the present invention more comprehensible, the technical solutions in the embodiments of the present invention are described in detail below with reference to the accompanying drawings, and it is apparent that the embodiments described below are only some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Referring to fig. 1, an embodiment of a software testing method according to an embodiment of the present invention may include:
step S101, a function module list of the software to be tested is obtained from a preset configuration file, and module identifiers of all the function modules of the software to be tested are read from the function module list.
The invention is based on the modularized software development thought, namely, the modularized software development is to divide the software into a plurality of mutually independent modules according to each function, each module only realizes a specific function, and all the functions required by the software can be realized by combining the modules. In the development process of new software, each functional module of the previous software can be reused, so that the workload is greatly reduced.
As shown in fig. 2, in this embodiment, a function module resource library is pre-constructed, and each independent function module is stored in the function module resource library for direct call when new software is developed. Since different software may have some functions that are identical and some functions that are different, there may be some identical functional modules and some different functional modules.
Accordingly, as shown in fig. 3, for each functional module, a set of test cases corresponding to each functional module is preset, and these test case sets are all stored in a test case resource library.
Each test case set includes a plurality of test cases, where the test cases are used to test the functional module corresponding to the test cases, for example, all test cases in the test case set 1 are used to test the functional module 1, all test cases in the test case set 2 are used to test the functional module 2, … …, and all test cases in the test case set N are used to test the functional module N.
For the software to be tested, a function module list is set in advance for the software to be tested.
Specifically, firstly, the called frequency of each function module in the function module resource library in the historical software development process is obtained, then each function module is displayed on a preset user interaction interface, the function modules are arranged according to the sequence from high to low of the called frequency, finally, the selection of each function module by a user through the user interaction interface is received, and the module identification of the selected function module is added into the function module list.
The module identifier is a unique identifier of a functional module, and each functional module has only one module identifier.
Step S102, respectively inquiring the set identifiers of the test case sets corresponding to the functional modules in a preset test case set list according to the module identifiers.
And the corresponding relation between each functional module and each test case set is recorded in the test case set list, wherein each functional module is represented by a module identifier of the functional module, and each test case set is represented by a set identifier of the functional module. And determining the set identifier of the test case set corresponding to each functional module of the software to be tested by inquiring the table.
Step S103, respectively inquiring storage addresses corresponding to the test case sets in a preset address list according to the set identifier.
The list of addresses shown is shown in the following table:
| test case set | Memory address |
| Test case set 1 | Memory address 1: [ StartAddr1, endAddr1 ]] |
| Test case set 2 | Memory address 2: [ StartAddr2, endAddr2 ]] |
| Test case set 3 | Storage address 3: [ StartAddr3, endAddr3] |
| …… | …… |
And the address list records the corresponding relation between each test case set and the storage address thereof, wherein each test case set is represented by the set identifier thereof. Each memory address is denoted as [ StartAddr, endAddr ] and represents the memory space between starting from the start address StartAddr and going to the end address EndAddr. For example, the memory space between the start address StartAddr1 and the end address EndAddr1 can be known from the test case set 1 by looking up a table.
Step S104, respectively reading the test case sets corresponding to the functional modules from the storage addresses.
And step 105, testing each functional module of the software to be tested by using the test cases in the test case set.
In this embodiment, all cases in the test case set may be sequentially executed, so as to implement an integrated test for each functional module of the software to be tested.
However, the test mode is based on sufficient test time, but under the actual test situation, the test time is often very intense, and it is difficult to test all the test cases, so the steps shown in fig. 4 can be preferably adopted for testing:
step S401, acquiring history test records of each functional module.
In this embodiment, each test performed on each functional module is saved to a preset history test record, so as to perform statistical analysis later.
And step S402, respectively calculating the test priority index of each test case in the test case set according to the history test record.
Specifically, the test priority index of each test case in the test case set may be calculated according to the following formula:
wherein M is the serial number of the functional module, M is 1-1, M is the total number of the functional modules of the software to be tested, N is the serial number of the test case, and N is 1-1, N is less than or equal to N m ，N m The mth test case set is the test case set corresponding to the mth functional module of the software to be tested, T is the serial number of the test times, and T is more than or equal to 1 and less than or equal to T m,n ，T m,n To use the nth test case in the mth test case set for the number of times of testing, bugNum m,n,t To use the nth test case in the mth test case setThe number of defects found when the test case performs the t-th test, testPeriod m,n,t To test duration at the time of the t-th test using the nth test case in the mth test case set, codeLine m Impdieg is the number of code lines of the mth functional module m,n And the test priority index of the nth test case in the mth test case set.
Step S403, selecting TS test cases with highest test priority indexes from the test case set as preferred test cases.
Wherein TS is an integer greater than 0.
Specifically, each test case in the test case set may be arranged as the following test case sequence according to the order of the test priority index from high to low:
TestCaseSet＝{TestCase 1 ,TestCase 2 ,......,TestCase sq ,......,TestCase CaseNum }
wherein sq is the sequence number of test cases arranged from high to low according to the test priority index, 1.ltoreq.sq.ltoreq. CaseNum, caseNum is the total number of test cases in the test case set, and
TestCase sq impdieg for test cases arranged in the sq th bit from high to low according to the test priority index sq ≥ImpDeg sq+1 ，ImpDeg sq For TestCase sq Is a test priority index of (c).
Then, acquiring the total testing duration of the software to be tested, and determining TS values meeting the following formulas as the number of the preferred test cases:
wherein T is the serial number of the test times, and T is more than or equal to 1 and less than or equal to T sq ，T sq To test the number of times using the sq th test case, testperiod sq,t Ongoing for the sq test caseThe test duration at the t-th test is the total test duration, which can be set in advance by a tester according to actual conditions, for example, can be set to 30 minutes, 1 hour, 2 hours or other values.
And finally, selecting the front TS test cases from the test case sequence as the preferred test cases.
And step S404, testing each functional module of the software to be tested by using the preferred test case.
The optimal test cases selected through the process are the optimal test cases determined by comprehensively considering the number of the found software defects, the test duration, the code quantity and other factors, and the optimal test effect can be obtained in a limited test time through the optimal test cases.
In summary, the embodiment of the invention is based on the modularized software development and test idea, in the modularized software development, the software is formed by combining a plurality of functional modules, and the functional modules can be multiplexed in different software. In the embodiment of the invention, the characteristic of modularized software development is fully considered, the test case sets corresponding to all the functional modules are preset, the functional module list of the software to be tested is obtained through the configuration file when the software is tested, so that all the functional modules forming the software are determined, then the storage addresses of the test case sets corresponding to the functional modules are queried, the test case sets are read, and finally the test cases in the test case sets are used for testing all the functional modules of the software to be tested. Because each functional module can be multiplexed in different software, the test case set corresponding to each functional module can be multiplexed in the software test process by the modularized test method, and the test case corresponding to each software does not need to be rewritten, so that the time for writing the case is greatly reduced, and the test efficiency is improved.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.
Corresponding to a software testing method described in the above embodiments, fig. 5 shows a block diagram of an embodiment of a software testing apparatus according to an embodiment of the present invention.
In this embodiment, a software testing apparatus may include:
a module list obtaining module 501, configured to obtain a function module list of software to be tested from a preset configuration file, and read module identifiers of each function module of the software to be tested from the function module list;
the case set query module 502 is configured to query set identifiers of test case sets corresponding to each functional module in a preset test case set list according to the module identifiers;
a storage address query module 503, configured to query storage addresses corresponding to each test case set in a preset address list according to the set identifier;
a case set reading module 504, configured to read test case sets corresponding to the respective function modules from the storage addresses respectively;
and the functional module testing module 505 is configured to test each functional module of the software to be tested by using the test cases in the test case set.
Further, the functional module testing module may include:
the history test record acquisition unit is used for acquiring the history test record of each functional module;
the priority index calculation unit is used for calculating the test priority index of each test case in the test case set according to the history test record;
the optimal test case selection unit is used for selecting TS (transport stream) test cases with highest test priority indexes from the test case set as optimal test cases, wherein TS is an integer greater than 0;
and the functional module testing unit is used for testing each functional module of the software to be tested by using the preferred test case.
Further, the priority index calculating unit may include:
the priority index calculation subunit is configured to calculate test priority indexes of each test case in the test case set according to the following methods:
wherein M is the serial number of the functional module, M is 1-1, M is the total number of the functional modules of the software to be tested, N is the serial number of the test case, and N is 1-1, N is less than or equal to N m ，N m The mth test case set is the test case set corresponding to the mth functional module of the software to be tested, T is the serial number of the test times, and T is more than or equal to 1 and less than or equal to T m,n ，T m,n To use the nth test case in the mth test case set for the number of times of testing, bugNum m,n,t To use the nth test case in the mth test case set to perform the number of defects found at the t-th test, testperiod m,n,t To test duration at the time of the t-th test using the nth test case in the mth test case set, codeLine m Impdieg is the number of code lines of the mth functional module m,n And the test priority index of the nth test case in the mth test case set.
Further, the preferred test case selection unit may include:
the test case sequence construction subunit is configured to arrange each test case in the test case set into the following test case sequence according to the order of the test priority index from high to low:
TestCaseSet＝{TestCase 1 ,TestCase 2 ,......,TestCase sq ,......,TestCase CaseNum }
wherein sq is the test case according to the testThe test priority index is the sequence number from high to low, 1.ltoreq.sq.ltoreq. CaseNum, caseNum is the total number of the test cases in the test case set, and
TestCase sq impdieg for test cases arranged in the sq th bit from high to low according to the test priority index sq ≥ImpDeg sq+1 ，ImpDeg sq For TestCase sq Is a test priority index of (2);
a test total duration obtaining subunit, configured to obtain a test total duration for testing the software to be tested;
the case number determining subunit is configured to determine, as the number of the preferred test cases, a TS value satisfying the following formula:
wherein T is the serial number of the test times, and T is more than or equal to 1 and less than or equal to T sq ，T sq To test the number of times using the sq th test case, testperiod sq,t And (3) testing duration of the sq test case when the t test is carried out, wherein TestPeriodLimit is the total testing duration.
And the preferred test case selection subunit is used for selecting the first TS test cases from the test case sequence as the preferred test cases.
Further, the software testing device may further include:
the calling frequency acquisition module is used for acquiring the called frequency of each function module in a preset function module resource library in the development process of historical software;
the interactive display module is used for displaying each functional module on a preset user interactive interface, and the functional modules are arranged in sequence according to the frequency of being called from high to low;
and the selection receiving module is used for receiving the selection of each functional module by a user through the user interaction interface and adding the module identification of the selected functional module into the functional module list.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described apparatus, modules and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Fig. 6 shows a schematic block diagram of a terminal device according to an embodiment of the present invention, and for convenience of explanation, only a portion related to the embodiment of the present invention is shown.
In this embodiment, the terminal device 6 may be a computing device such as a desktop computer, a notebook computer, a palm computer, and a cloud server. The terminal device 6 may comprise: a processor 60, a memory 61, and computer readable instructions 62 stored in the memory 61 and executable on the processor 60, such as computer readable instructions for performing the software testing method described above. The processor 60, when executing the computer readable instructions 62, implements the steps of the various software testing method embodiments described above, such as steps S101 through S105 shown in fig. 1. Alternatively, the processor 60, when executing the computer readable instructions 62, performs the functions of the modules/units of the apparatus embodiments described above, such as the functions of modules 501-505 of fig. 5.
Illustratively, the computer readable instructions 62 may be partitioned into one or more modules/units that are stored in the memory 61 and executed by the processor 60 to complete the present invention. The one or more modules/units may be a series of computer readable instruction segments capable of performing specific functions describing the execution of the computer readable instructions 62 in the terminal device 6.
The processor 60 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 61 may be an internal storage unit of the terminal device 6, such as a hard disk or a memory of the terminal device 6. The memory 61 may be an external storage device of the terminal device 6, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device 6. Further, the memory 61 may also include both an internal storage unit and an external storage device of the terminal device 6. The memory 61 is used for storing the computer readable instructions as well as other instructions and data required by the terminal device 6. The memory 61 may also be used for temporarily storing data that has been output or is to be output.
The functional units in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution contributing to the prior art or in the form of a software product stored in a storage medium, comprising a number of computer readable instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing computer readable instructions.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (6)
1. A method of testing software, comprising:
acquiring a function module list of software to be tested from a preset configuration file, and reading module identifiers of all function modules of the software to be tested from the function module list;
respectively inquiring set identifiers of test case sets corresponding to the functional modules in a preset test case set list according to the module identifiers;
respectively inquiring storage addresses corresponding to each test case set in a preset address list according to the set identifier;
respectively reading test case sets corresponding to each functional module from the storage addresses;
acquiring historical test records of all functional modules;
respectively calculating the test priority index of each test case in the test case set according to the history test record:
wherein M is the serial number of the functional module, M is more than or equal to 1 and less than or equal to M, M is the total number of the functional modules of the software to be tested,n is the serial number of the test case, N is more than or equal to 1 and less than or equal to N m ，N m The mth test case set is the test case set corresponding to the mth functional module of the software to be tested, T is the serial number of the test times, and T is more than or equal to 1 and less than or equal to T m,n ，T m,n To use the nth test case in the mth test case set for the number of times of testing, bugNum m,n,t To use the nth test case in the mth test case set to perform the number of defects found at the t-th test, testperiod m,n,t To test duration at the time of the t-th test using the nth test case in the mth test case set, codeLine m Impdieg is the number of code lines of the mth functional module m,n A test priority index for an nth test case in the mth test case set;
selecting TS test cases with highest test priority indexes from the test case set as preferred test cases, wherein TS is an integer greater than 0;
and testing each functional module of the software to be tested by using the preferred test case.
2. The software testing method according to claim 1, wherein selecting the TS test cases with the highest test priority index from the test case set as the preferred test cases comprises:
the test cases in the test case set are arranged into the following test case sequences according to the order of the test priority indexes from high to low:
TestCaseSet＝{TestCase 1 ,TestCase 2 ,......,TestCase sq ,......,TestCase CaseNum }
wherein sq is the sequence number of test cases arranged from high to low according to the test priority index, 1.ltoreq.sq.ltoreq. CaseNum, caseNum is the total number of test cases in the test case set, and
TestCase sq is pressed byImpdieg is performed according to test cases in which the test priority index is arranged in the sq th bit from high to low sq ≥ImpDeg sq+1 ，ImpDeg sq For TestCase sq Is a test priority index of (2);
acquiring the total testing duration of the software to be tested;
determining TS values meeting the following formula as the number of the preferred test cases:
wherein T is the serial number of the test times, and T is more than or equal to 1 and less than or equal to T sq ，T sq To test the number of times using the sq th test case, testperiod sq,t The test period of the stPeriodLimit is the total test period when the stth test is carried out for the stth test case;
and selecting the first TS test cases from the test case sequence as the preferred test cases.
3. The software testing method according to any one of claims 1 to 2, wherein the setting process of the function module list includes:
acquiring the called frequency of each function module in a preset function module resource library in the development process of historical software;
displaying each functional module on a preset user interaction interface, and arranging the functional modules according to the sequence from high to low of the called frequency;
and receiving the selection of the user on each functional module through the user interaction interface, and adding the module identification of the selected functional module into the functional module list.
4. A computer readable storage medium storing computer readable instructions which, when executed by a processor, implement the steps of the software testing method of any one of claims 1 to 3.
5. A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, wherein the processor, when executing the computer readable instructions, performs the steps of:
acquiring a function module list of software to be tested from a preset configuration file, and reading module identifiers of all function modules of the software to be tested from the function module list;
respectively inquiring set identifiers of test case sets corresponding to the functional modules in a preset test case set list according to the module identifiers;
respectively inquiring storage addresses corresponding to each test case set in a preset address list according to the set identifier;
respectively reading test case sets corresponding to each functional module from the storage addresses;
acquiring historical test records of all functional modules;
respectively calculating the test priority index of each test case in the test case set according to the history test record:
wherein M is the serial number of the functional module, M is 1-1, M is the total number of the functional modules of the software to be tested, N is the serial number of the test case, and N is 1-1, N is less than or equal to N m ，N m The mth test case set is the test case set corresponding to the mth functional module of the software to be tested, T is the serial number of the test times, and T is more than or equal to 1 and less than or equal to T m,n ，T m,n To use the nth test case in the mth test case set for the number of times of testing, bugNum m,n,t Missing found for the t-th test using the nth test case in the mth test case setNumber of notches, testPeriod m,n,t To test duration at the time of the t-th test using the nth test case in the mth test case set, codeLine m Impdieg is the number of code lines of the mth functional module m,n A test priority index for an nth test case in the mth test case set;
selecting TS test cases with highest test priority indexes from the test case set as preferred test cases, wherein TS is an integer greater than 0;
and testing each functional module of the software to be tested by using the preferred test case.
6. The terminal device according to claim 5, wherein selecting, from the set of test cases, the TS test cases with the highest test priority index as the preferred test cases includes:
the test cases in the test case set are arranged into the following test case sequences according to the order of the test priority indexes from high to low:
TestCaseSet＝{TestCase 1 ,TestCase 2 ,......,TestCase sq ,......,TestCase CaseNum }
wherein sq is the sequence number of test cases arranged from high to low according to the test priority index, 1.ltoreq.sq.ltoreq. CaseNum, caseNum is the total number of test cases in the test case set, and
TestCase sq impdieg for test cases arranged in the sq th bit from high to low according to the test priority index sq ≥ImpDeg sq+1 ，ImpDeg sq For TestCase sq Is a test priority index of (2);
acquiring the total testing duration of the software to be tested;
determining TS values meeting the following formula as the number of the preferred test cases:
wherein T is the serial number of the test times, and T is more than or equal to 1 and less than or equal to T sq ，T sq To test the number of times using the sq th test case, testperiod sq,t The test period of the stPeriodLimit is the total test period when the stth test is carried out for the stth test case;
and selecting the first TS test cases from the test case sequence as the preferred test cases.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810915660.0A CN109062802B (en) | 2018-08-13 | 2018-08-13 | Software testing method, computer readable storage medium and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810915660.0A CN109062802B (en) | 2018-08-13 | 2018-08-13 | Software testing method, computer readable storage medium and terminal equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109062802A CN109062802A (en) | 2018-12-21 |
| CN109062802B true CN109062802B (en) | 2023-06-09 |
Family
ID=64683769
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810915660.0A Active CN109062802B (en) | 2018-08-13 | 2018-08-13 | Software testing method, computer readable storage medium and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109062802B (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109815142B (en) * | 2019-01-09 | 2022-04-15 | 珠海天燕科技有限公司 | Product testing method and device |
| CN109800169A (en) * | 2019-01-24 | 2019-05-24 | 拉扎斯网络科技（上海）有限公司 | Test case obtaining method and device, readable storage medium and electronic equipment |
| CN110046091B (en) * | 2019-03-12 | 2023-10-20 | 创新先进技术有限公司 | Automatic test method and device |
| CN110069397A (en) * | 2019-03-15 | 2019-07-30 | 深圳壹账通智能科技有限公司 | Function test method, device, computer equipment and storage medium |
| CN110188034A (en) * | 2019-05-10 | 2019-08-30 | 广州高鸿信息科技有限公司 | A kind of method for testing software based on information sharing |
| CN110262961A (en) * | 2019-05-21 | 2019-09-20 | 深圳壹账通智能科技有限公司 | Test method, device, storage medium and the terminal device of Workflow Management System |
| CN110232008A (en) * | 2019-05-31 | 2019-09-13 | 口碑(上海)信息技术有限公司 | A kind of acquisition method and device of application performance data |
| CN112231229B (en) * | 2020-11-09 | 2024-06-28 | 恩亿科(北京)数据科技有限公司 | Web UI automatic test method, system, electronic equipment and readable storage medium |
| CN113238930B (en) * | 2021-04-26 | 2024-05-31 | 南方电网电力科技股份有限公司 | Method and device for testing software system, terminal equipment and storage medium |
| CN113254337A (en) * | 2021-05-24 | 2021-08-13 | 北京创源微致软件有限公司 | Software function testing system, method and server |
| CN113760747A (en) * | 2021-06-03 | 2021-12-07 | 京东科技控股股份有限公司 | Software testing method, device, equipment, storage medium and program product |
| CN113448867B (en) * | 2021-07-16 | 2022-08-16 | 谢靖 | Software pressure testing method and device |
| CN113626409B (en) * | 2021-08-06 | 2023-08-15 | 百度在线网络技术（北京）有限公司 | Test data processing method, device, equipment and storage medium |
| CN113760771A (en) * | 2021-09-14 | 2021-12-07 | 中国农业银行股份有限公司 | Execution method and device of integrated test case |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102063374A (en) * | 2011-01-07 | 2011-05-18 | 南京大学 | Method for selecting regression test case for clustering with semi-supervised information |
| CN108182142A (en) * | 2016-12-08 | 2018-06-19 | 武汉安天信息技术有限责任公司 | Test resource integration method, system and function test method, system |
| CN108255653A (en) * | 2018-01-02 | 2018-07-06 | 深圳壹账通智能科技有限公司 | The test method and its terminal of a kind of product |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130041613A1 (en) * | 2011-08-10 | 2013-02-14 | International Business Machines Corporation | Generating a test suite for broad coverage |
-
2018
- 2018-08-13 CN CN201810915660.0A patent/CN109062802B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102063374A (en) * | 2011-01-07 | 2011-05-18 | 南京大学 | Method for selecting regression test case for clustering with semi-supervised information |
| CN108182142A (en) * | 2016-12-08 | 2018-06-19 | 武汉安天信息技术有限责任公司 | Test resource integration method, system and function test method, system |
| CN108255653A (en) * | 2018-01-02 | 2018-07-06 | 深圳壹账通智能科技有限公司 | The test method and its terminal of a kind of product |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109062802A (en) | 2018-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109062802B (en) | Software testing method, computer readable storage medium and terminal equipment | |
| CN108694123B (en) | Regression testing method, computer readable storage medium and terminal equipment | |
| EP3825861A2 (en) | Method and apparatus of user clustering, computer device | |
| CN108388509B (en) | Software testing method, computer readable storage medium and terminal equipment | |
| CN109033165B (en) | Data display method, computer readable storage medium and terminal equipment | |
| CN113407536A (en) | Method and device for associating table data, terminal equipment and medium | |
| WO2020233347A1 (en) | Test method and apparatus for workflow management system, storage medium and terminal device | |
| Hunold et al. | Reproducible MPI micro-benchmarking isn't as easy as you think | |
| CN112948233A (en) | Interface testing method, device, terminal equipment and medium | |
| CN104765792A (en) | Dimension data storing method, device and system | |
| CN112328882B (en) | Information recommendation method, device, terminal equipment and storage medium | |
| CN112711739B (en) | Data processing method and device, server and storage medium | |
| CN109062638B (en) | System component display method, computer readable storage medium and terminal device | |
| CN116841811A (en) | Chip register test method and device, electronic equipment and storage medium | |
| CN110851437A (en) | Storage method, device and equipment | |
| CN105761119B (en) | Online number distribution calculation method and device | |
| CN111158994B (en) | Method and device for testing pressing performance | |
| CN114661753A (en) | Call bill retrieval method and device | |
| CN116795723B (en) | Chain unit test processing method and device and computer equipment | |
| CN112433932B (en) | Data processing method and device and computer storage medium | |
| CN109783331B (en) | Database cluster pressure testing method and device | |
| CN111752821B (en) | Method, device, computer equipment and readable storage medium for packet pressure measurement | |
| CN109086218B (en) | Automatic testing method, system and testing terminal based on ant colony algorithm | |
| CN115221057A (en) | Test data response time output method and device, medium and computer equipment | |
| CN108132946B (en) | Serialized data display method and device |
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 |