CN113238930A - Software system testing method and device, terminal equipment and storage medium - Google Patents
Software system testing method and device, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN113238930A CN113238930A CN202110452624.7A CN202110452624A CN113238930A CN 113238930 A CN113238930 A CN 113238930A CN 202110452624 A CN202110452624 A CN 202110452624A CN 113238930 A CN113238930 A CN 113238930A
- Authority
- CN
- China
- Prior art keywords
- test
- software system
- functional module
- test case
- module
- 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.)
- Granted
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 318
- 238000000034 method Methods 0.000 claims abstract description 58
- 230000006870 function Effects 0.000 claims abstract description 39
- 238000010998 test method Methods 0.000 claims abstract description 10
- 238000010586 diagram Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 12
- 238000012545 processing Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 238000013515 script Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 3
- 230000007547 defect Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000000528 statistical test Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a test method, a test device, terminal equipment and a storage medium of a software system, wherein the method comprises the steps of obtaining 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; 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 (i.e. whether the test case can be correctly executed in the functional module in the software system), so that whether the software system functions normally and the relevant information such as the running capability can be determined according to each execution condition, and whether the software system passes the test can be determined according to the information. The method does not need manual participation, 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 software system testing method and apparatus, a terminal device, and a storage medium.
Background
With the increasing level of intelligence, a large number of software systems (e.g., power software systems) are emerging, and these software systems can automatically manage data, information, and the like, for example, power grid dispatching and the like can be automatically completed by using the power system software systems. In order to make the software system function, it is first determined that the software system has normal and reliable functions, and it is very important to test the software system.
However, software systems typically include more functionality and the testing process is cumbersome. At present, a manual testing mode is generally adopted, but the method is low in testing efficiency, and errors are easy to occur in manual operation, so that the testing accuracy is low.
Content of application
In view of this, embodiments of the present application provide a method and an apparatus for testing a software system, a terminal device, and a storage medium, 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 a test case matched with the function of each functional module;
executing the matched test case in each functional module to obtain the execution result of each functional 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, where the apparatus includes:
the system comprises an information acquisition module, a test case collection module and a test result generation module, wherein the information acquisition module is used for acquiring a software system to be tested and the test case collection, the software system comprises at least one functional module, and the test case collection comprises at least one test case;
the case selection module is used for selecting the test case matched with the function of each functional module;
the case execution module is used for executing the test case matched with each functional module in each functional module to obtain the 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 application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, the one or more application programs being configured to perform the method of testing a software system as provided in the first aspect above.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a program code is stored in the computer-readable storage medium, and the program code may be called by a processor to execute the method for testing the software system provided in the first aspect.
According to the test method, the test device, the terminal equipment and the storage medium of the software system, the software system to be tested and a test case set are obtained firstly, 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 (i.e. whether the test case can be correctly executed in the functional module in the software system), so that whether the software system functions normally and the relevant information such as the running capability can be determined according to each execution condition, and whether the software system passes the test can be determined according to the information. The method does not need manual participation, 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 needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic application scenario diagram of a software system testing method provided in an embodiment of the present application;
FIG. 2 is a schematic structural diagram of a software system test system according to an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating a testing process of a software system according to an embodiment of the present application;
FIG. 4 is a diagram illustrating a test case storage structure according to an embodiment of the present application;
FIG. 5 is a schematic flowchart of a software system testing method according to another embodiment of the present application;
FIG. 6 is a flowchart illustrating the initiation of a test task according to an embodiment of the present application;
FIG. 7 is a schematic structural diagram of a testing apparatus of a software system provided in an embodiment of the present application;
fig. 8 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;
fig. 9 is a schematic structural diagram of a computer-readable storage medium provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described clearly and completely below, and it should be understood that the described embodiments are only a part of the embodiments of the present application, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In order to explain the present application in more detail, a method, an apparatus, a terminal device, and a storage medium for testing a software system provided in the present application are specifically described below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating an application scenario of a testing method of a software system provided in an embodiment of the present application, where the application scenario includes a terminal device 100 provided in an embodiment of the present application, and the terminal device 100 may be various electronic devices (such as block diagrams of 102, 104, 106, and 108) having 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 equipment can be installed and run with relevant application program for software system test, 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 be generally referred to as one of a plurality of terminal devices, and the present embodiment is only illustrated by the terminal device 100. Those skilled in the art will appreciate that the number of terminal devices described above may be greater or fewer. For example, the number of the terminal devices may be only a few, or the number of the terminal devices may be tens of or hundreds, or may be more, and the number and the type of the terminal devices are not limited in the embodiment of the present application. The terminal device 100 may be used to execute a software system testing method provided in the embodiments of the present application.
In an alternative embodiment, as shown in fig. 2, the terminal device 100 includes a software system testing system, which 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 the execution of a specified test case on the tested software system through the test engine, verifying whether the test passes according to the content of the test case, supporting the manual start of the test, and being capable of pausing and resuming in the test process or terminating the test process in advance. A periodic start test is supported, specifying that it be performed monthly, daily, hourly, minute, or second.
The test result management module is mainly used for managing all case execution results, and a user can display various statistical information including the start time and the end time of test execution, the number of cases of test passing and the number of cases of test failure by using a visual interface such as a graphic interface and the like by selecting one execution result; and providing detailed log information of the test case execution according to the proportion of the module statistical test passing and the proportion of the function statistical test passing.
The test report management module is mainly used for managing all use case execution results, a user selects one use case execution result, statistical information of the test can be displayed, and a test report is generated by one key and comprises detailed test use cases, test processes, test defects and the like.
In an optional implementation manner, the application scenario may include a server in addition to the terminal device 100 provided in the embodiment of the present application, where a network is disposed between the server and the terminal device. Networks are used as the medium for providing communication links between terminal devices and servers. The network may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
It should be understood that the number of terminal devices, networks, and servers are 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 composed of 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 that provides various services. Wherein the server may be used to execute the steps of the testing method of the software system provided in the embodiments of the present application. In addition, when the terminal device executes the method for testing the software system provided in the embodiment of the present application, a part of the steps may be executed at the terminal device, and a part of the steps may be executed at the server, which is not limited herein.
Based on this, the embodiment of the application provides a test method of a software system. Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a method for testing a software system according to an embodiment of the present application, and taking the application of the method to the terminal device in fig. 1 as an example, the method includes the following steps:
step S110, acquiring a 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.
The software system to be tested can be any software system which needs to be tested, such as an electric power software system, a power grid dispatching software system, an alarm software system, an entrance guard software system and the like.
A software system typically comprises a plurality of functions, such as data acquisition, data processing, display, etc., wherein 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, embodying test schemes, methods, techniques, and policies. The contents of the test object, the test environment, the input data, the test steps, the expected results, the test scripts and the like are included, and finally, a document is formed. Simply, a test case is considered to be a set of test inputs, execution conditions, and expected results tailored for a particular purpose to verify whether a certain software is satisfied to work correctly. Different classes of software system test cases are different; in addition, the test cases of different functional modules in a software system are different.
The test cases can be designed in advance by testers, and the adopted design method can be a black box test method and a white box test method. In the test case design, some test data is usually modularized, parameterized, and the like to form a test case.
In an alternative embodiment, referring to fig. 4, the test cases may be organized and stored according to a four-layer structure of test items, test modules, test functions, and test cases. Any software system to be tested can be marked as a test item; one test item comprises a plurality of test modules, each test module can comprise a plurality of test functions (one test function can be represented by one function module), and each test function can correspond to one or more test cases. The test cases can be conveniently and dynamically expanded by organizing, designing and storing the test cases by adopting a four-layer structure, and batch import and export and online modification are facilitated; in addition, 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 … … in fig. 4 may be combined together to form a test case suite.
Step S120, selecting a test case matched with the function of each functional module.
Specifically, different functional modules correspond to different test cases, so that a test case matched with each functional module needs to be selected when each functional module is tested. 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 matched with one functional module is selected.
Optionally, for the accuracy of the test, all the test cases matched with each functional module may be selected, and then all the matched test cases may be used to test the test function.
Step S130, executing the matched test case in each functional module to obtain the execution result of each functional module.
Step S140, determining whether the software system passes the test according to each execution result.
After the test case matched with each functional module is selected, the corresponding test case is 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 executed test cases, number of test cases that pass the test, number of test cases that fail the test, test case related information (i.e., used for determining which test cases execute the test), expected result of the test case, and actual result of the test case (i.e., actual result obtained after each test case executes). 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 an embodiment, a method for testing a software system includes the following steps: starting testing, 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 project id, a test task id and a test case id; and after the acquisition is successful, acquiring the information of the software system to be tested, including the software system ip to be tested, the system user to be tested, the password and the functional module in the system to be tested, and after the acquisition is successful, executing the script in the software system to be tested, wherein the script is successfully executed, and the test is finished. The software system to be tested executes the script to execute the matched test case on the functional module of the software system to be tested.
When the software system is tested, the software system can be divided into a plurality of test tasks according to the functional modules during testing, and a test task list is formed. Then, the execution is performed according to the sequence of the test task list, wherein in the execution process, the test task may be started at regular time or periodically according to a manual task scheduling manner (i.e., manually starting the test task), and the specific process is shown in fig. 6.
Further, for step S140, there are various implementations for determining whether the software system passes the test according to each execution result. Two implementations are chosen and described separately below.
In one embodiment, determining whether the software system passes the test according to each execution result includes: when the set functional module passes the test, judging that the software system passes the test; the set functional module is one or more functional modules in the software system.
The set functional modules are usually some functional modules preset by a tester, and the functional modules are one or more of software systems; the functional modules set for different software systems are different, which functional modules are selected and the number of the selected functional modules is determined according to the type of the software system, the function of the software system and the like, and generally, the functional module of the core of the software system is selected as the set functional module, wherein the functional module of the core refers to the functional module corresponding to the important function which needs to be realized by the software system.
By adopting the method, whether the software system passes the test or not can be judged or determined very conveniently, the most core or most important function of the software system can be ensured to run normally, and the cost and time for modifying and testing the software system at the later stage can be reduced.
Next, a second implementation of determining whether the software system passes the test based on each execution result will be described.
In another embodiment, determining whether the software system passes the test based on the results of each execution includes: counting the test passing rate of the functional modules in the software system; and when the test passing rate is greater 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 may 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 value preset by the tester, typically a percentage value. The specific data can be set according to actual requirements, but in practice, the value should not be too small, which easily causes the software system to have low test accuracy. 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 comprises the steps of firstly obtaining 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 (i.e. whether the test case can be correctly executed in the functional module in the software system), so that whether the software system functions normally and the relevant information such as the running capability can be determined according to each execution condition, and whether the software system passes the test can be determined according to the information. The method does not need manual participation, and greatly improves the efficiency and the accuracy.
Further, in step S130, when the matched test case is executed in each functional module to obtain the execution result of each functional module, the method includes determining whether the functional module passes the test, and the specific process is as follows.
In one embodiment, executing the matched test case in each functional module to obtain the execution result of each functional module includes: and executing the matched test cases in each functional module respectively, and determining whether each functional module passes the test according to the execution result of each test case.
Specifically, the execution result includes the total number of executed test cases, the number of test cases that pass the test, the number of test cases that fail the test, information related to the test cases (i.e., information used to determine which test cases execute the test), an expected result of the test cases, and an actual result of the test cases (i.e., an actual result obtained after each test case is executed); whether a certain test case passes the test or not can be determined according to the test case result, namely whether the test is successful or not. The determination process is as follows: and comparing the expected result of the test case of a certain test case with the actual result of the test case, and when the results are consistent, indicating that the test case is tested successfully.
Whether each functional module passes the test can be determined according to the execution result of each functional module.
Next, a description will be given of a specific embodiment of determining whether or not 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 the test cases which fail to be executed in each test case corresponding to one functional module is less than or equal to a first preset threshold value, judging that the functional module passes the test.
The first preset threshold may be a value preset by a tester, and is a positive integer. The specific data can be set according to actual requirements, but in practice, the value should not be too large, which indicates that the number of failed test cases in a certain functional module is large, and the probability of the functional module having a fault is higher, thereby easily causing the low test accuracy of the software system. The method is very convenient to judge or determine whether a certain functional module passes the test or not.
Optionally, the first preset threshold may be 0, at this time, all test cases in a certain functional module are required to be successfully executed, and by using the method, the performance of the functional module can be ensured to the greatest extent, and the test accuracy is high.
In some embodiments, obtaining the execution result of each functional module further includes: and recording the test case execution log information.
The log information refers to network equipment, a system, a service program and the like, and an event record called log is generated during operation; each row of the log records the description of the date, time, user and action. In this embodiment, the test case execution information is used to record information generated when each functional module executes a test case, and according to the information, it can be determined whether the execution time of each step of the test case is correct or not, so that when the test case fails to execute, the failure reason is conveniently analyzed, and thus it is determined whether the functional module is abnormal or not.
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 a 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 through 6 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 3, 4-6 may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternatingly with other steps or at least some of the sub-steps or stages of other steps.
The embodiment disclosed in the present application describes a method for testing a software system in detail, and the method disclosed in the present application can be implemented by devices in various forms.
Referring to fig. 7, a testing apparatus for a software system disclosed in an embodiment of the present application mainly includes:
the information acquisition module 710 is configured to acquire a software system to be tested and a test case set, where the software system includes at least one function module, and the test case set includes at least one test case;
a use case selection module 720, configured to select a test use case matching the function of each functional module;
the case execution module 730 is configured to execute the test case matched with each functional module in each functional module to obtain an execution result of each functional module;
and a system test determining module 740, configured to determine whether the software system passes the test according to each execution result.
In one embodiment, the use case execution module includes: function module test decision module:
the case execution module is used for respectively executing the test cases matched with the function modules in each function module;
and the functional module test judging module is used for determining whether each functional module passes the test or not according to the execution result of each test case.
In an embodiment, the functional module test determining module is configured to determine that a functional module passes a test when the number of test cases that fail to be executed in each test case 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 test case execution log information.
In some embodiments, two different implementations of determining whether the software system passes the test according to each execution result are provided by the system test determination module, which are respectively described as follows:
the first realization mode is as follows:
the system test judging module is used for judging that the software system passes the test when the set functional module passes the test; the set functional module is one or more functional modules in the software system.
The second embodiment is as follows:
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 apparatus of the software system further includes a test report generation module, configured to generate a test report according to an execution result of each functional module.
For the specific definition of the test device of the software system, reference may be made to the above definition of the method, which is not described herein again. The various modules in the above-described apparatus may be implemented in whole or in part by software systems, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent of a processor in the terminal device, and can also be stored in a memory in the terminal device in a software system form, so that the processor can call and execute operations corresponding to the modules.
Referring to fig. 8, fig. 8 is a block diagram illustrating a structure 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: a processor 82, a 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 above-described method embodiments applied to a terminal device, and also configured to perform the methods described in the above-described test method embodiments applied to a software system.
The 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 calling data stored in the memory 84. Alternatively, the processor 82 may be implemented in hardware using at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 82 may be integrated with one or a combination of a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing display content; the modem is used to handle wireless communications. It is understood that the modem may be implemented by a communication chip, rather than integrated into the processor 82.
The Memory 84 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). The memory 84 may be used to store instructions, programs, code sets 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 (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, and the like. The storage data area may also store data created by the terminal device 80 in use, and the like.
Those skilled in the art will appreciate that the structure shown in fig. 8 is a block diagram of only a portion of the structure relevant to the present application, and does not constitute a limitation on the terminal device to which the present application is applied, and a particular terminal device may include more or less components than those shown in the drawings, or combine some 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 corresponding method for testing a software system in the foregoing method embodiment, and has the beneficial effects of the corresponding method embodiment, which are not described herein again.
Referring to fig. 9, a block diagram of a computer-readable storage medium according to an embodiment of the present disclosure is shown. The computer readable storage medium 90 stores program codes, which can be called by the processor to execute the methods described in the embodiments of the test method of the software system, and can also be called by the processor to execute the methods described in the embodiments of the test method of the software system.
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. Alternatively, the computer-readable storage medium 90 includes a non-transitory computer-readable storage medium. The computer readable storage medium 90 has storage space for program code 92 for performing any of the method steps of the method described above. The program code can be read from or written to one or more computer program products. The program code 92 may be compressed, for example, in a suitable form.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," 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 application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer 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, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one 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 (10)
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 a test case matched with the function of each functional module;
executing the matched test case in each functional module to obtain the execution result of each functional module;
and judging whether the software system passes the test or not according to each execution result.
2. The method of claim 1, wherein executing the matched test case in each functional module to obtain the execution result of each functional module comprises:
and executing the matched test cases in each functional module respectively, and determining whether each functional module passes the test according to the execution result of each test case.
3. The method of claim 2, wherein determining whether each functional module passes the test according to the execution result of each test case comprises:
and when the number of the test cases which fail to be executed in each test case corresponding to one functional module is less than or equal to a first preset threshold value, judging that the functional module passes the test.
4. The method of claim 2, wherein obtaining the execution result of each functional module further comprises:
and recording the test case execution log information.
5. The method according to any one of claims 2-4, wherein said determining whether the software system passes the test based on each of the execution results comprises:
when the set functional module passes the test, judging that the software system passes the test;
wherein the set functional module is one or more functional modules in the software system.
6. The method according to any one of claims 2-4, wherein said determining whether the software system passes the test based on each of the execution results comprises:
counting the test passing rate of the functional modules in the software system;
and when the test passing rate is greater than a second preset threshold value, judging that the software system passes the test.
7. An apparatus for testing a software system, the apparatus comprising:
the system comprises an information acquisition module, a test case collection module and a test result generation module, wherein the information acquisition module is used for acquiring a software system to be tested and the test case collection, the software system comprises at least one functional module, and the test case collection comprises at least one test case;
the case selection module is used for selecting the test case matched with the function of each functional module;
the case execution module is used for executing the test case matched with each functional module in each functional module to obtain the 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.
8. The apparatus of claim 7, wherein the use case execution module comprises: function module test decision module:
the functional module test judging module is used for respectively executing the test cases matched with the functional modules in each functional module and determining whether each functional module passes the test or not according to the execution result of each test case.
9. 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 the 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-6.
10. A computer-readable storage medium, having stored thereon program code that can be invoked by a processor to perform the method according to any one of claims 1 to 6.
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 true CN113238930A (en) | 2021-08-10 |
| CN113238930B 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) |
Cited By (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 |
| CN116737597A (en) * | 2023-08-10 | 2023-09-12 | 杭银消费金融股份有限公司 | 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 |
Cited By (5)
| 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 |
| CN116737597A (en) * | 2023-08-10 | 2023-09-12 | 杭银消费金融股份有限公司 | Test case processing method, system and storage medium |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113238930B (en) | 2024-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113238930A (en) | Software system testing method and device, terminal equipment and storage medium | |
| US20220321440A1 (en) | Interface Service Function Monitoring Method and System Based on Data Acquisition | |
| CN108804215B (en) | Task processing method and device and electronic equipment | |
| CN111124919A (en) | User interface testing method, device, equipment and storage medium | |
| CN111240973B (en) | Equipment testing method and system based on simulation and readable storage medium | |
| CN111881014B (en) | System test method, device, storage medium and electronic equipment | |
| CN107861876A (en) | Method of testing, device, computer equipment and readable storage medium storing program for executing | |
| US11799748B2 (en) | Mitigating failure in request handling | |
| CN114064208A (en) | Method and device for detecting application service state, electronic equipment and storage medium | |
| CN115080389A (en) | Test system, method, equipment and storage medium for improving index statistical efficiency | |
| CN107679423A (en) | Partition integrity inspection method and device | |
| EP3734460A1 (en) | Probabilistic software testing via dynamic graphs | |
| 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 | |
| CN112286754A (en) | Method and system for realizing modular construction of IT (information technology) resource inspection automation | |
| CN112596750B (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN112965910B (en) | Automatic regression testing method and device, electronic equipment and storage medium | |
| CN114676066A (en) | Security testing method and device for target application, electronic equipment and storage medium | |
| CN112380118A (en) | Unit testing method, unit testing device, medium and electronic equipment | |
| CN111737129A (en) | Service control method, service control device, computer readable medium and electronic equipment | |
| CN111835566A (en) | System fault management method, device and system | |
| CN112015648A (en) | Test method, device, computer equipment and medium based on automation script | |
| CN109669868A (en) | The method and system of software test | |
| US11494292B2 (en) | Log-based automation testing | |
| CN114064484A (en) | Interface testing method and device, electronic equipment and readable storage medium |
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 |