CN115470105A - Regression testing method, device, electronic equipment and computer readable storage medium - Google Patents

Regression testing method, device, electronic equipment and computer readable storage medium Download PDF

Info

Publication number
CN115470105A
CN115470105A CN202210986985.4A CN202210986985A CN115470105A CN 115470105 A CN115470105 A CN 115470105A CN 202210986985 A CN202210986985 A CN 202210986985A CN 115470105 A CN115470105 A CN 115470105A
Authority
CN
China
Prior art keywords
interface
version information
request processing
iteration version
information
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
Application number
CN202210986985.4A
Other languages
Chinese (zh)
Inventor
李绍斌
黎清顾
林永吉
李霞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Gree Electric Appliances Inc of Zhuhai
Zhuhai Lianyun Technology Co Ltd
Original Assignee
Gree Electric Appliances Inc of Zhuhai
Zhuhai Lianyun Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Gree Electric Appliances Inc of Zhuhai, Zhuhai Lianyun Technology Co Ltd filed Critical Gree Electric Appliances Inc of Zhuhai
Priority to CN202210986985.4A priority Critical patent/CN115470105A/en
Publication of CN115470105A publication Critical patent/CN115470105A/en
Pending legal-status Critical Current

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/368—Test management for test version control, e.g. updating test cases to a new software version
    • 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/3696—Methods or tools to render software testable

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 disclosure relates to the technical field of project iterative processing, and provides a regression testing method, a regression testing device, electronic equipment and a computer-readable storage medium. The method comprises the following steps: recording current iteration version information of a target project under the condition that the target project normally operates based on the current iteration version information; and responding to the detected iteration version regression instruction, selecting target iteration version information from the recorded iteration version information, setting the target iteration version information as current iteration version information, and operating the target item based on the current iteration version information. The embodiment of the disclosure can automatically change the iteration version based on the recorded iteration version information, thereby greatly reducing the workload and further greatly saving the labor cost.

Description

Regression testing method, device, electronic equipment and computer readable storage medium
Technical Field
The present disclosure relates to the field of project iterative processing technologies, and in particular, to a regression testing method, apparatus, electronic device, and computer-readable storage medium.
Background
The software project will be iterated continuously based on the requirements, however, each iteration on the original project easily causes some functions that are already stable to have problems, and a tester needs to return to the function of the last version or even before multiple versions after each iteration update. The automation tool in the prior art often needs to manually set an interface to enter or write a script, and a large amount of labor cost needs to be consumed.
Disclosure of Invention
In view of this, embodiments of the present disclosure provide a regression testing method, apparatus, electronic device, and computer-readable storage medium, so as to solve the problem in the prior art that labor cost is high in a project iteration process.
In a first aspect of the embodiments of the present disclosure, a regression testing method is provided, including:
recording current iteration version information of a target project under the condition that the target project normally operates based on the current iteration version information;
and responding to the detected iteration version regression instruction, selecting target iteration version information from the recorded iteration version information, setting the target iteration version information as current iteration version information, and operating the target item based on the current iteration version information.
In some embodiments, the iterative version information includes at least one request processing interface for processing a request issued by the target item, and the interface status information corresponding to each request processing interface includes at least one of interface identification information, an interface return status code, error information, and error time.
In some embodiments, the above method further comprises:
capturing interface state information corresponding to at least one request processing interface corresponding to the current iteration version information in the process of operating the target item based on the current iteration version information;
judging whether the interface state information corresponding to each request processing interface represents the success of request processing;
and if the interface state information corresponding to each request processing interface indicates that the request processing is successful, indicating that the target item normally operates based on the current iteration version information.
In some embodiments, determining whether the interface status information corresponding to each request processing interface indicates that the request processing is successful includes:
if the interface return status code and the error report information of the interface status information corresponding to any request processing interface indicate that the request processing is successful, the interface status information corresponding to the request processing interface indicates that the request processing is successful;
and if the interface of the interface state information corresponding to any request processing interface returns a state code and/or error report information indicating that the request processing fails, the interface state information corresponding to the request processing interface indicates that the request processing fails.
In some embodiments, the above method further comprises:
and if the interface state information corresponding to any request processing interface indicates that the request processing fails, indicating that the target item operates abnormally based on the current iteration version information.
In some embodiments, the above method further comprises:
and generating abnormal prompt information under the condition that the target item operates abnormally based on the current iteration version information.
In some embodiments, the above method further comprises:
and displaying a first interface containing each request processing interface and interface state information thereof, wherein the display color of the interface state information indicating that the request processing is successful is different from the display color of the interface state information indicating that the request processing is failed.
In some embodiments, the interface status information indicating that the request processing is successful is displayed in green color, and/or the interface status information indicating that the request processing is failed is displayed in red color.
In some embodiments, the above method further comprises:
and after the target item is operated based on the current iteration version information, generating a test report corresponding to the current iteration version information so as to analyze the interface state information indicating the request processing failure, wherein the test report comprises at least one piece of interface state information indicating the request processing failure.
In some embodiments, the above method further comprises:
selecting at least one iteration version information from the iteration version information which has finished the operation of the target project, and generating a corresponding statistical test report to analyze the interface state information indicating the processing failure of the request, wherein the test report comprises at least one interface state information indicating the processing failure of the request.
In some embodiments, in a case where the target item is operating normally based on the current iterative version information, the method further comprises:
and setting a timing execution task to enable the target project to repeatedly execute the step of capturing interface state information corresponding to at least one interface corresponding to the current iteration version information every other preset time length in the process of running the target project based on the current iteration version information.
In a second aspect of the embodiments of the present disclosure, a regression testing apparatus is provided, including:
the recording module is used for recording the current iteration version information of the target project under the condition that the target project normally operates based on the current iteration version information;
and the selection module is used for responding to the detected iteration version regression instruction, selecting target iteration version information from the recorded iteration version information, setting the target iteration version information as current iteration version information, and operating the target item based on the current iteration version information.
In a third aspect of the embodiments of the present disclosure, an electronic device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the above method when executing the computer program.
In a fourth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, which stores a computer program, which when executed by a processor, implements the steps of the above-mentioned method.
Advantageous effects
Compared with the prior art, the embodiment of the disclosure has the advantages that at least: by recording the current iteration version information of the target project under the condition that the target project operates normally, responding to the detected iteration version regression instruction, acquiring the target iteration version information corresponding to the iteration version regression instruction, and setting the target iteration version information as the current operation iteration version information of the target project, the iteration version can be automatically changed based on the recorded iteration version information, the workload is greatly reduced, and the labor cost is greatly saved.
Drawings
To more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings needed for the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without inventive efforts.
FIG. 1 is a schematic diagram of a scenario for a regression testing method provided in accordance with an embodiment of the present disclosure;
FIG. 2 is a flow diagram of some embodiments of a regression testing method provided in accordance with embodiments of the present disclosure;
FIG. 3 is a flow diagram of further embodiments of another regression testing method provided in accordance with embodiments of the present disclosure;
FIG. 4 is a schematic diagram illustrating a simplified structure of a regression testing apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic diagram of an electronic device provided in accordance with an embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be further noted that, for the convenience of description, only the portions relevant to the present disclosure are shown in the drawings. The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different systems, devices, modules or units, and are not used for limiting the order or interdependence of the functions executed by the systems, devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 is a schematic diagram of one application scenario of a regression testing method according to some embodiments of the present disclosure.
In the application scenario of fig. 1, the item may run between the client device 102 and the server device 103, and the computing device 101 may forward data or requests between the client device 102 and the server device 103. Project runtime may perform data and request transfers between client device 102 and server device 103 and be processed by client device 102 and/or server device 103. The client device 102 and the server device 103 may communicate based on any communication protocol or communication mode of the present or future inventions. By way of example, the client device 102 and the server device 103 may operate based on a hypertext Transfer Protocol (HTTP), and are not particularly limited herein.
In addition, the computing device 101 may first record the current iteration version information of the target item when the target item is operating normally based on the current iteration version information. Subsequently, in response to detecting the iterative version regression instruction, the computing device 101 may select target iterative version information from the recorded iterative version information and set the target iterative version information as current iterative version information based on which the target item is run.
Any one of the computing device 101, the client device 102, or the server device 103 may be hardware or software. When the device is hardware, the device may be implemented as a distributed cluster formed by a plurality of servers or terminal devices, or may be implemented as a single server or a single terminal device. When the device is embodied as software, it can be installed in the hardware devices enumerated above. It may be implemented, for example, as multiple software or software modules to provide distributed services, or as a single software or software module. And is not particularly limited herein.
It should be understood that the number of computing devices in FIG. 1 is merely illustrative. There may be any number of computing devices, as implementation needs dictate.
With continued reference to fig. 2, a flow 200 of some embodiments of a regression testing method according to the present disclosure is shown. The method may be performed by the computing device 101 of fig. 1. The regression testing method comprises the following steps:
in step 201, in some embodiments, an executing entity (e.g., the computing device 101 shown in fig. 1) of the regression testing method may connect target devices (e.g., the client device 102 and the server device 103) through a wired connection or a wireless connection, and then record current iteration version information of the target item if the target item operates normally based on the current iteration version information.
It should be noted that the wireless connection means may include, but is not limited to, a 3G/4G/5G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, an UWB (ultra wideband) connection, and other wireless connection means now known or developed in the future.
The target item may refer to a software item for performing the iteration. The iteration version information may refer to related information processed through each request processing interface in the operation process in the iteration version of the current operation of the target item. A request processing interface may refer to a software interface used to process data and/or requests during the operation of a project. As an example, the request processing interface may comprise a client identification interface for a client identification in the project, the client may send a client identification confirmation request to the client identification interface of the server, and then the server may send relevant information indicating pass or fail identification for the client identification confirmation request from the client identification interface to the client.
In some optional implementations of some embodiments, the iterative version information includes at least one request processing interface for processing a request issued by the target item, and the interface state information corresponding to each request processing interface includes at least one of interface identification information, an interface return state code, error information, and error time.
The interface identification information may refer to identification information for identifying each interface. The interface return status code may refer to an identification code returned for different communication situations in any communication protocol framework. As an example, the communication protocol may be a state code based on the HTTP protocol, which may include several types of state codes: 100-199 are used to specify certain actions that the client should take accordingly. 200-299 are used to indicate that the request was successful. 300-399 for files that have been moved and are often included in positioning header information specifying new address information. 400-499 is used to indicate errors on the client. 500-599 are used to support server errors. The status code may also be a status code based on other communication protocols, and is not limited herein.
The error information may refer to error information for a request sent by a server or a client during the operation of a project. The error reporting information may be information manually set for different error types, or error reporting information preset for different error types by a type framework, a protocol, a resource library, and the like. Also taking the client identifier interface as an example, when the client information is wrong, the ERROR reporting information may be "client identifier ERROR", "fault", "ERROR001", or "001", and the like, and is set as required, and is not limited herein. When the customer information is correct, the error information may be null, or the error information may be information indicating correct, such as "correct", "YES", or "000", where "000" and "001" may be preset simple representations for referring to different processing results.
The error reporting time can indicate the relative time or the real time corresponding to the error information, and is set according to the requirement.
The normal operation can mean that all relevant interfaces in the operation process of the target item based on the current iteration version information are in a normal operation state.
In some optional implementations of some embodiments, the execution subject may determine whether the target item operates normally based on the current iteration version information by: capturing interface state information corresponding to at least one request processing interface corresponding to the current iteration version information in the process of operating the target item based on the current iteration version information; judging whether the interface state information corresponding to each request processing interface indicates that the request processing is successful; and if the interface state information corresponding to each request processing interface indicates that the request processing is successful, indicating that the target item normally operates based on the current iteration version information.
In some optional implementation manners of some embodiments, if interface state information corresponding to any one request processing interface indicates that request processing fails, it indicates that the target item runs abnormally based on current iteration version information.
In some preferred implementation manners of some embodiments, determining whether the interface state information corresponding to each request processing interface indicates that the request processing is successful includes: if the interface return status code and the error information of the interface status information corresponding to any request processing interface indicate that the request processing is successful, indicating that the interface status information corresponding to each request processing interface indicates that the request processing is successful; if the interface of the interface state information corresponding to any request processing interface returns the state code and/or the error information represents the request processing failure, the interface state information corresponding to each request processing interface represents the request processing failure. The interface returns the state code and sets corresponding content according to the preset state code to judge whether the corresponding processing result shows success or failure. And when error information appears in the error reporting information, the processing result is failed, otherwise, the processing result is successful when no error reporting information exists or the error reporting information shows that the processing is successful.
In some optional implementations of some embodiments, in a case that the target item runs abnormally based on the current iteration version information, generating an abnormality hint information. The exception prompting information can be displayed in the generated exception prompting interface, and can also be sent to the target equipment or the target module. The exception hint information may include information about the corresponding request processing interface.
In some optional implementations of some embodiments, the exception prompting information may be displayed based on: and displaying a first interface containing each request processing interface and interface state information thereof, wherein the display color of the interface state information representing successful request processing is different from the display color of the interface state information representing failed request processing. The first interface may refer to an interface for displaying exception prompting information. In addition, in some examples, the display color of the interface state information indicating that the request processing is successful is green, and/or the display color of the interface state information indicating that the request processing is failed is red.
In some optional implementations of some embodiments, the method further comprises: and after the target item is operated based on the current iteration version information, generating a test report corresponding to the current iteration version information so as to analyze the interface state information indicating the request processing failure, wherein the test report comprises at least one piece of interface state information indicating the request processing failure. The test report may refer to a data report in which at least one interface status information is recorded. For example, the test report may include interface status information of all request processing interfaces, may only include interface status information of processing failure, and may also include interface status information of at least one specific request processing interface set according to user requirements.
In some optional implementations of some embodiments, the method further comprises: selecting at least one iteration version information from the iteration version information which has finished the operation of the target project, and generating a corresponding statistical test report to analyze the interface state information indicating the processing failure of the request, wherein the test report comprises at least one interface state information indicating the processing failure of the request. The comprehensive test report may refer to a data report for counting information related to each request processing interface in at least one iteration version. The comprehensive test report can be used for comprehensively analyzing information of a plurality of iterative versions and finding out request processing interface information with target characteristics, such as a request processing interface with poor stability. The comprehensive test report is set, so that a tester can conveniently carry out interface optimization according to corresponding development of the report reminding project member, and a project principal can conveniently know the problem of the project more intuitively.
It should be noted that the test report may be automatically generated after the target project is run based on the current iteration version information, and the statistical test report may be generated according to the requirement of the user.
Step 202, in response to the detection of the iterative version regression instruction, selecting target iterative version information from the recorded iterative version information, setting the target iterative version information as current iterative version information, and operating the target item based on the current iterative version information.
In some embodiments, in response to detecting an iterative version regression instruction, the execution subject may select target iterative version information from the recorded iterative version information, set the target iterative version information as current iterative version information, and run the target item based on the current iterative version information.
The iterative version regression instruction may refer to an instruction for replacing currently-running iterative version information of the target item with the iterative version regression instruction corresponding to the iterative version regression instruction and selecting target iterative version information from recorded iterative version information. The target iteration version information is set as the current iteration version information, the target item is operated based on the current iteration version information, and conversion among different iteration versions can be realized very simply.
In some optional implementations of some embodiments, the method further comprises: and under the condition that the target item normally operates based on the current iteration version information, setting a timing execution task to enable the target item to repeatedly execute the step of capturing interface state information corresponding to at least one interface corresponding to the current iteration version information in the process of operating the target item based on the current iteration version information every other preset time. By setting a timing task and repeatedly executing the steps, errors generated in the normal operation process of the detection target item can be more, and errors can be more effectively avoided in a non-iteration period, even system crash (such as database crash, interface abnormity and the like) caused by errors can be more effectively avoided.
The beneficial effects of one of the above embodiments of the present disclosure at least include: by recording the current iteration version information of the target project under the condition that the target project operates normally, responding to the detected iteration version regression instruction, acquiring the target iteration version information corresponding to the iteration version regression instruction, and setting the target iteration version information as the current operation iteration version information of the target project, the iteration version can be automatically changed based on the recorded iteration version information, the workload is greatly reduced, and the labor cost is greatly saved.
With continued reference to FIG. 3, a flow 300 of further embodiments of regression testing methods according to the present disclosure is illustrated, which may be performed by computing device 101 of FIG. 1. The regression testing method comprises the following steps:
step 301, recording current iteration version information of a target item under the condition that the target item normally operates based on the current iteration version information, wherein the iteration version information includes at least one request processing interface for processing a request sent by the target item, and interface state information corresponding to each request processing interface includes at least one of interface identification information, an interface return state code, error reporting information and error reporting time.
Step 302, in response to the detection of the iterative version regression instruction, selecting target iterative version information from the recorded iterative version information, setting the target iterative version information as current iterative version information, and operating the target item based on the current iterative version information.
Step 303, capturing interface state information corresponding to at least one request processing interface corresponding to the current iteration version information in the process of operating the target item based on the current iteration version information.
Step 304, determine whether the interface status information corresponding to each request processing interface indicates that the request processing is successful.
Step 305, if the interface state information corresponding to all the request processing interfaces indicates that the request processing is successful, indicating that the target item normally operates based on the current iteration version information.
Step 306, if the interface state information corresponding to any request processing interface indicates that the request processing fails, it indicates that the target item operates abnormally based on the current iteration version information.
And 307, generating abnormal prompt information under the condition that the target item operates abnormally based on the current iteration version information.
And 308, setting a timing execution task to enable the target item to repeatedly execute the step of capturing interface state information corresponding to at least one interface corresponding to the current iteration version information every other preset time length in the process of running the target item based on the current iteration version information.
In some embodiments, the detailed implementation and technical effects of steps 301 to 308 may refer to steps 201 to 202 in those embodiments corresponding to fig. 2, and are not described herein again.
All the above optional technical solutions may be combined arbitrarily to form optional embodiments of the present application, and are not described herein again.
The following are embodiments of the disclosed apparatus that may be used to perform embodiments of the disclosed methods. For details not disclosed in the embodiments of the apparatus of the present disclosure, refer to the embodiments of the method of the present disclosure.
With further reference to fig. 4, as an implementation of the above-described methods for the above-described figures, the present disclosure provides some embodiments of regression testing devices, which correspond to those method embodiments described above for fig. 2.
As shown in fig. 4, the regression testing apparatus 400 of some embodiments includes:
the recording module 401 is configured to record current iteration version information of a target item under the condition that the target item normally operates based on the current iteration version information;
a selecting module 402, configured to, in response to detecting an iterative version regression instruction, select target iterative version information from the recorded iterative version information, set the target iterative version information as current iterative version information, and run the target item based on the current iterative version information.
In some optional implementations of some embodiments, the iteration version information includes at least one request processing interface for processing a request issued by the target item, and the interface state information corresponding to each request processing interface includes at least one of interface identification information, an interface return state code, error information, and error time.
In some optional implementations of some embodiments, the regression testing apparatus 400 further includes: the grabbing module is used for grabbing interface state information corresponding to at least one request processing interface corresponding to the current iteration version information in the process of operating the target project based on the current iteration version information; the judging module is used for judging whether the interface state information corresponding to each request processing interface indicates that the request processing is successful; and the normal representation module is used for representing that the target item normally operates based on the current iteration version information if the interface state information corresponding to each request processing interface represents that the request processing is successful.
In some optional implementation manners of some embodiments, the determining whether the interface state information corresponding to each request processing interface indicates that the request processing is successful includes: if the interface return status code and the error information of the interface status information corresponding to any request processing interface indicate that the request processing is successful, indicating that the interface status information corresponding to each request processing interface indicates that the request processing is successful; if the interface of the interface state information corresponding to any request processing interface returns the state code and/or the error information represents the request processing failure, the interface state information corresponding to each request processing interface represents the request processing failure.
In some optional implementations of some embodiments, the regression test apparatus 400 further includes: and the operation exception representing module is used for representing that the target item operates abnormally based on the current iteration version information if the interface state information corresponding to any request processing interface represents that the request processing fails.
In some optional implementations of some embodiments, the regression testing apparatus 400 further includes: and the exception prompt message module is used for generating exception prompt messages under the condition that the target item runs abnormally based on the current iteration version information.
In some optional implementations of some embodiments, the regression testing apparatus 400 further includes: and the first interface display module is used for displaying a first interface containing each request processing interface and interface state information thereof, wherein the display color of the interface state information representing successful request processing is different from the display color of the interface state information representing failed request processing.
In some optional implementations of some embodiments, the interface status information indicating that the request processing is successful is displayed in green, and/or the interface status information indicating that the request processing is failed is displayed in red.
In some optional implementations of some embodiments, the regression test apparatus 400 further includes: and the test report generation module is used for generating a test report corresponding to the current iteration version information after the target item is operated based on the current iteration version information so as to analyze the interface state information indicating the request processing failure, wherein the test report comprises at least one piece of interface state information indicating the request processing failure.
In some optional implementations of some embodiments, the regression test apparatus 400 further includes: and the statistical test report generation module is used for selecting at least one iteration version information from the iteration version information which has finished the operation of the target project, and generating a corresponding statistical test report so as to analyze the interface state information indicating the processing failure of the request, wherein the test report comprises at least one interface state information indicating the processing failure of the request.
In some optional implementations of some embodiments, in a case where the target item normally operates based on the current iteration version information, the regression testing apparatus 400 further includes: and the timing task setting module is used for setting a timing execution task so as to enable the target project to repeatedly execute the step of capturing interface state information corresponding to at least one interface corresponding to the current iteration version information in the process of operating the target project based on the current iteration version information at intervals of preset time.
It is understood that the modules recited in the apparatus 400 correspond to the various steps in the method described with reference to fig. 2. Thus, the operations, features and resulting advantages described above for the method are also applicable to the apparatus 400 and the modules included therein, and are not described herein again.
As shown in fig. 5, electronic device 500 may include a processing means (e.g., central processing unit, graphics processor, etc.) 501 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 502 or a program loaded from a storage means 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the electronic apparatus 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
Generally, the following devices may be connected to the I/O interface 505: input devices 506 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 507 including, for example, a Liquid Crystal Display (LCD), speakers, vibrators, and the like; storage devices 508 including, for example, magnetic tape, hard disk, etc.; and a communication device 509. The communication means 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. While fig. 5 illustrates an electronic device 500 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided. Each block shown in fig. 5 may represent one device or may represent multiple devices as desired.
In particular, according to some embodiments of the present disclosure, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In some such embodiments, the computer program may be downloaded and installed from a network via the communication means 509, or installed from the storage means 508, or installed from the ROM 502. The computer program, when executed by the processing device 501, performs the above-described functions defined in the methods of some embodiments of the present disclosure.
It should be noted that the computer readable medium described above in some embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In some embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the apparatus; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to perform the steps described above.
Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in some embodiments of the present disclosure may be implemented by software or hardware. The modules described may also be provided in a processor.
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems on a chip (SOCs), complex Programmable Logic Devices (CPLDs), and the like.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is made without departing from the inventive concept as defined above. For example, the above features and (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure are mutually replaced to form the technical solution.

Claims (14)

1. A regression testing method, comprising:
recording current iteration version information of a target project under the condition that the target project normally operates based on the current iteration version information;
and responding to the detected iteration version regression instruction, selecting target iteration version information from the recorded iteration version information, setting the target iteration version information as current iteration version information, and operating the target item based on the current iteration version information.
2. The method of claim 1, wherein the iterative version information includes at least one request processing interface for processing a request issued by the target item, and the interface status information corresponding to each request processing interface includes at least one of interface identification information, an interface return status code, error information, and error time.
3. The method of claim 2, further comprising:
capturing interface state information corresponding to at least one request processing interface corresponding to the current iteration version information in the process of operating the target item based on the current iteration version information;
judging whether the interface state information corresponding to each request processing interface represents the success of request processing;
and if the interface state information corresponding to all the request processing interfaces indicates that the request processing is successful, indicating that the target item normally operates based on the current iteration version information.
4. The method of claim 3, wherein the determining whether the interface state information corresponding to each request processing interface indicates that the request processing is successful comprises:
if the interface return status code and the error information of the interface status information corresponding to any request processing interface both indicate that the request processing is successful, the interface status information corresponding to the request processing interface indicates that the request processing is successful;
and if the interface of the interface state information corresponding to any request processing interface returns a state code and/or error report information indicating that the request processing fails, the interface state information corresponding to the request processing interface indicates that the request processing fails.
5. The method of claim 3, further comprising:
and if the interface state information corresponding to any request processing interface indicates that the request processing fails, indicating that the target item operates abnormally based on the current iteration version information.
6. The method of claim 5, further comprising:
and generating abnormal prompt information under the condition that the target item operates abnormally based on the current iteration version information.
7. The method of claim 5, further comprising:
and displaying a first interface containing each request processing interface and interface state information thereof, wherein the display color of the interface state information indicating that the request processing is successful is different from the display color of the interface state information indicating that the request processing is failed.
8. The method according to claim 7, wherein the display color of the interface status information indicating that the request processing is successful is green, and/or the display color of the interface status information indicating that the request processing is failed is red.
9. The method of claim 5, further comprising:
and after the target item is operated based on the current iteration version information, generating a test report corresponding to the current iteration version information so as to analyze the interface state information indicating the request processing failure, wherein the test report comprises at least one piece of interface state information indicating the request processing failure.
10. The method of claim 5, further comprising:
selecting at least one iteration version information from the iteration version information which has finished the operation of the target project, and generating a corresponding statistical test report to analyze the interface state information indicating the processing failure of the request, wherein the test report comprises at least one interface state information indicating the processing failure of the request.
11. The method of claim 3, wherein in the case that the target item is operating normally based on current iteration version information, the method further comprises:
and setting a timing execution task to enable the target item to repeatedly execute the step of capturing interface state information corresponding to at least one interface corresponding to the current iteration version information every other preset time length in the process of operating the target item based on the current iteration version information.
12. A regression testing apparatus, comprising:
the recording module is used for recording the current iteration version information of the target project under the condition that the target project normally operates based on the current iteration version information;
and the selection module is used for responding to the detected iteration version regression instruction, selecting target iteration version information from the recorded iteration version information, setting the target iteration version information as current iteration version information, and operating the target item based on the current iteration version information.
13. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 11 when executing the computer program.
14. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 11.
CN202210986985.4A 2022-08-17 2022-08-17 Regression testing method, device, electronic equipment and computer readable storage medium Pending CN115470105A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210986985.4A CN115470105A (en) 2022-08-17 2022-08-17 Regression testing method, device, electronic equipment and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210986985.4A CN115470105A (en) 2022-08-17 2022-08-17 Regression testing method, device, electronic equipment and computer readable storage medium

Publications (1)

Publication Number Publication Date
CN115470105A true CN115470105A (en) 2022-12-13

Family

ID=84365706

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210986985.4A Pending CN115470105A (en) 2022-08-17 2022-08-17 Regression testing method, device, electronic equipment and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN115470105A (en)

Similar Documents

Publication Publication Date Title
CN112650685B (en) Automatic test method, device, electronic equipment and computer storage medium
CN113495820B (en) Anomaly information collecting and processing method and device and anomaly monitoring system
CN114356785B (en) Data processing method and device, electronic equipment and storage medium
CN112084114B (en) Method and apparatus for testing interfaces
CN107315672B (en) Method and device for monitoring server
CN109218338B (en) Information processing system, method and device
US11121912B2 (en) Method and apparatus for processing information
CN115470105A (en) Regression testing method, device, electronic equipment and computer readable storage medium
CN107342917B (en) Method and apparatus for detecting network device performance
CN111290873B (en) Fault processing method and device
CN109960659B (en) Method and device for detecting application program
CN112445697B (en) Method and apparatus for testing applications
CN113704079B (en) Protobuf-based interface testing method and device
CN116560918A (en) Pressure testing method, device, equipment and medium
CN115705258A (en) Test method, test device, storage medium and electronic equipment
CN114443480A (en) Test method, test system, readable medium and electronic device
CN114968696A (en) Index monitoring method, electronic equipment and chip system
CN110022244B (en) Method and apparatus for transmitting information
CN112671822B (en) Service request processing method, device, storage medium, server and system
CN118041804B (en) Communication equipment networking data detection method and device, electronic equipment and readable medium
CN112559087B (en) Information generation method, apparatus, electronic device and computer readable medium
CN113778800B (en) Error information processing method, device, system, equipment and storage medium
CN114884807B (en) Link log generation method and device, internet of things platform and storage medium
CN113760590A (en) Fault processing method and device, electronic equipment and computer readable medium
CN113760635A (en) Method and device for determining connection abnormity, 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