CN113238930B - Method and device for testing software system, terminal equipment and storage medium - Google Patents
Method and device for testing software system, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN113238930B CN113238930B CN202110452624.7A CN202110452624A CN113238930B CN 113238930 B CN113238930 B CN 113238930B CN 202110452624 A CN202110452624 A CN 202110452624A CN 113238930 B CN113238930 B CN 113238930B
- Authority
- CN
- China
- Prior art keywords
- test
- software system
- module
- functional module
- test case
- 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
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000012360 testing method Methods 0.000 claims abstract description 322
- 230000006870 function Effects 0.000 claims abstract description 57
- 238000010998 test method Methods 0.000 claims description 12
- 230000005856 abnormality Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 6
- 238000013461 design Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000007547 defect Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000000528 statistical test Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000000007 visual 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
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 application provides a method, a device, a terminal device and a storage medium for testing a software system, wherein the method comprises the steps of obtaining the software system to be tested and a test case set, the software system comprises at least one functional module, and the test case set comprises at least one test case; selecting test cases matched with the functions of each functional module, and executing the test cases matched with the functional modules in each functional module to obtain an execution result of each functional module; the execution result can reflect the execution condition of the test case on each functional module in the software system (namely, whether the test case can be correctly executed in the functional module in the software system) so as to determine whether the software system functions normally or not according to each execution condition, and the running capability and other related information, and determine whether the software system passes the test or not according to the information. The method does not need to be manually participated, and greatly improves the efficiency and the accuracy.
Description
Technical Field
The present application relates to the field of software system testing technologies, and in particular, to a method and apparatus for testing a software system, a terminal device, and a storage medium.
Background
With the continuous increase of the level of intelligence, a large number of software systems (such as power software systems) are emerging, and the software systems can automatically manage data, information and the like, for example, power grid dispatching can be automatically completed by adopting the power system software systems. In order to make the software system function, it is important to test the software system by determining that the software system can function normally and reliably.
However, software systems typically include a large number of functions and a complex testing process. At present, a manual test mode is usually adopted, but the method has low test efficiency, and the manual operation is easy to cause errors, so that the test accuracy is low.
Content of the application
In view of the above, the embodiments of the present application provide a method, an apparatus, a terminal device, and a storage medium for testing a software system, so as to overcome the problem of low testing efficiency and accuracy in the prior art.
In a first aspect, an embodiment of the present application provides a method for testing a software system, where the method includes:
acquiring a software system to be tested and a test case set, wherein the software system comprises at least one functional module, and the test case set comprises at least one test case;
Selecting test cases matched with the functions of each functional module;
Executing the test cases matched with the function modules in each function module to obtain an execution result of each function module;
and judging whether the software system passes the test or not according to each execution result.
In a second aspect, an embodiment of the present application provides a testing apparatus for a software system, including:
The information acquisition module is used for acquiring a software system to be tested and a test case set, wherein the software system comprises at least one functional module, and the test case set comprises at least one test case;
the use case selection module is used for selecting a test use case matched with the function of each functional module;
The case execution module is used for executing the test case matched with the case execution module in each functional module so as to obtain an execution result of each functional module;
and the system test judging module is used for judging whether the software system passes the test or not according to each execution result.
In a third aspect, an embodiment of the present application provides a terminal device, including: a memory; one or more processors coupled with the memory; one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to perform the method of testing a software system provided in the first aspect described above.
In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, where a program code is stored, where the program code is capable of being invoked by a processor to execute the test method of the software system provided in the first aspect.
The method, the device, the terminal equipment and the storage medium for testing the software system provided by the embodiment of the application firstly acquire the software system to be tested and a test case set, wherein the software system comprises at least one functional module, and the test case set comprises at least one test case; then selecting a test case matched with the function of each functional module, and executing the test case matched with the function in each functional module to obtain an execution result of each functional module; the execution result can reflect the execution condition of the test case on each functional module in the software system (namely, whether the test case can be correctly executed in the functional module in the software system) so as to determine whether the software system functions normally or not according to each execution condition, and the running capability and other related information, and determine whether the software system passes the test or not according to the information. The method does not need to be manually participated, and greatly improves the efficiency and the accuracy.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be 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 embodiments of the present application, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
Fig. 1 is an application scenario schematic diagram of a test method of a software system according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a software system testing system according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a test flow of a software system according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a test case storage structure according to an embodiment of the present application;
FIG. 5 is a flowchart of a software system testing method according to another embodiment of the present application;
FIG. 6 is a flow chart of a test task initiation provided in accordance with one embodiment of the present application;
FIG. 7 is a schematic diagram of a test device of a software system according to an embodiment of the present application;
Fig. 8 is a schematic structural diagram of a terminal device according to an embodiment of the present application;
Fig. 9 is a schematic structural view of a computer-readable storage medium provided in an embodiment of the present application.
Detailed Description
The following description of the technical solutions in the embodiments of the present application will be clear and complete, and it is obvious that the described embodiments are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In order to more specifically describe the present application, a method, an apparatus, a terminal device and a storage medium for testing a software system provided by the present application are specifically described below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 shows a schematic diagram of an application scenario of a test method of a software system provided by an embodiment of the present application, where the application scenario includes a terminal device 100 provided by an embodiment of the present application, and the terminal device 100 may be various electronic devices (such as a structure diagram of 102, 104, 106, and 108) with a display screen, including, but not limited to, a smart phone and a computer device, where the computer device may be at least one of a desktop computer, a portable computer, a laptop computer, a tablet computer, and the like. The terminal device can be installed and run with related application programs for testing the software system, and the software system to be tested can be tested through the program. In addition, the terminal device 100 may also maintain at least one database for storing test case sets and the like. The terminal device 100 may refer broadly to one of a plurality of terminal devices, and the present embodiment is illustrated with the terminal device 100 only. Those skilled in the art will appreciate that the number of terminal devices described above may be greater or lesser. For example, the number of the terminal devices may be only several, or the number of the terminal devices may be tens or hundreds, or more, and the number and types of the terminal devices are not limited in the embodiment of the present application. The terminal device 100 may be used to perform a method for testing a software system provided in an embodiment of the present application.
In an alternative embodiment, as shown in fig. 2, the terminal device 100 includes a software system test system, where the system includes a test case management module, a test execution management module, a test result management module, and a test report management module. The test case management module is mainly used for organizing and storing test cases.
The test execution management module is mainly used for realizing that the specified test case is executed on the tested software system through the test engine, verifying whether the test passes or not according to the content of the test case, supporting the manual starting test, and stopping and recovering the test process in the test process or stopping the test process in advance. The support cycle initiates the test, specifying execution on a monthly, daily, hourly, minute, or second basis.
The test result management module is mainly used for managing all the case execution results, and a user selects one execution result, namely various statistical information can be displayed by using a visual interface such as a graphic and the like, wherein the statistical information comprises test execution starting time, test execution ending time, the number of cases for test execution, the number of cases for test passing and the number of cases for test failure; and according to the proportion of the passing of the module statistical test and the proportion of the passing of the function statistical test, providing detailed log information of test case execution.
The test report management module is mainly used for managing all use case execution results, and a user selects one use case execution result to display statistical information of the test, so that one-key generation of a test report is supported, and the test report comprises detailed test use cases, test procedures, test defects and the like.
In an optional implementation manner, the application scenario may further include a server in addition to the terminal device 100 provided by the embodiment of the present application, where a network is disposed between the server and the terminal device. The network is used as a medium for providing a communication link between the terminal device and the server. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
It should be understood that the number of terminal devices, networks and servers is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, the server may be a server cluster formed by a plurality of servers. Wherein the terminal device interacts with the server through the network to receive or send messages and the like. The server may be a server providing various services. Wherein the server may be adapted to perform the steps of a method for testing a software system provided in an embodiment of the application. In addition, when the terminal device executes the test method of the software system provided in the embodiment of the present application, a part of the steps may be executed in the terminal device, and a part of the steps may be executed in the server, which is not limited herein.
Based on the above, the embodiment of the application provides a testing method of a software system. Referring to fig. 3, fig. 3 is a flow chart illustrating a testing method of a software system according to an embodiment of the present application, and the method is applied to the terminal device in fig. 1 for illustration, and includes the following steps:
step S110, a software system to be tested and a test case set are obtained.
Wherein the software system comprises at least one functional module and the set of test cases comprises at least one test case.
The software system to be tested can be any software system to be tested, such as a power software system, a power grid dispatching software system, an alarm software system, an access control software system and the like.
A software system typically includes a plurality of functions, such as data acquisition, data processing, display, etc., where each function may be represented by a functional module.
A test case is a set of conditions or variables, i.e., a description of a test task performed on a particular software product, that embody test schemes, methods, techniques, and strategies. The content of the method comprises a test target, a test environment, input data, a test step, an expected result, a test script and the like, and finally a document is formed. Briefly, a test case is a set of test inputs, execution conditions, and expected results formulated for a particular goal to verify that a piece of software is satisfied that it is functioning properly. The software system test cases of different classes are different; in addition, test cases are different with different functional modules of a software system.
The test cases can be designed in advance by a tester, and the adopted design method can be a black box test method and a white box test method. The test case design is usually to modularize, parameterize and so on some test data to form a test case.
In an alternative embodiment, referring to fig. 4, the test cases may be organized into designs and stores according to a test item, test module, test function, test case four-layer structure. Wherein any one of the software systems to be tested can be recorded as a test item; wherein one test item includes a plurality of test modules, each of which may include a plurality of test functions (one of which may be represented by one of the functional modules), each of which may correspond to one or more test cases. The four-layer structure is adopted to organize design and store the test cases, so that the test cases can be conveniently and dynamically expanded, and batch import and export and online modification are convenient; in addition, the test case design may support multiple scripting languages.
In addition, a plurality of test cases are combined or aggregated together to form a test case set. For example, test case 1, test case 2, and test case 3 … …, test case n in fig. 4 may be combined together to form a test case set.
Step S120, selecting test cases matched with the functions of each functional module.
Specifically, different functional modules correspond to different test cases, so that when each functional module is tested, a test case matched with each functional module is selected. One of the functional modules may correspond to one or more test cases, so that at least one test case is selected when a test case is selected for which the functional module matches.
Alternatively, for testing accuracy, all test cases that match each functional module may be selected and then the test function may be tested with all test cases that match.
Step S130, executing the test cases matched with the functional modules in each functional module to obtain the execution result of each functional module.
Step S140, judging whether the software system passes the test according to each execution result.
After the test cases matched with each functional module are selected, the corresponding test cases are executed in each functional module, so that the execution result of each functional module is obtained. The execution result includes execution start time, execution end time, total number of test cases executed, number of test cases passed by the test, number of test cases failed by the test, test case related information (i.e., for determining which test cases executed the test), test case expected result, and test case actual result (i.e., actual result obtained after each test case is executed). After the execution results of each functional module are obtained, the execution results are analyzed to determine whether the software system passes the test.
Referring to fig. 5, in one embodiment, the testing method of the software system includes the following specific steps: starting a test, and acquiring information of a test case, wherein the information of the test case comprises a test platform ip, a port, a test log id, a test item id, a test task id and a test case id; after the software system to be tested is successfully obtained, the information of the software system to be tested is obtained, wherein the information comprises the software system ip to be tested, a user of the system to be tested, a password and a functional module in the system to be tested, after the software system to be tested is successfully obtained, a script is executed in the software system to be tested, the script is successfully executed, and then the test is finished. The software system execution script to be tested is used for executing the test cases matched with the functional modules of the software system to be tested.
When the software system is tested, the software system can be divided into test tasks according to the functional modules to form a test task list. And then executing according to the sequence of the test task list, wherein the specific process can be shown in fig. 6 in a manual task scheduling mode (namely manual test task starting), a timed test task starting mode or a periodic test task starting mode in the executing process.
Further, for step S140, it is determined whether the software system passes the test according to each execution result. Two of these implementations are selected and described separately below.
In one embodiment, determining whether the software system passes the test based on each execution result includes: when the set functional module passes the test, judging that the software system passes the test; wherein the set functional modules are one or more functional modules in the software system.
Wherein the set functional modules are usually some functional modules preset by a tester, and the functional modules are one or more of the software systems; the function modules set for different software systems are different, which function modules are selected and the number of the function modules are determined according to the type of the software system, the function of the software system, and the like, and the function modules of the core of the software system are generally selected as the set function modules, wherein the core function modules refer to the function modules which are important for the software system and correspond to functions which need to be realized.
The method is very convenient to judge or determine whether the software system passes the test, can ensure that the most core or important functions of the software system normally run, and can reduce the cost and time of modification and test of the later software system.
A second implementation of determining whether the software system passes the test based on the execution results is described next.
In another embodiment, determining whether the software system passes the test based on the execution results includes: counting the test passing rate of the functional modules in the software system; and when the test passing rate is larger than a second preset threshold value, judging that the software system passes the test.
Specifically, the test passing rate of the functional modules in the software system can be calculated according to the total number of the functional modules included in the software system and the number of the functional modules passing the test.
The second preset threshold may be a preset value by the tester, typically a percentage value. The specific data can be set according to the actual requirements, but in practice, the value should not be too small, which easily results in low accuracy of software system testing. In this way it is very convenient to judge or determine whether the software system passes the test.
The method for testing the software system provided by the embodiment of the application comprises the steps of firstly obtaining a software system to be tested and a test case set, wherein the software system comprises at least one functional module, and the test case set comprises at least one test case; then selecting a test case matched with the function of each functional module, and executing the test case matched with the function in each functional module to obtain an execution result of each functional module; the execution result can reflect the execution condition of the test case on each functional module in the software system (namely, whether the test case can be correctly executed in the functional module in the software system) so as to determine whether the software system functions normally or not according to each execution condition, and the running capability and other related information, and determine whether the software system passes the test or not according to the information. The method does not need to be manually participated, and greatly improves the efficiency and the accuracy.
Further, in executing step S130, when the test case matched with the function module is executed in each function module to obtain the execution result of each function module, it is determined whether the function module passes the test, which is specifically as follows.
In one embodiment, executing the test cases matched with each function module to obtain an execution result of each function module includes: and executing the test cases matched with the functional modules in each functional module respectively, and determining whether each functional module passes the test according to the execution results of the test cases.
Specifically, the execution results include the total number of executed test cases, the number of test cases passing the test, the number of test cases failing the test, test case related information (i.e., for determining which test cases executed the test), expected test case results, and actual test case results (i.e., actual results obtained after each test case is executed); according to the test case result, whether a certain test case passes the test or not, namely whether the test is successful or not can be determined. The determining process is as follows: and comparing the expected test case result of a certain test case with the actual test case result, and when the results are consistent, indicating that the test case is tested successfully.
It is determined whether each of the functional modules passes the test based on the execution result of each of the functional modules.
Next, a description will be given of a specific embodiment of determining whether the functional module passes the test. In one embodiment, determining whether each functional module passes the test according to the execution result of each test case includes: and when the number of test cases which are corresponding to the functional module and fail to be executed in each test case is smaller than or equal to a first preset threshold value, judging that the functional module passes the test.
The first preset threshold value may be a value preset by a tester, and is a positive integer. The specific data can be set according to the actual requirement, but in practice, the value should not be too large, which indicates that the number of test cases in a certain functional module is too large, and the greater the possibility of faults of the functional module, the lower the test accuracy of the software system is easy to cause. In this way, it is very convenient to judge or determine whether a certain functional module passes the test.
Optionally, the first preset threshold may be 0, where all test cases in a certain functional module are required to be executed successfully.
In some embodiments, the executing result of each functional module is further including: recording test case execution log information.
The log information refers to network equipment, a system, a service program and the like, and generates an event record called log when the network equipment, the system, the service program and the like operate; each row of the log records the description of the date, time, user, action, and other related operations. In this embodiment, the test case execution information is information for recording information generated when each functional module executes the test case, and according to the information, it can be determined whether the execution time of each step of the test case is correct, so that the failure cause can be analyzed when the test case fails to execute, and whether the functional module has an abnormality is determined.
In some embodiments, the method for testing a software system further includes generating a test report according to the execution result of each functional module. The test report can display the tested functional module, the used test case, the test process, the test defect and the like. And the test report is generated so that a tester can conveniently check the test result.
It should be understood that, although the steps in the flowcharts of fig. 3,4 to 6 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Also, in fig. 3, at least a portion of the steps of fig. 4 to 6 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of execution of the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with at least a portion of the other steps or sub-steps of other steps.
The embodiment of the application discloses a method for testing a software system, which can be implemented by adopting various types of equipment, so that the application also discloses a device for testing the software system corresponding to the method, and specific embodiments are given below for detailed description.
Referring to fig. 7, a testing device for a software system according to an embodiment of the present application mainly includes:
an information obtaining module 710, configured to obtain a software system to be tested and a test case set, where the software system includes at least one functional module, and the test case set includes at least one test case;
A case selection module 720, configured to select a test case that matches a function of each function module;
The case execution module 730 is configured to execute a test case matched with each function module to obtain an execution result of each function module;
The system test determination module 740 is configured to determine whether the software system passes the test according to each execution result.
In one embodiment, the use case execution module includes: the functional module test judging module:
the case execution module is used for respectively executing each test case matched with each functional module;
and the functional module test judging module is used for determining whether each functional module passes the test according to the execution result of each test case.
In one embodiment, the functional module test determination module is configured to determine that a functional module passes a test when the number of test cases that fail execution among test cases corresponding to the functional module is less than or equal to a first preset threshold.
In some embodiments, the use case execution module further comprises: and the log information recording module is used for recording the execution log information of the test case.
In some embodiments, two different implementations of the system test determination module implementing determining whether a software system passes a test based on execution results are provided, and are described separately below:
the first implementation way is:
The system test judging module is used for judging that the software system passes the test when the set functional module passes the test; wherein the set functional modules are one or more functional modules in the software system.
The second embodiment is:
and the system test judging module is used for counting the test passing rate of the functional modules in the software system, and judging that the software system passes the test when the test passing rate is greater than a second preset threshold value.
In some embodiments, the test device of the software system further comprises a test report generating module, configured to generate a test report according to the execution result of each functional module.
Specific limitations regarding the testing apparatus of the software system may be found in the limitations of the method above and will not be described in detail herein. The various modules in the apparatus described above may be implemented in whole or in part by software systems, hardware, and combinations thereof. The above modules may be embedded in hardware or independent of a processor in the terminal device, or may be stored in a memory in the terminal device in a software system, so that the processor invokes and executes operations corresponding to the above modules.
Referring to fig. 8, fig. 8 shows a block diagram of a terminal device according to an embodiment of the present application. The terminal device 80 may be a computer device. The terminal device 80 in the present application may include one or more of the following components: the processor 82, the memory 84, and one or more applications, wherein the one or more applications may be stored in the memory 84 and configured to be executed by the one or more processors 82, the one or more applications configured to perform the methods described in the method embodiments applied to the terminal device, and also configured to perform the methods described in the test method embodiments applied to the software system.
Processor 82 may include one or more processing cores. The processor 82 connects various parts within the overall terminal device 80 using various interfaces and lines, and performs various functions of the terminal device 80 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 84, and invoking data stored in the memory 84. Alternatively, the processor 82 may be implemented in at least one hardware form of digital signal Processing (DIGITAL SIGNAL Processing, DSP), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA), programmable Logic Array (PLA). The processor 82 may integrate one or a combination of several of a central processing unit (Cen tralProcessing Unit, CPU), a report validator of buried point data (Graphics Processing Unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for being responsible for rendering and drawing of display content; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 82 and may be implemented solely by a single communication chip.
The Memory 84 may include random access Memory (Random Access Memory, RAM) or Read-Only Memory (ROM). Memory 84 may be used to store instructions, programs, code, sets of codes, or instruction sets. The memory 84 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (e.g., a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described below, etc. The storage data area may also store data created by the terminal device 80 in use, etc.
It will be appreciated by those skilled in the art that the structure shown in fig. 8 is merely a block diagram of a portion of the structure associated with the present inventive arrangements and is not limiting of the terminal device to which the present inventive arrangements are applied, and that a particular terminal device may include more or fewer components than shown, or may combine some of the components, or have a different arrangement of components.
In summary, the terminal device provided in the embodiment of the present application is used to implement the testing method of the corresponding software system in the foregoing method embodiment, and has the beneficial effects of the corresponding method embodiment, which is not described herein again.
Referring to fig. 9, a block diagram of a computer readable storage medium according to an embodiment of the application is shown. The computer readable storage medium 90 has stored therein program code which is capable of being invoked by a processor to perform the methods described in the test method embodiments of the software system described above, or by a processor to perform the methods described in the test method embodiments of the software system described above.
The computer readable storage medium 90 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Optionally, the computer readable storage medium 90 comprises a non-transitory computer readable medium (non-transitory computer-readable storage medium). The computer readable storage medium 90 has storage space for program code 92 that performs any of the method steps described above. The program code can be read from or written to one or more computer program products. Program code 92 may be compressed, for example, in a suitable form.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (6)
1. A method of testing a software system, the method comprising:
acquiring a software system to be tested and a test case set, wherein the software system comprises at least one functional module, and the test case set comprises at least one test case;
Selecting test cases matched with the functions of each functional module;
Executing the test cases matched with the function modules in each function module to obtain an execution result of each function module;
judging whether the software system passes the test or not according to each execution result;
the test cases matched with the functional modules are executed in each functional module to obtain the execution result of each functional module, and the test cases comprise: each test case matched with each functional module is executed in each functional module, and whether each functional module passes the test is determined according to the execution result of each test case;
Said determining whether said software system passes the test based on each of said execution results comprises: when the set functional module passes the test, judging that the software system passes the test; wherein the set functional modules are one or more functional modules in the software system;
The obtaining the execution result of each functional module further includes: recording test case execution log information; the test case execution log information is used for recording information generated by each functional module when the test case is executed, determining whether the execution time and execution of each step of the test case are correct according to the information, and analyzing failure reasons when the test case fails, so as to determine whether the functional module has abnormality.
2. The method according to claim 1, wherein determining whether each functional module passes the test according to the execution result of each test case comprises:
and when the number of test cases which are corresponding to the functional module and fail to be executed in each test case is smaller than or equal to a first preset threshold value, judging that the functional module passes the test.
3. The method according to any one of claims 1-2, wherein said determining whether the software system passes a test based on each of the execution results comprises:
Counting the test passing rate of the functional module in the software system;
and when the test passing rate is larger than a second preset threshold value, judging that the software system passes the test.
4. A test apparatus for a software system, the apparatus comprising:
The information acquisition module is used for acquiring a software system to be tested and a test case set, wherein the software system comprises at least one functional module, and the test case set comprises at least one test case;
the use case selection module is used for selecting a test use case matched with the function of each functional module;
The case execution module is used for executing the test case matched with the case execution module in each functional module so as to obtain an execution result of each functional module;
the system test judging module is used for judging whether the software system passes the test or not according to each execution result;
The use case execution module comprises: the functional module test judging module: the function module test judging module is used for respectively executing each test case matched with each function module in each function module and determining whether each function module passes the test according to the execution result of each test case;
the system test judging module is used for judging that the software system passes the test when the set functional module passes the test; wherein the set functional modules are one or more functional modules in the software system;
The case execution module further comprises a log information recording module used for recording the test case execution log information; the test case execution log information is used for recording information generated by each functional module when the test case is executed, determining whether the execution time and execution of each step of the test case are correct according to the information, and analyzing failure reasons when the test case fails, so as to determine whether the functional module has abnormality.
5. A terminal device, comprising:
A memory; one or more processors coupled with the memory; one or more applications, wherein the one or more applications are stored in memory and configured to be executed by the one or more processors, the one or more applications configured to perform the method of any of claims 1-3.
6. A computer readable storage medium, characterized in that the computer readable storage medium has stored therein a program code, which is callable by a processor for performing the method according to any of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110452624.7A CN113238930B (en) | 2021-04-26 | 2021-04-26 | Method and device for testing software system, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110452624.7A CN113238930B (en) | 2021-04-26 | 2021-04-26 | Method and device for testing software system, terminal equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113238930A CN113238930A (en) | 2021-08-10 |
| CN113238930B true CN113238930B (en) | 2024-05-31 |
Family
ID=77129403
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110452624.7A Active CN113238930B (en) | 2021-04-26 | 2021-04-26 | Method and device for testing software system, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113238930B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114124750A (en) * | 2021-11-10 | 2022-03-01 | 重庆芯讯通无线科技有限公司 | Test method, system, equipment and storage medium of communication module |
| CN115048315A (en) * | 2022-07-06 | 2022-09-13 | 东软睿驰汽车技术（沈阳）有限公司 | Analysis method and device for automatic driving simulation test result and electronic equipment |
| CN116737597B (en) * | 2023-08-10 | 2023-10-20 | 杭银消费金融股份有限公司 | Test case processing method, system and storage medium |
| CN118093444A (en) * | 2024-04-25 | 2024-05-28 | 深圳柯拓云物联科技有限公司 | Test method, test device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106598869A (en) * | 2016-12-26 | 2017-04-26 | 北京京东金融科技控股有限公司 | Method and device for realizing automatic software testing and electronic equipment |
| CN109062802A (en) * | 2018-08-13 | 2018-12-21 | 深圳壹账通智能科技有限公司 | A kind of method for testing software, computer readable storage medium and terminal device |
| CN111475401A (en) * | 2020-03-19 | 2020-07-31 | 平安国际智慧城市科技股份有限公司 | Test method and related equipment |
| CN111522734A (en) * | 2020-03-17 | 2020-08-11 | 上海云励科技有限公司 | Software function testing method and device, electronic equipment and storage medium |
-
2021
- 2021-04-26 CN CN202110452624.7A patent/CN113238930B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106598869A (en) * | 2016-12-26 | 2017-04-26 | 北京京东金融科技控股有限公司 | Method and device for realizing automatic software testing and electronic equipment |
| CN109062802A (en) * | 2018-08-13 | 2018-12-21 | 深圳壹账通智能科技有限公司 | A kind of method for testing software, computer readable storage medium and terminal device |
| CN111522734A (en) * | 2020-03-17 | 2020-08-11 | 上海云励科技有限公司 | Software function testing method and device, electronic equipment and storage medium |
| CN111475401A (en) * | 2020-03-19 | 2020-07-31 | 平安国际智慧城市科技股份有限公司 | Test method and related equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113238930A (en) | 2021-08-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113238930B (en) | Method and device for testing software system, terminal equipment and storage medium | |
| CN106844217B (en) | Method and device for embedding point of applied control and readable storage medium | |
| CN103150249B (en) | A kind of method and system of automatic test | |
| US7673179B2 (en) | Online testing unification system with remote test automation technology | |
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| CN104820640A (en) | Webpage testing method and device | |
| CN110716870A (en) | Automatic service testing method and device | |
| CN107451040A (en) | Localization method, device and the computer-readable recording medium of failure cause | |
| CN111552633A (en) | Interface abnormal call testing method and device, computer equipment and storage medium | |
| CN114003451B (en) | Interface testing method, device, system and medium | |
| CN109739704A (en) | A kind of interface test method, server-side and computer readable storage medium | |
| CN112506757A (en) | Automatic test method, system, computer device and medium thereof | |
| CN111767209A (en) | Code testing method, device, storage medium and terminal | |
| CN115080389A (en) | Test system, method, equipment and storage medium for improving index statistical efficiency | |
| CN107679423A (en) | Partition integrity inspection method and device | |
| CN109388420A (en) | Application upgrade test method, device, computer equipment and storage medium | |
| CN113094251B (en) | Method and device for testing embedded system, computer equipment and storage medium | |
| CN116662203A (en) | Test method, test device, computer equipment and storage medium | |
| CN116431731A (en) | Data asynchronous export method, device, equipment and storage medium thereof | |
| US11681511B2 (en) | Systems and methods for building and deploying machine learning applications | |
| CN117667658A (en) | Test program generating method and test program generating device | |
| CN114297057A (en) | Design and use method of automatic test case | |
| CN112015648A (en) | Test method, device, computer equipment and medium based on automation script | |
| CN107885649A (en) | The performance test methods and device of IOS application programs | |
| CN109669868A (en) | The method and system of software test |
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 |