CN113760747A - Software testing method, device, equipment, storage medium and program product - Google Patents
Software testing method, device, equipment, storage medium and program product Download PDFInfo
- Publication number
- CN113760747A CN113760747A CN202110621042.7A CN202110621042A CN113760747A CN 113760747 A CN113760747 A CN 113760747A CN 202110621042 A CN202110621042 A CN 202110621042A CN 113760747 A CN113760747 A CN 113760747A
- Authority
- CN
- China
- Prior art keywords
- test case
- module
- software
- function
- test
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 60
- 238000013522 software testing Methods 0.000 title claims abstract description 43
- 238000012360 testing method Methods 0.000 claims abstract description 239
- 230000006870 function Effects 0.000 claims description 91
- 238000012545 processing Methods 0.000 claims description 26
- 238000013461 design Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 15
- 230000008571 general function Effects 0.000 claims description 9
- 238000012812 general test Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 10
- 238000001514 detection method Methods 0.000 description 4
- 230000007547 defect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000007704 transition 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
-
- 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/3692—Test management for test results analysis
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)
- Stored Programmes (AREA)
Abstract
The application provides a software testing method, a device, equipment, a storage medium and a program product, wherein the method comprises the following steps: the electronic equipment receives at least one functional module of the software to be tested input by a user, acquires at least one test case corresponding to the at least one functional module from a preset test case library, and finally tests the at least one functional module of the software to be tested according to the at least one test case to obtain a test result. In the technical scheme, the electronic equipment tests at least one functional module by utilizing at least one test case corresponding to at least one functional module and obtains a test result, and the test cases do not need to be independently compiled aiming at different functional modules in different software, so that the labor cost is effectively reduced, the testing efficiency is improved, and the convenience of software testing is improved.
Description
Technical Field
The present application relates to the field of software automatic testing technologies, and in particular, to a software testing method, apparatus, device, storage medium, and program product.
Background
With the rapid development of computer technology, software products occupy more and more important positions in human life, and deeply influence the daily life of people. The software product is tested before being released, so that problems and defects in the software product can be effectively found and repaired, the final quality of a software program is ensured, hidden dangers and risks caused by potential errors after the software product is released are further avoided, and the use requirements of users are effectively met. Testing of the software product is therefore essential.
Currently, testing a software product mainly includes testing each functional module in the software by a tester/developer. Specifically, before the software product is released, each enterprise performs a function/regression test on each function module in each software, and matches the software requirement specification with an expected result, thereby detecting whether the software product meets the requirement and verifying whether the software product completes a predetermined function.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: for the test of a software product, because a plurality of testers/developers are required to participate together, the labor cost is higher, the test efficiency is lower, and the convenience degree is poorer.
Disclosure of Invention
The application provides a software testing method, a software testing device, software testing equipment, a storage medium and a program product, and aims to solve the problems that in the prior art, for testing of one software product, due to the fact that multiple testers/developers are required to participate together, the labor cost is high, the testing efficiency is low, and the convenience degree is poor.
In a first aspect, an embodiment of the present application provides a software testing method, including:
receiving at least one functional module of software to be tested input by a user;
acquiring at least one test case corresponding to the at least one functional module from a preset test case library, wherein the test case library comprises test cases of a plurality of general functional modules;
and testing at least one functional module of the software to be tested according to the at least one test case to obtain a test result.
In a possible design of the first aspect, the obtaining, from a preset test case library, at least one test case corresponding to the at least one function module includes:
and inquiring and acquiring a test case corresponding to the function identifier from the test case library based on the function identifier aiming at each function module in the at least one function module.
In another possible design of the first aspect, the obtaining, from a preset test case library, at least one test case corresponding to the at least one function module includes:
sending a test case obtaining request to a service platform, wherein the test case obtaining request comprises at least one function identifier corresponding to the at least one function module;
and receiving the at least one test case returned by the service platform, wherein the at least one test case is obtained by querying the test case library according to the at least one function identifier.
In yet another possible design of the first aspect, the method further includes:
obtaining a plurality of software samples;
abstracting a plurality of universal function modules from the plurality of software samples;
and designing a universal test case for each universal function module based on functions, performance, safety, appearance and compatibility, and storing the universal test case to the test case library.
In yet another possible design of the first aspect, the at least one functional module includes:
the system comprises at least one of a registration module, a login module, a data adding module, a data deleting module, a data modifying module, a data inquiring module and a data detail module.
In a second aspect, an embodiment of the present application provides a software testing apparatus, including:
the acquisition module is used for receiving at least one functional module of the software to be tested, which is input by a user;
a processing result, configured to obtain at least one test case corresponding to the at least one function module from a preset test case library, where the test case library includes test cases of multiple general function modules;
and the processing result is also used for testing at least one functional module of the software to be tested according to the at least one test case to obtain a test result.
In a possible design of the second aspect, the processing module is specifically configured to:
and inquiring and acquiring a test case corresponding to the function identifier from the test case library based on the function identifier aiming at each function module in the at least one function module.
In another possible design of the second aspect, the processing module is specifically configured to:
sending a test case obtaining request to a service platform, wherein the test case obtaining request comprises at least one function identifier corresponding to the at least one function module;
and receiving the at least one test case returned by the service platform, wherein the at least one test case is obtained by querying the test case library according to the at least one function identifier.
In yet another possible design of the second aspect, the obtaining module is further configured to obtain a plurality of software samples;
the processing module is further used for abstracting a plurality of universal functional modules from the plurality of software samples;
the processing module is further configured to design a general test case for each general function module based on the function, performance, safety, appearance and compatibility, and store the general test case in the test case library.
In yet another possible design of the second aspect, the at least one functional module includes:
the system comprises at least one of a registration module, a login module, a data adding module, a data deleting module, a data modifying module, a data inquiring module and a data detail module.
In a third aspect, an embodiment of the present application provides an electronic device, including: a processor, a memory and computer program instructions stored on the memory and executable on the processor for implementing the method of the first aspect and each possible design when the processor executes the computer program instructions.
In a fourth aspect, embodiments of the present application may provide a computer-readable storage medium having stored therein computer-executable instructions for implementing the method provided by the first aspect and each possible design when executed by a processor.
In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program that, when executed by a processor, is configured to implement the method provided by the first aspect and each possible design.
The embodiment of the application provides a software testing method, a device, equipment, a storage medium and a program product, wherein the method comprises the following steps: the electronic equipment receives at least one functional module of the software to be tested input by a user, acquires at least one test case corresponding to the at least one functional module from a preset test case library, and finally tests the at least one functional module of the software to be tested according to the at least one test case to obtain a test result. In the technical scheme, the electronic equipment tests the corresponding at least one functional module through the at least one test case and obtains a test result, and the test case does not need to be independently written for different functional modules in different software, so that the labor cost is effectively reduced, the test efficiency is improved, and the convenience of software test is improved. Furthermore, the software testing process can be independent of experience level of testers, and the detection quality is effectively improved.
Drawings
Fig. 1 is a schematic view of an application scenario of a software testing method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a first embodiment of a software testing method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a second software testing method provided in the embodiment of the present application;
FIG. 4 is a schematic diagram illustrating a software testing method according to an embodiment of the present disclosure;
FIG. 5 is a schematic structural diagram of a software testing apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but 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.
Before introducing the embodiments of the present application, an application scenario of the embodiments of the present application is explained first:
in an age with various software products, the software products occupy more and more important positions in human life, and deeply affect the daily life of people. For example, people can communicate in real time through communication software, and can commute in daily work or play on holidays through traffic software. In order to ensure that the software product can meet the requirements of the user, the software product needs to be tested before being released. The problems and defects in the software product are obtained through testing and corrected, and the final quality of the software program can be effectively guaranteed, so that hidden dangers and risks caused by potential errors after the software product is released are avoided, and the use requirements of users can be effectively met.
Currently, testing a software product mainly includes testing each functional module in the software by a tester/developer. Specifically, before the software product is released, each enterprise performs a function/regression test on each function module in each software, and matches the software requirement specification with an expected result, thereby detecting whether the software product meets the requirement and verifying whether the software product completes a predetermined function. For example, the testing work of the software product developed by enterprise a is performed by the tester/developer in charge of different functional modules by enterprise a, and the same is true for enterprise B.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: for the test of a software product, because a plurality of testers/developers are required to participate together, the labor cost is high, the test efficiency is low, and the convenience degree is poor.
Specifically, although the services of different software products are different, most software products have many identical or similar functional modules, for example, most software products have a registration login function, a list content search function, a data adding, deleting, modifying, and checking function, and the like. However, different software products developed by the same enterprise may also be tested by different testers/developers for the same functional module (e.g., login module), which may cause the same error to occur multiple times.
Further, since the testing quality of the software product depends on the technical level and experience of the testers/developers, the technical level of the testers/developers varies among different enterprises, so that the automation degree of the software testing is different, and enterprises with relatively weak technical levels cannot refer to or utilize the successful experience of mature enterprises. If the tester/developer experiences little, many problems may occur after the software product is released. The human flow also has a great influence on the iteration of the software product, when a tester/developer leaves a post, a new person who takes over the test work of the tester/developer needs a long learning time, the starting threshold of the test work of the software product is high, and a long transition period is needed.
In view of the above problems, the inventive concept of the present application is as follows: in the current scheme, although most software products have the same or similar functional modules, a special tester/developer is required to write a case for testing each functional module of each software product, which results in low testing efficiency. Based on this, the inventor finds that if a test case library including test cases of a plurality of general function modules can be preset, the process of compiling the cases respectively for each function module of each software product in the prior art can be replaced, and the problem of low test efficiency in the prior art can be solved, so that the labor cost can be reduced, and the convenience of detection can be improved.
For example, the software testing method provided by the embodiment of the present application may be applied to an application scenario diagram shown in fig. 1. Fig. 1 is a schematic view of an application scenario of a software testing method provided in an embodiment of the present application, so as to solve the above technical problem. As shown in fig. 1, the application scenario may include: the terminal equipment, the server and a test case library connected with the server.
For example, in the application scenario shown in fig. 1, the terminal device may receive at least one function module of the software to be tested, which is input by a user, and then send the function module to the server, and the server receives the at least one function module of the software to be tested, which is sent by the terminal device, through the network, so as to subsequently obtain a corresponding test case from the test case library for the function module.
In this embodiment, at least one test case is stored in the test case library. The server can obtain the test case corresponding to the functional module from the test case library based on the received functional module, test the functional module by using the test case, and obtain the test result. The server can also send the test case to the terminal equipment, and the terminal equipment tests the functional module by using the test case after receiving the test case.
It should be noted that fig. 1 is only a schematic diagram of an application scenario provided in this embodiment, and this embodiment of the present application does not limit the devices included in fig. 1, nor the location relationship between the devices in fig. 1, for example, in fig. 1, the test case library may be an external database with respect to the server, and in other cases, the test case library may also be placed in the server.
In practical applications, since the terminal device is also a processing device with data processing capability, the server in the application scenario shown in fig. 1 can also be implemented by the terminal device. In the embodiments of the present application, the server and the terminal device for data processing may be collectively referred to as an electronic device. Optionally, in the embodiment of the present application, an execution subject of the software testing method is used as an electronic device, for example, a background service platform and the like for explanation.
The technical solution of the present application will be described in detail below with reference to specific examples.
It should be noted that the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.
Fig. 2 is a schematic flowchart of a first embodiment of a software testing method according to an embodiment of the present application. As shown in fig. 2, the software testing method may include the steps of:
s101: and receiving at least one functional module of the software to be tested input by a user.
In this step, since the software to be tested has a plurality of functional modules, when at least one functional module in the software to be tested needs to be tested, the electronic device needs to receive at least one functional module of the software to be tested, which is input by the user, through the network or the service platform.
Optionally, at least one of the functional modules includes: the system comprises at least one of a registration module, a login module, a data adding module, a data deleting module, a data modifying module, a data inquiring module and a data detail module.
Optionally, each functional module corresponds to one functional identifier, and each functional identifier corresponds to one general test case, so that the corresponding test case can be obtained subsequently according to the functional identifier.
S102: and acquiring at least one test case corresponding to at least one functional module from a preset test case library.
In this step, since the electronic device needs to test the functional module according to the test case, the test cases required by different functional modules are different. Therefore, after the electronic device obtains the at least one functional module, the electronic device needs to obtain a corresponding test case according to the at least one functional module.
In a specific implementation manner, when the electronic device receives at least one functional module, analyzing each functional module in the at least one functional module to obtain a function identifier corresponding to each functional module. And then the electronic equipment queries from the test case library based on the function identifier to acquire a universal test case corresponding to the function identifier. For at least one functional module, the electronic equipment acquires at least one test case from the test case library.
The test case library comprises a plurality of test cases of the universal function module.
Optionally, the test case library may further include a plurality of personalized cases of the general function module.
In this specific implementation manner, when there is a personalized service in the functional module of the software to be tested, for example, when the login of the universal login module fails, the prompt message is "login failure", and when the login module of the software to be tested fails and needs to display "your login information is wrong and please re-input", the electronic device may further obtain a personalized case corresponding to the functional module with the personalized service. When the electronic equipment receives at least one functional module, the electronic equipment acquires the Identity (ID) of each functional module in the at least one functional module of the software to be detected, and acquires the personalized case corresponding to the ID from the test case library according to the ID.
Wherein, the ID of the same functional module of different software is different.
In another specific implementation, the electronic device may receive at least one functional module, and generate a test case obtaining request in response to an operation of a user on the graphical user interface.
The test case obtaining request comprises at least one function identifier corresponding to at least one function module.
In the specific implementation manner, the electronic device sends the test case acquisition request to the service platform and receives at least one test case returned by the service platform. The electronic equipment sends a test case obtaining request to the service platform, and after the service platform receives the test case obtaining request, the service platform obtains at least one function identifier carried in the request from the test case. The service platform queries from the test case library according to the at least one function identifier, obtains a corresponding test case for each function identifier, obtains at least one test case altogether, sends the obtained at least one test case to the electronic equipment, and the electronic equipment receives the at least one test case returned by the service platform.
And the test case obtaining request can also comprise at least one ID corresponding to at least one functional module.
In the specific implementation manner, the electronic device sends a test case acquisition instruction carrying at least one ID to the service platform, the service platform acquires at least one ID personalized case according to the at least one ID and sends the ID personalized case to the electronic device, and the electronic device receives the at least one personalized case sent by the service platform.
S103: and testing at least one functional module of the software to be tested according to at least one test case to obtain a test result.
In this step, after the electronic device obtains at least one test case, the corresponding functional module may be tested according to each test case, and a test result may be obtained.
In a specific implementation manner, for each functional module in at least one functional module, the functional module is tested according to the test case corresponding to the functional module, and a test result of the functional module is obtained. And by parity of reasoning, the test result of each functional module is obtained respectively.
Optionally, for each functional module in the at least one functional module, the personalized service of the functional module may also be tested according to the personalized case corresponding to the functional module, so as to obtain a test result of the functional module.
Wherein the test result of each module comprises test success and test failure.
Optionally, when the test result is a test failure, the test result may further include a specific reason and a specific position of the test failure, so that a tester/developer may repair the functional module with respect to the test result in the following process.
In a possible implementation manner, the electronic device may further process the test result of each functional module to generate a test result report, where the test report may include the test result, the test time, and the like, and may also include other data generated in the software test process, and may be defined according to an actual situation, which is not specifically limited in this application.
According to the software testing method provided by the embodiment of the application, the electronic equipment receives at least one functional module of software to be tested input by a user, obtains at least one test case corresponding to the at least one functional module from a preset test case library, and finally tests the at least one functional module of the software to be tested according to the at least one test case to obtain a test result. In the method, the electronic equipment tests the corresponding at least one functional module through the at least one test case and obtains the test result, and the test case does not need to be independently compiled aiming at different functional modules in different software, so that the labor cost is effectively reduced, the test efficiency is improved, and the convenience of software test is improved. Furthermore, the software testing process can be independent of experience level of testers, and the detection quality is effectively improved.
Exemplarily, on the basis of the above embodiments, fig. 3 is a schematic flow diagram of a second embodiment of a software testing method provided in the embodiment of the present application. As shown in fig. 3, in this embodiment, the software testing method may further include the following steps:
s201: a plurality of software samples are acquired.
In this step, since at least one functional module in the software to be tested needs to be calculated by using the test case corresponding to each functional module, the electronic device first needs to obtain a software sample, so as to subsequently obtain a plurality of universal functional modules according to the software sample, and obtain a corresponding test case according to the plurality of universal functional modules.
Due to the difference of the software, the universal function modules universal among different types of software can be obtained, so that the obtained universal function modules are more universal, and the accuracy and universality of subsequently obtained test cases are improved. Therefore, the electronic device needs to acquire multiple software samples.
Optionally, the multiple software samples may be software with a large use amount and different services for the user, such as different communication software and game software.
Optionally, for the same software, different clients may also be included, for example, a computer end, a mobile phone application end, an applet end, and the like may be included, and different clients of the same software may be one software sample or different software samples, which may be set according to actual conditions, and the present scheme is not specifically limited.
S202: a plurality of common functional modules are abstracted from a plurality of software samples.
In this step, since the software has multiple functions, after the electronic device obtains multiple software samples, the electronic device needs to process the multiple software samples to abstract out multiple universal function modules, so as to obtain multiple test cases according to the multiple universal function modules in the following step.
In a specific implementation manner, the electronic device divides each software sample according to different functions without considering a service scene, abstracts at least one universal function module which is universal and has commonality from each software sample, and then can enrich and refine the universal function modules step by step.
S203: and designing a universal test case for each universal functional module based on the function, performance, safety, appearance and compatibility, and storing the universal test case to a test case library.
In this step, after the electronic device acquires the universal function modules, a corresponding test case may be designed for each universal function module, so as to facilitate subsequent detection of the acquired function modules in the software to be detected.
According to each universal functional module, the electronic equipment makes certain specifications based on the angles of function, performance, safety, appearance, compatibility and the like, so that a universal test case is designed.
Optionally, a certain specification may be to limit the length of the input box and special characters, a non-empty check and a friendly prompt must be made for a mandatory field, or may be a specification that can be formulated in some other test cases, and may be limited according to an actual situation, and this is not specifically limited by the present scheme.
Optionally, due to differences of software, personalized services exist in the same functional module between the software, so that a personalized use case can be designed according to different requirements of a software sample.
Furthermore, the electronic device may store the obtained general test case and the personalized case in a test case library.
According to the software testing method provided by the embodiment of the application, the electronic equipment obtains a plurality of software samples, and extracts a plurality of universal functional modules from the plurality of software samples. And then, the electronic equipment designs a universal test case for each universal function module based on the function, performance, safety, appearance and compatibility, and stores the universal test case into a test case library. The electronic equipment lays a foundation for testing at least one functional module of the software to be tested by utilizing at least one test case subsequently through designing the corresponding test case by each universal functional module. And the test case can be used in the process of testing the software, and can also be provided for research personnel to carry out self-test on the software, thereby effectively driving the research and development of the software.
For example, the software testing method in the foregoing embodiment may be applied to a schematic diagram shown in fig. 4, and fig. 4 is a schematic diagram of a principle of the software testing method provided in the embodiment of the present application. As shown in fig. 4, the electronic device first needs to obtain a plurality of software samples, which are exemplified by N software samples, i.e. software sample 1, software sample 2, and software sample 3 … … software sample N. The number of software samples is only an example, and may be other numbers, which may be set according to actual situations, and this is not limited in this embodiment of the present invention.
Then, the electronic device abstracts a plurality of general-purpose functional modules from the N software samples, and in addition, can abstract a plurality of non-general-purpose functional modules. The universal function module can comprise a registration module, a login module, a data adding module, a data deleting module, a data modifying module, a data inquiring module and a data detail module.
Next, designing a universal test case for each universal function module based on functions, performance, safety, appearance and compatibility, wherein the universal test case comprises a registered test case, a logged test case, a data added test case, a data deleted test case, a data modified test case, a data queried test case and a data detailed test case. Besides, personalized use cases can be designed for the general function modules and the non-general function modules.
The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.
Fig. 5 is a schematic structural diagram of a software testing apparatus according to an embodiment of the present application. As shown in fig. 5, the software testing apparatus includes:
an obtaining module 51, configured to receive at least one functional module of software to be tested, input by a user;
a processing result 52, configured to obtain at least one test case corresponding to at least one functional module from a preset test case library, where the test case library includes test cases of multiple general functional modules;
the processing result 52 is further configured to test at least one functional module of the software to be tested according to at least one test case, so as to obtain a test result.
In one possible design of this embodiment of the present application, the processing module 52 is specifically configured to:
and inquiring and acquiring a test case corresponding to the function identifier from the test case library based on the function identifier aiming at each function module in at least one function module to obtain at least one test case.
In yet another possible design of the embodiment of the present application, the processing module 52 is specifically configured to:
sending a test case acquisition request to the service platform, wherein the test case acquisition request comprises at least one function identifier corresponding to at least one function module;
and receiving at least one test case returned by the service platform, wherein the at least one test case is obtained by inquiring from the test case library according to at least one function identifier.
In another possible design of the embodiment of the present application, the obtaining module 51 is further configured to obtain a plurality of software samples;
the processing module 52 is further configured to abstract a plurality of general-purpose functional modules from a plurality of software samples;
the processing module 52 is further configured to design a general test case for each general function module based on the function, performance, security, appearance, and compatibility, and store the general test case in the test case library.
In another possible design of the embodiment of the present application, the at least one functional module includes:
the system comprises at least one of a registration module, a login module, a data adding module, a data deleting module, a data modifying module, a data inquiring module and a data detail module.
The software testing device provided in the embodiment of the present application can be used to execute the software testing method provided in any of the above embodiments, and the implementation principle and technical effect are similar, which are not described herein again.
It should be noted that the division of the modules of the above apparatus is only a logical division, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 6, the electronic device may include: a processor 61, a memory 62 and computer program instructions stored on the memory 62 and executable on the processor 61, the processor 61 implementing the software testing method provided by any of the foregoing embodiments when executing the computer program instructions.
Optionally, the electronic device may further include an interface for interacting with other devices.
Optionally, the above devices of the electronic device may be connected by a system bus.
The memory 62 may be a separate memory unit or a memory unit integrated into the processor. The number of processors is one or more.
It should be understood that the Processor 61 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.
The system bus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The system bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus. The memory may comprise Random Access Memory (RAM) and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
All or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The aforementioned program may be stored in a readable memory. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape, floppy disk, optical disk, and any combination thereof.
The electronic device provided in the embodiment of the present application may be implemented as a terminal device or a server, and may be configured to execute the software testing method provided in any method embodiment.
The embodiment of the application provides a computer-readable storage medium, in which computer instructions are stored, and when the computer instructions are run on a computer, the computer is enabled to execute the software testing method.
The computer-readable storage medium may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. Readable storage media can be any available media that can be accessed by a general purpose or special purpose computer.
Alternatively, a readable storage medium may be coupled to the processor such that the processor can read information from, and write information to, the readable storage medium. Of course, the readable storage medium may also be an integral part of the processor. The processor and the readable storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and the readable storage medium may also reside as discrete components in the apparatus.
Embodiments of the present application further provide a computer program product, which includes a computer program, where the computer program is stored in a computer-readable storage medium, and the computer program can be read by at least one processor from the computer-readable storage medium, and the software testing method can be implemented when the computer program is executed by the at least one processor.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (13)
1. A software testing method, comprising:
receiving at least one functional module of software to be tested input by a user;
acquiring at least one test case corresponding to the at least one functional module from a preset test case library, wherein the test case library comprises test cases of a plurality of general functional modules;
and testing at least one functional module of the software to be tested according to the at least one test case to obtain a test result.
2. The method according to claim 1, wherein the obtaining at least one test case corresponding to the at least one function module from a preset test case library comprises:
and inquiring and acquiring a test case corresponding to the function identifier from the test case library based on the function identifier aiming at each function module in the at least one function module.
3. The method according to claim 1, wherein the obtaining at least one test case corresponding to the at least one function module from a preset test case library comprises:
sending a test case obtaining request to a service platform, wherein the test case obtaining request comprises at least one function identifier corresponding to the at least one function module;
and receiving the at least one test case returned by the service platform, wherein the at least one test case is obtained by querying the test case library according to the at least one function identifier.
4. The method according to any one of claims 1 to 3, further comprising:
obtaining a plurality of software samples;
abstracting a plurality of universal function modules from the plurality of software samples;
and designing a universal test case for each universal function module based on functions, performance, safety, appearance and compatibility, and storing the universal test case to the test case library.
5. The method according to any one of claims 1 to 3, wherein the at least one functional module comprises:
the system comprises at least one of a registration module, a login module, a data adding module, a data deleting module, a data modifying module, a data inquiring module and a data detail module.
6. A software testing apparatus, comprising:
the acquisition module is used for receiving at least one functional module of the software to be tested, which is input by a user;
a processing result, configured to obtain at least one test case corresponding to the at least one function module from a preset test case library, where the test case library includes test cases of multiple general function modules;
and the processing result is also used for testing at least one functional module of the software to be tested according to the at least one test case to obtain a test result.
7. The apparatus of claim 6, wherein the processing module is specifically configured to:
and inquiring and acquiring a test case corresponding to the function identifier from the test case library based on the function identifier aiming at each function module in the at least one function module.
8. The apparatus of claim 6, wherein the processing module is specifically configured to:
sending a test case obtaining request to a service platform, wherein the test case obtaining request comprises at least one function identifier corresponding to the at least one function module;
and receiving the at least one test case returned by the service platform, wherein the at least one test case is obtained by querying the test case library according to the at least one function identifier.
9. The apparatus according to any one of claims 6 to 8, wherein the obtaining module is further configured to obtain a plurality of software samples;
the processing module is further used for abstracting a plurality of universal functional modules from the plurality of software samples;
the processing module is further configured to design a general test case for each general function module based on the function, performance, safety, appearance and compatibility, and store the general test case in the test case library.
10. The apparatus according to any one of claims 6 to 8, wherein the at least one functional module comprises:
the system comprises at least one of a registration module, a login module, a data adding module, a data deleting module, a data modifying module, a data inquiring module and a data detail module.
11. An electronic device, comprising: a processor, a memory and computer program instructions stored on the memory and executable on the processor, the processor when executing the computer program instructions being for implementing the software testing method of any one of claims 1 to 5.
12. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, implement the software testing method of any one of claims 1 to 5.
13. A computer program product comprising a computer program for implementing a software testing method as claimed in any one of claims 1 to 5 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110621042.7A CN113760747A (en) | 2021-06-03 | 2021-06-03 | Software testing method, device, equipment, storage medium and program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110621042.7A CN113760747A (en) | 2021-06-03 | 2021-06-03 | Software testing method, device, equipment, storage medium and program product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113760747A true CN113760747A (en) | 2021-12-07 |
Family
ID=78787364
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110621042.7A Pending CN113760747A (en) | 2021-06-03 | 2021-06-03 | Software testing method, device, equipment, storage medium and program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113760747A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117555813A (en) * | 2024-01-11 | 2024-02-13 | 天津异乡好居网络科技股份有限公司 | Method, device, equipment and medium for determining common test case |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109062802A (en) * | 2018-08-13 | 2018-12-21 | 深圳壹账通智能科技有限公司 | A kind of method for testing software, computer readable storage medium and terminal device |
-
2021
- 2021-06-03 CN CN202110621042.7A patent/CN113760747A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109062802A (en) * | 2018-08-13 | 2018-12-21 | 深圳壹账通智能科技有限公司 | A kind of method for testing software, computer readable storage medium and terminal device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117555813A (en) * | 2024-01-11 | 2024-02-13 | 天津异乡好居网络科技股份有限公司 | Method, device, equipment and medium for determining common test case |
| CN117555813B (en) * | 2024-01-11 | 2024-05-14 | 天津异乡好居网络科技股份有限公司 | Method, device, equipment and medium for determining common test case |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108984389B (en) | Application program testing method and terminal equipment | |
| CN110955409B (en) | Method and device for creating resources on cloud platform | |
| CN109683997B (en) | Method for accessing application program interface through sandbox, sandbox and sandbox equipment | |
| CN114116496A (en) | Automatic testing method, device, equipment and medium | |
| CN111858296A (en) | Interface test method, device, equipment and storage medium | |
| CN111045942A (en) | Application testing method, system, storage medium and electronic equipment | |
| CN111241111B (en) | Data query method and device, data comparison method and device, medium and equipment | |
| CN113760747A (en) | Software testing method, device, equipment, storage medium and program product | |
| CN112256672B (en) | Database change approval method and device | |
| CN117076330B (en) | Access verification method, system, electronic equipment and readable storage medium | |
| CN112416725A (en) | Pressure testing method and device | |
| CN117499287A (en) | Web testing method, device, storage medium and proxy server | |
| CN111708712A (en) | User behavior test case generation method, flow playback method and electronic equipment | |
| CN116775493A (en) | mock testing method and device, mock platform and storage medium | |
| CN115022201B (en) | Data processing function test method, device, equipment and storage medium | |
| CN114942905A (en) | Migration data verification method, device, equipment and storage medium | |
| CN115269424A (en) | Automatic regression testing method, device, equipment and storage medium for production flow | |
| CN109165127B (en) | Problem interface positioning method and device and electronic equipment | |
| CN113238940A (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN114338846A (en) | Message testing method and device | |
| CN111475400A (en) | Verification method of service platform and related equipment | |
| CN110851254A (en) | Equipment production method, device, server and storage medium based on microservice | |
| CN111597101A (en) | SDK access state detection method, computer device and computer readable storage medium | |
| CN112527660B (en) | Static detection method and device for codes | |
| CN109525638B (en) | Method for transmitting experimental data in real time, electronic equipment and 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 |