CN114817079A - Software stability testing method and device, electronic equipment and storage medium - Google Patents
Software stability testing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114817079A CN114817079A CN202210754387.4A CN202210754387A CN114817079A CN 114817079 A CN114817079 A CN 114817079A CN 202210754387 A CN202210754387 A CN 202210754387A CN 114817079 A CN114817079 A CN 114817079A
- Authority
- CN
- China
- Prior art keywords
- test
- online
- service
- tested
- testing
- 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
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)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method and a device for testing software stability, electronic equipment and a storage medium, wherein the method comprises the following steps: receiving a test scene adding instruction sent by a user through an interactive terminal, wherein the test scene adding instruction comprises an identifier of a service to be tested in at least one preset service; inquiring a database according to the identification of the service to be tested to obtain a test scene template corresponding to the service to be tested, and sending the test scene template to the interactive terminal, so that a user can add a test script to the test scene template to obtain a test case; and receiving the test case and the test frequency sent by the user through the interactive terminal, testing the service to be tested according to the test case and the test frequency, and sending the test result of the test to the interactive terminal. The invention has high testing efficiency and realizes the high-efficiency overall management of the testing result.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a method and a device for testing software stability, electronic equipment and a storage medium.
Background
And the software stability is that whether the software can bear a certain flow pressure for a long time or not and continuously and stably operates. The excellent stability of the software is a basic factor for providing good user experience, attracting new users and retaining old users.
Currently, the test of software stability depends on manual work, and the efficiency of executing the test is low; in addition, during software testing, each service is often assigned to a corresponding tester, so that the test result is difficult to be coordinated.
Disclosure of Invention
The embodiment of the invention provides a method and a device for testing software stability, electronic equipment and a storage medium, aiming at solving the problem that the efficiency of executing a test in the existing test for the software stability is low; and the test result is difficult to be integrated.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides a method for testing software stability, including:
receiving a test scene adding instruction sent by a user through an interactive terminal, wherein the test scene adding instruction comprises an identifier of a service to be tested in at least one preset service;
inquiring a database according to the identification of the service to be tested to obtain a test scene template corresponding to the service to be tested, and sending the test scene template to the interactive terminal, so that a user can add a test script to the test scene template to obtain a test case;
and receiving the test case and the test frequency sent by the user through the interactive terminal, testing the service to be tested according to the test case and the test frequency, and sending the test result of the test to the interactive terminal.
Alternatively,
the step of testing the service to be tested according to the test case and the test frequency comprises the following steps:
determining the test date of each test according to the test frequency;
testing the service to be tested according to the testing date;
sending the test result of the test to the interactive end, including:
obtaining a test result trend graph with the test date as an abscissa and the test result as an ordinate according to the test date and the test result corresponding to the test date one to one;
and sending the test result trend graph to the interactive terminal.
Alternatively,
sending the test result of the test to the interactive end, and then:
inquiring an online progress database in an online process management system to obtain online progress data of the service to be tested;
checking the test results corresponding to the online nodes one by one according to the online nodes in the online progress data and a preset checking specification;
if the verification result of the verification is that at least one test result corresponding to the online node is unqualified, forbidding a response user to an online instruction sent by the interactive terminal, wherein the online instruction is used for indicating that the service to be tested is operated online after the online instruction is received;
and if the verification result of the verification is that the test results corresponding to the online nodes are all qualified, and the online instruction is received, and the service to be tested is operated online.
Alternatively,
if the verification result of the verification is that at least one test result corresponding to the online node is unqualified, the method further comprises the following steps:
and generating a verification report according to the verification result, and sending the verification report to the interactive terminal.
In a second aspect, an embodiment of the present invention provides a device for testing software stability, including:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving a test scene adding instruction sent by a user through an interactive terminal, and the test scene adding instruction comprises an identifier of a service to be tested in at least one preset service;
the first execution module is used for inquiring a database according to the identifier of the service to be tested to obtain a test scene template corresponding to the service to be tested, and sending the test scene template to the interaction terminal, so that a user can add a test script to the test scene template to obtain a test case;
and the second execution module is used for receiving the test case and the test frequency sent by the user through the interactive terminal, testing the service to be tested according to the test case and the test frequency, and sending the test result of the test to the interactive terminal.
Alternatively,
the second execution module is further configured to determine a test date of each test according to the test frequency;
the second execution module is further used for testing the service to be tested according to the test date;
the second execution module is further configured to obtain a test result trend graph with the test date as an abscissa and the test result as an ordinate according to the test date and the test results corresponding to the test date one to one;
the second execution module is further configured to send the test result trend graph to the interaction terminal.
Alternatively,
the second execution module is further configured to query an online progress database in an online process management system to obtain online progress data of the service to be tested;
the second execution module is further used for checking the test results corresponding to the online nodes one by one according to the online nodes in the online progress data and a preset checking specification;
the second execution module is further configured to prohibit a response to an online instruction sent by a user through the interactive terminal if the verification result of the verification is that at least one test result corresponding to the online node is not qualified, where the online instruction is used to instruct that the service to be tested is operated online after the online instruction is received;
and the second execution module is further configured to, if the verification result of the verification is that the test results corresponding to the online nodes are all qualified, receive the online instruction, and perform online operation on the service to be tested.
Alternatively,
the second execution module is further configured to generate a verification report according to the verification result, and send the verification report to the interaction terminal.
In a third aspect, an embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program or an instruction stored on the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements the steps in the software stability testing method according to any one of the first aspect.
In a fourth aspect, the embodiment of the present invention provides a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps in the software stability testing method according to any one of the first aspect.
In the embodiment of the invention, a test scene adding instruction sent by a user through an interactive terminal is received, wherein the test scene adding instruction comprises an identifier of a service to be tested in at least one preset service; inquiring a database according to the identification of the service to be tested to obtain a test scene template corresponding to the service to be tested, and sending the test scene template to the interactive terminal, so that a user can add a test script to the test scene template to obtain a test case; and receiving the test case and the test frequency sent by the user through the interactive terminal, testing the service to be tested according to the test case and the test frequency, and sending the test result of the test to the interactive terminal. According to the embodiment of the invention, by intensifying the tasks to be tested, a user does not need to test manually, and can realize the test only by correspondingly adding the test script and the test frequency, so that the test efficiency is high; moreover, the testing result does not need to be comprehensively planned under the manual line by the testing personnel corresponding to each service to be tested, and the high-efficiency overall management of the testing result is realized.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flowchart illustrating a method for testing software stability according to an embodiment of the present invention;
FIG. 2 is a second flowchart illustrating a method for testing software stability according to an embodiment of the present invention;
FIG. 3 is a third flowchart illustrating a method for testing software stability according to an embodiment of the present invention;
FIG. 4 is a graph showing test result trends;
FIG. 5 is a fourth flowchart illustrating a method for testing software stability according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating a method for testing software stability according to an embodiment of the present invention;
FIG. 7 is a schematic block diagram of a device for testing software stability according to an embodiment of the present invention;
FIG. 8 is a functional block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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 invention.
An embodiment of the present invention provides a method for testing software stability, as shown in fig. 1, fig. 1 is a schematic flow diagram of the method for testing software stability according to the embodiment of the present invention, and the method includes:
step 11: receiving a test scene adding instruction sent by a user through an interactive terminal, wherein the test scene adding instruction comprises an identifier of a service to be tested in at least one preset service;
step 12: inquiring a database according to the identification of the service to be tested to obtain a test scene template corresponding to the service to be tested, and sending the test scene template to an interactive terminal, so that a user can add a test script to the test scene template to obtain a test case;
step 13: and receiving a test case and a test frequency sent by a user through the interactive terminal, testing the service to be tested according to the test case and the test frequency, and sending a test result of the test to the interactive terminal.
In the embodiment of the present invention, the following process is exemplarily included on the product side:
1. in the testing platform, a stability testing script is created:
a) in combination with an actual service scene, a [ add ] button is clicked on a stability test scene page of the test platform, and a test scene template corresponding to a service, such as a YTASK service of a task library and a 'live broadcast mode scene of the task library', is added.
b) And c, adding specific scripts and filling script information in combination with the actual service scene according to the stability test scene data, operation columns and points (newly added scripts) created in the step a, and by analogy, adding a plurality of stability test scripts to the scene for combination to simulate the real service scene.
2. And in a task scheduling center platform, creating a task for automatically executing the stability test script:
a) and (4) clicking a [ newly added ] button on a task management page, and creating a task for automatically executing the stability test script.
b) And filling task related information in the newly added task surface, for example, setting specific date and time, and executing the stability test script according to a certain frequency, for example, setting the stability test script to be automatically executed at 10 am every thursday.
In the embodiment of the invention, a test scene adding instruction sent by a user through an interactive terminal is received, wherein the test scene adding instruction comprises an identifier of a service to be tested in at least one preset service; inquiring a database according to the identification of the service to be tested to obtain a test scene template corresponding to the service to be tested, and sending the test scene template to the interactive terminal, so that a user can add a test script to the test scene template to obtain a test case; and receiving the test case and the test frequency sent by the user through the interactive terminal, testing the service to be tested according to the test case and the test frequency, and sending the test result of the test to the interactive terminal. According to the embodiment of the invention, by intensifying the tasks to be tested, a user does not need to test manually, and can realize the test only by correspondingly adding the test script and the test frequency, so that the test efficiency is high; moreover, the testing result does not need to be comprehensively planned under the manual line by the testing personnel corresponding to each service to be tested, and the high-efficiency overall management of the testing result is realized.
In some embodiments of the present invention, optionally, referring to fig. 2, fig. 2 is a second flowchart of a method for testing software stability according to an embodiment of the present invention, where testing a service to be tested according to a test case and a test frequency includes:
step 21: determining the test date of each test according to the test frequency;
step 22: testing the service to be tested according to the test date;
referring to fig. 3, fig. 3 is a third schematic flow chart of the software stability testing method according to the embodiment of the present invention, and the sending of the test result to the interactive end includes:
step 31: obtaining a test result trend graph with the test date as an abscissa and the test result as an ordinate according to the test date and the test results corresponding to the test date one to one;
step 32: and sending the test result trend graph to the interactive terminal.
In the embodiment of the present invention, the following process is exemplarily included on the product side:
1. in the testing platform, a stability testing script is created:
a) in combination with an actual service scene, a [ add ] button is clicked on a stability test scene page of the test platform, and a test scene template corresponding to a service, such as a YTASK service of a task library and a 'live broadcast mode scene of the task library', is added.
b) And c, adding specific scripts and filling script information in combination with the actual service scene according to the stability test scene data, operation columns and points (newly added scripts) created in the step a, and by analogy, adding a plurality of stability test scripts to the scene for combination to simulate the real service scene.
2. And in a task scheduling center platform, creating a task for automatically executing the stability test script:
a) and (4) clicking a [ newly added ] button on a task management page, and creating a task for automatically executing the stability test script.
b) And filling task related information in the newly added task surface, for example, setting specific date and time, and executing the stability test script according to a certain frequency, for example, setting the stability test script to be automatically executed at 10 am every thursday.
3. On the testing platform, referring to fig. 4, fig. 4 is a schematic diagram illustrating a trend of the testing result; and drawing a trend analysis chart of the stability of the software system on the basis of the stability test result data automatically carried out every week, and continuously analyzing and paying attention to the trend change of the stability of the software system:
a) and in the upper half part of the page, a TPS trend graph of the corresponding service is displayed, wherein the horizontal axis of the graph is the date, and the vertical axis of the graph is the TPS of the service.
b) In the lower half of the page, specific weekly stability test result data is shown.
c) In the search bar, stability test result data of a certain service in a certain period of time can be searched.
d) In the "remarks" column, the reason why the success rate is not 100% and the reason why TPS is decreased from the last week are filled in.
TPS, Transaction Per Second, namely: the number of transactions or transactions that the system can process per second. It is an important index for measuring the processing capacity of the system.
In the embodiment of the invention, the service to be tested is tested according to the test case and the test frequency, on one hand, the specific date and time can be flexibly and autonomously selected, and the stability test script is executed according to the self-defined frequency, so that the test efficiency is improved; in addition, a trend analysis chart of the stability of the software system is drawn on the basis of stability test result data executed according to user-defined test frequency, so that the trend change of the stability of the software system can be continuously analyzed and concerned, problems can be found in time in the test process, the problems can be processed in time, and high test efficiency can be realized.
In some embodiments of the present invention, optionally, referring to fig. 5, fig. 5 is a fourth flowchart of the method for testing software stability according to the embodiment of the present invention, and the sending the test result to the interactive end includes:
step 41: inquiring an online progress database in an online process management system to obtain online progress data of the service to be tested;
step 42: checking the test results corresponding to the online nodes one by one according to the online nodes in the online progress data and a preset checking specification;
step 43: if the verification result of the verification is that at least one test result corresponding to the online node is unqualified, forbidding to respond to an online instruction sent by the user through the interactive terminal, wherein the online instruction is used for indicating that the service to be tested is operated online after the online instruction is received;
step 44: and if the verification result of the verification is that the test results corresponding to the online nodes are all qualified, and the online instruction is received, and the service to be tested is operated online.
In the embodiment of the invention, the service to be tested is tested according to the test case and the test frequency, on one hand, the specific date and time can be flexibly and autonomously selected, and the stability test script is executed according to the self-defined frequency, so that the test efficiency is improved; in addition, a trend analysis chart of the stability of the software system is drawn on the basis of stability test result data executed according to user-defined test frequency, so that the trend change of the stability of the software system can be continuously analyzed and concerned, problems can be found in time in the test process, the problems can be processed in time, and high test efficiency can be realized; in addition, the test result is combined with the online flow management, the on-line flow stability test standard stuck point inspection is carried out, the overall arrangement and utilization of the test result are realized, and the test efficiency is improved.
In some embodiments of the present invention, optionally, if the verification result of the verification is that at least one test result corresponding to the upper line node is not qualified, the method further includes:
and generating a verification report according to the verification result, and sending the verification report to the interactive terminal.
In the embodiment of the present invention, the following process is further included, for example, on the product side:
the online process management system follows the online process of each item service every week, and checks the checkpoint at the stage test stage:
a) when the routine on-line every week is carried out, in the stage of stage testing, when a tester finishes the stage testing, the on-line management system inquires whether the service responsible by the on-line management system has a stability test record in the week in an interface mode, and whether TPS (TPS profile) is reduced compared with the data in the last week, and if the condition is not met, in the stage testing stage, when a point [ submit ] button is arranged, the submission fails.
In the embodiment of the present invention, the following process is exemplarily included on the technical side:
1. and creating a stability test script of the corresponding service in the test platform.
2. And in the task scheduling center, a task for automatically executing the stability test script by setting specific date and time and according to a certain frequency is created.
3. And automatically counting the stability test result data on the test platform, and drawing a trend analysis chart.
4. In the on-line process management system, in the on-line process and the stage test stage of each week, when the point submission of the tester is completed, the on-line process management system inquires whether the service responsible by the tester has a stability test record in the week in an interface mode, and whether TPS (TPS) data is reduced compared with data in the last week, and then the point clamping check is carried out.
In the embodiment of the present invention, for example, referring to fig. 6, fig. 6 is a schematic flowchart of a method for testing software stability by applying the embodiment of the present invention, and the method includes the following steps on a product side:
1. in the testing platform, a stability testing script is created:
a) in combination with an actual service scene, a [ add ] button is clicked on a stability test scene page of the test platform, and a test scene template corresponding to a service, such as a YTASK service of a task library and a 'live broadcast mode scene of the task library', is added.
b) And c, adding specific scripts and filling script information in combination with the actual service scene according to the stability test scene data, operation columns and points (newly added scripts) created in the step a, and by analogy, adding a plurality of stability test scripts to the scene for combination to simulate the real service scene.
2. And in a task scheduling center platform, creating a task for automatically executing the stability test script:
a) and (4) clicking a [ newly added ] button on a task management page, and creating a task for automatically executing the stability test script.
b) Filling in relevant information of task in the newly added task surface, such as setting specific date and time, executing stability test script according to certain frequency, such as setting to automatically execute stability test script at 10 am every thursday
3. On the test platform, based on the stability test result data automatically performed every week, a trend analysis chart of the software system stability is drawn for continuously analyzing and paying attention to the trend change of the software system stability:
a) and in the upper half part of the page, a TPS trend graph of the corresponding service is displayed, wherein the horizontal axis of the graph is the date, and the vertical axis of the graph is the TPS of the service.
b) In the lower half of the page, specific weekly stability test result data is shown.
c) In the search bar, stability test result data of a certain service in a certain period of time can be searched.
d) In the "remarks" column, the reason why the success rate is not 100% and the reason why TPS is decreased from the last week are filled in.
4) The online process management system follows the online process of each weekly project service, and the checkpoint check is carried out at the stage test stage:
a) when the routine on-line every week is carried out, in the stage of stage testing, when a tester finishes the stage testing, the on-line management system inquires whether the service responsible by the on-line management system has a stability test record in the week in an interface mode, and whether TPS (TPS profile) is reduced compared with the data in the last week, and if the condition is not met, in the stage testing stage, when a point [ submit ] button is arranged, the submission fails.
An embodiment of the present invention provides a device for testing software stability, as shown in fig. 7, where fig. 7 is a schematic block diagram of the device for testing software stability according to the embodiment of the present invention, and the device 60 for testing software stability includes:
the receiving module 61 is configured to receive a test scenario adding instruction sent by a user through an interactive terminal, where the test scenario adding instruction includes an identifier of a service to be tested in at least one preset service;
the first execution module 62 is configured to query a database according to the identifier of the service to be tested, obtain a test scenario template corresponding to the service to be tested, and send the test scenario template to the interaction end, so that a user can add a test script to the test scenario template to obtain a test case;
the second execution module 63 is configured to receive the test case and the test frequency sent by the user through the interactive end, test the service to be tested according to the test case and the test frequency, and send a test result of the test to the interactive end.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the second executing module 63 is further configured to determine a test date of each test according to the test frequency;
the second execution module 63 is further configured to test the service to be tested according to the test date;
the second executing module 63 is further configured to obtain a test result trend graph with the test date as an abscissa and the test result as an ordinate according to the test date and the test result corresponding to the test date one to one;
the second executing module 63 is further configured to send the test result trend graph to the interactive terminal.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the second execution module 63 is further configured to query an online progress database in an online process management system to obtain online progress data of the service to be tested;
the second execution module 63 is further configured to perform one-to-one verification on the test results corresponding to the online nodes according to the online nodes in the online progress data and a preset verification specification;
the second execution module 63 is further configured to prohibit a response to an online instruction sent by a user through the interactive terminal if the verification result of the verification is that at least one test result corresponding to the online node is not qualified, where the online instruction is used to instruct that the service to be tested is operated online after the online instruction is received;
the second execution module 63 is further configured to, if the verification result of the verification is that the test results corresponding to the online nodes are all qualified, receive the online instruction, and perform online operation on the service to be tested.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the second execution module 63 is further configured to generate a verification report according to the verification result, and send the verification report to the interaction terminal.
The device for testing software stability provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 1 to fig. 6, and achieve the same technical effect, and is not described here again to avoid repetition.
Referring to fig. 8, fig. 8 is a schematic block diagram of an electronic device 70 according to an embodiment of the present invention, and includes a processor 71, a memory 72, and a program or an instruction stored in the memory 72 and executable on the processor 71, where the program or the instruction implements steps in any software stability testing method of the present invention when executed by the processor.
The embodiment of the present invention provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the embodiment of the software stability testing method according to any one of the above embodiments, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. A method for testing software stability is characterized by comprising the following steps:
receiving a test scene adding instruction sent by a user through an interactive terminal, wherein the test scene adding instruction comprises an identifier of a service to be tested in at least one preset service;
inquiring a database according to the identification of the service to be tested to obtain a test scene template corresponding to the service to be tested, and sending the test scene template to the interactive terminal, so that a user can add a test script to the test scene template to obtain a test case;
and receiving the test case and the test frequency sent by the user through the interactive terminal, testing the service to be tested according to the test case and the test frequency, and sending the test result of the test to the interactive terminal.
2. The method for testing software stability according to claim 1, wherein:
the step of testing the service to be tested according to the test case and the test frequency comprises the following steps:
determining the test date of each test according to the test frequency;
testing the service to be tested according to the testing date;
sending the test result of the test to the interactive end, including:
obtaining a test result trend graph with the test date as an abscissa and the test result as an ordinate according to the test date and the test result corresponding to the test date one to one;
and sending the test result trend graph to the interactive terminal.
3. The method for testing software stability according to claim 1, wherein:
sending the test result of the test to the interactive end, and then:
inquiring an online progress database in an online process management system to obtain online progress data of the service to be tested;
checking the test results corresponding to the online nodes one by one according to the online nodes in the online progress data and a preset checking specification;
if the verification result of the verification is that at least one test result corresponding to the online node is unqualified, forbidding a response user to an online instruction sent by the interactive terminal, wherein the online instruction is used for indicating that the service to be tested is operated online after the online instruction is received;
and if the verification result of the verification is that the test results corresponding to the online nodes are all qualified, and the online instruction is received, and the service to be tested is operated online.
4. The software stability testing method according to claim 3, wherein:
if the verification result of the verification is that at least one test result corresponding to the online node is unqualified, the method further comprises the following steps:
and generating a verification report according to the verification result, and sending the verification report to the interactive terminal.
5. A device for testing software stability, comprising:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving a test scene adding instruction sent by a user through an interactive terminal, and the test scene adding instruction comprises an identifier of a service to be tested in at least one preset service;
the first execution module is used for inquiring a database according to the identifier of the service to be tested to obtain a test scene template corresponding to the service to be tested, and sending the test scene template to the interaction terminal, so that a user can add a test script to the test scene template to obtain a test case;
and the second execution module is used for receiving the test case and the test frequency sent by the user through the interactive terminal, testing the service to be tested according to the test case and the test frequency, and sending the test result of the test to the interactive terminal.
6. The software stability testing apparatus of claim 5, wherein:
the second execution module is further configured to determine a test date of each test according to the test frequency;
the second execution module is further used for testing the service to be tested according to the test date;
the second execution module is further configured to obtain a test result trend graph with the test date as an abscissa and the test result as an ordinate according to the test date and the test results corresponding to the test date one to one;
the second execution module is further configured to send the test result trend graph to the interaction terminal.
7. The software stability testing apparatus according to claim 5, wherein:
the second execution module is further configured to query an online progress database in an online process management system to obtain online progress data of the service to be tested;
the second execution module is further used for checking the test results corresponding to the online nodes one by one according to the online nodes in the online progress data and a preset checking specification;
the second execution module is further configured to prohibit a response to an online instruction sent by a user through the interactive terminal if the verification result of the verification is that at least one test result corresponding to the online node is not qualified, where the online instruction is used to instruct that the service to be tested is operated online after the online instruction is received;
and the second execution module is further configured to, if the verification result of the verification is that the test results corresponding to the online nodes are all qualified, receive the online instruction, and perform online operation on the service to be tested.
8. The software stability testing apparatus of claim 7, wherein:
the second execution module is further configured to generate a verification report according to the verification result, and send the verification report to the interaction terminal.
9. An electronic device, characterized in that: comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which program or instructions, when executed by the processor, implement the steps in the method of testing software stability of any one of claims 1 to 4.
10. A readable storage medium, characterized by: the readable storage medium stores thereon a program or instructions which, when executed by a processor, implement the steps in the method of testing software stability of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210754387.4A CN114817079A (en) | 2022-06-30 | 2022-06-30 | Software stability testing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210754387.4A CN114817079A (en) | 2022-06-30 | 2022-06-30 | Software stability testing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114817079A true CN114817079A (en) | 2022-07-29 |
Family
ID=82523542
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210754387.4A Pending CN114817079A (en) | 2022-06-30 | 2022-06-30 | Software stability testing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114817079A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116149983A (en) * | 2022-11-17 | 2023-05-23 | 中国人民财产保险股份有限公司 | Script testing method, device, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111352853A (en) * | 2020-05-25 | 2020-06-30 | 南京领行科技股份有限公司 | Compatibility testing method, device, server and storage medium |
| CN112306873A (en) * | 2020-10-30 | 2021-02-02 | 云账户技术(天津)有限公司 | Online flow management method and device and electronic equipment |
| CN113377667A (en) * | 2021-06-29 | 2021-09-10 | 平安国际融资租赁有限公司 | Scene-based testing method and device, computer equipment and storage medium |
| CN113448869A (en) * | 2021-07-16 | 2021-09-28 | 建信金融科技有限责任公司 | Method and device for generating test case, electronic equipment and computer readable medium |
| CN113778878A (en) * | 2021-09-10 | 2021-12-10 | 未鲲(上海)科技服务有限公司 | Interface testing method and device, electronic equipment and storage medium |
-
2022
- 2022-06-30 CN CN202210754387.4A patent/CN114817079A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111352853A (en) * | 2020-05-25 | 2020-06-30 | 南京领行科技股份有限公司 | Compatibility testing method, device, server and storage medium |
| CN112306873A (en) * | 2020-10-30 | 2021-02-02 | 云账户技术(天津)有限公司 | Online flow management method and device and electronic equipment |
| CN113377667A (en) * | 2021-06-29 | 2021-09-10 | 平安国际融资租赁有限公司 | Scene-based testing method and device, computer equipment and storage medium |
| CN113448869A (en) * | 2021-07-16 | 2021-09-28 | 建信金融科技有限责任公司 | Method and device for generating test case, electronic equipment and computer readable medium |
| CN113778878A (en) * | 2021-09-10 | 2021-12-10 | 未鲲(上海)科技服务有限公司 | Interface testing method and device, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116149983A (en) * | 2022-11-17 | 2023-05-23 | 中国人民财产保险股份有限公司 | Script testing method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107341098B (en) | Software performance testing method, platform, equipment and storage medium | |
| CN108399114B (en) | System performance testing method and device and storage medium | |
| CN109710810B (en) | Change management method, device, equipment and storage medium | |
| CN108509344B (en) | Daily cutting batch test method, equipment and readable storage medium | |
| CN113535538B (en) | Method, device, electronic equipment and storage medium for automatically testing application full link | |
| CN112597028A (en) | Method and device for displaying case test result and readable storage medium | |
| CN112115058A (en) | Test method and device, test case generation method and device and test system | |
| CN108733712A (en) | A kind of question answering system evaluation method and device | |
| CN110659870A (en) | Business audit test method, device, equipment and storage medium | |
| CN112650676A (en) | Software testing method, device, equipment and storage medium | |
| CN110267215A (en) | A kind of data detection method, equipment and storage medium | |
| CN105868956A (en) | Data processing method and device | |
| CN114817079A (en) | Software stability testing method and device, electronic equipment and storage medium | |
| CN111930611B (en) | Statistical method and device for test data | |
| CN113672497B (en) | Method, device and equipment for generating non-buried point event and storage medium | |
| CN112799956B (en) | Asset identification capability test method, device and system device | |
| CN115080401A (en) | Automatic testing method and related device | |
| CN110866492B (en) | Baseline branch identification method and device and computer system | |
| CN113297082A (en) | Product quality evaluation method and device | |
| CN113791980A (en) | Test case conversion analysis method, device, equipment and storage medium | |
| CN112862264A (en) | Enterprise operation condition analysis method, computer device and computer storage medium | |
| CN111882347A (en) | Model performance detection method, device, computer equipment and storage medium | |
| CN112506765A (en) | Software testing method, device, equipment and storage medium | |
| CN115248778A (en) | Code inspection method and device | |
| CN117033210A (en) | Flow playback test system and method |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220729 |
|
| RJ01 | Rejection of invention patent application after publication |