A health code iteration testing method and device, electronic equipment and storage medium

Abstract

The application discloses a health code iteration test method and device, electronic equipment and a storage medium; the method comprises the following steps: acquiring an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system; based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, respectively determining a field-level change point and a pixel-level change point of the health code system; based on the field-level change point and the pixel-level change point of the health code system, performing iteration test on the health code system. The embodiment of the application can perform iteration test on the health code system based on multi-level differences, achieve field-level and pixel-level change control monitoring, thereby improving test efficiency and guaranteeing perfect test results.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of health code iteration testing, and in particular to a health code iteration testing method and device, electronic equipment and a storage medium. BACKGROUND

[0002] Iteration is an activity of repeating a feedback process, and the purpose is usually to approach a desired target or result. Each repetition of the process is called an iteration, and the result of each iteration is used as the initial value for the next iteration. Iterative development of software refers to dividing system work into a series of small, fixed-period projects, and each iteration includes requirement analysis, design, implementation and testing, and through gradual improvement, a more perfect software system is created.

[0003] Health code iteration testing is a process of evaluating and verifying whether a health code application is running as expected. The purpose of testing includes preventing software errors, reducing development costs and improving software performance. There are currently many different types of health code iteration testing, among which, functional testing is to verify the functions of a product, and according to product characteristics, operation description and user scheme, the characteristics and operable behavior of a product are tested to determine whether they meet the design requirements.

[0004] The health code system is a personal exclusive two-dimensional code system based on personal health data during the epidemic period, generated through comprehensive research and judgment of multiple data channels in the background. As a basic system for access during the epidemic period, it dynamically displays the personal epidemic risk level (red, yellow, green) to achieve the purpose of precise epidemic prevention and control.

[0005] With the increasing pace of version iteration, the quality assurance of test engineers faces great challenges. In the old mode, test engineers rely on the content provided by development engineers for system testing. The change points are actively provided by the development, and the test engineers lack the ability to independently judge the change points. In the process of continuous version iteration, it is easy to appear that the document is not supplemented in time, the personnel flow, and the like, the history iteration accumulation is lost, and the technical debt is high. Therefore, a system is needed to record the interface request situation and page UI situation of all versions. SUMMARY

[0006] The present application provides a health code iteration testing method, device, electronic equipment and storage medium, which can perform iteration testing on the health code system based on multi-level differences, achieve field-level and pixel-level change control monitoring, and thus improve the testing efficiency and ensure perfect test results.

[0007] In a first aspect, the embodiments of the present application provide a health code iteration testing method, which comprises:

[0008] acquire an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system;

[0009] determine a field-level change point and a pixel-level change point of the health code system based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, respectively;

[0010] perform iterative testing on the health code system based on the field-level change point and the pixel-level change point of the health code system.

[0011] In a second aspect, the embodiments of the present application further provide a health code iterative testing device, the device comprising: an acquisition module, a determination module and a testing module; wherein,

[0012] The acquisition module is configured to acquire an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system.

[0013] The determination module is configured to determine a field-level change point and a pixel-level change point of the health code system based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, respectively.

[0014] The testing module is configured to perform iterative testing on the health code system based on the field-level change point and the pixel-level change point of the health code system.

[0015] In a third aspect, the embodiments of the present application provide an electronic device, comprising:

[0016] one or more processors;

[0017] a memory configured to store one or more programs,

[0018] When the one or more programs are executed by the one or more processors, the one or more processors implement the health code iterative testing method according to any of the embodiments of the present application.

[0019] In a fourth aspect, the embodiments of the present application provide a storage medium having a computer program stored thereon, which is executed by a processor to implement the health code iterative testing method according to any of the embodiments of the present application.

[0020] The embodiment of the application provides a health code iterative testing method and device, electronic equipment and a storage medium. The interface request body and response body of a first version of a health code system and the interface request body and response body of a second version are acquired. Then, based on the interface request body and response body of the first version and the interface request body and response body of the second version, the field-level change point and the pixel-level change point of the health code system are determined respectively. Then, based on the field-level change point and the pixel-level change point of the health code system, the health code system is iteratively tested. That is, in the technical solution of the application, the health code system can be iteratively tested based on multi-level differences. In the prior art, the change points are actively provided by the development, and the test engineers lack the ability to independently judge the change points. In the process of continuous version iteration, the document supplement is not timely, the personnel flow occurs, the historical iteration accumulation is lost, and the technical debt is high. Therefore, compared with the prior art, the health code iterative testing method, device, electronic equipment and storage medium provided by the embodiment of the application can iteratively test the health code system based on multi-level differences, achieve field-level and pixel-level change control monitoring, thereby improving the test efficiency and guaranteeing perfect test results. In addition, the technical solution of the embodiment of the application is simple and convenient, easy to popularize, and has a wider application range. BRIEF DESCRIPTION OF DRAWINGS DETAILED DESCRIPTION OF THE INVENTION BRIEF DESCRIPTION OF DRAWINGS

[0021] Figure 1 A first flowchart of a health code iterative testing method provided by the embodiment of the application is shown in the figure.

[0022] Figure 2 A second flowchart of a health code iterative testing method provided by the embodiment of the application is shown in the figure.

[0023] Figure 3 A third flowchart of a health code iterative testing method provided by the embodiment of the application is shown in the figure.

[0024] Figure 4 A structure diagram of a health code iterative testing device provided by the embodiment of the application is shown in the figure.

[0025] Figure 5 A structure diagram of electronic equipment provided by the embodiment of the application is shown in the figure. DETAILED DESCRIPTION

[0026] The application will be further described in detail below with reference to the drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the application, but not to limit the application. In addition, it should be noted that, in order to facilitate description, only parts related to the application are shown in the drawings, not all structures.

[0027] Embodiment one

[0028] Figure 1A first flowchart of a health code iteration test method provided by the embodiments of the present application is shown in FIG. 1. The method can be executed by a health code iteration test device or an electronic device, which can be implemented in software and / or hardware, and can be integrated into any smart device with network communication function. As shown in FIG. 1, the health code iteration test method can include the following steps: Figure 1

[0029] S101, obtaining an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system.

[0030] In this step, the electronic device can obtain an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system, respectively. Specifically, the electronic device can send a first HTTP request message and a second HTTP request message to a server through the health code system, respectively; then receive a first HTTP return message returned by the server in response to the first HTTP request message and a second HTTP return message returned by the server in response to the second HTTP request message; wherein the first HTTP request message and the first HTTP return message are the interface request body and the response body of the first version, respectively; and the second HTTP request message and the second HTTP return message are the interface request body and the response body of the second version, respectively.

[0031] S102, determining a field-level change point and a pixel-level change point of the health code system based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, respectively.

[0032] In this step, the electronic device can determine a field-level change point and a pixel-level change point of the health code system based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, respectively. Specifically, the method for the electronic device to determine the field-level change point of the health code system can include the following steps: first, differentially compare the interface request body of the first version and the interface request body of the second version to obtain a differential comparison result of the interface request body of the first version and the interface request body of the second version; then differentially compare the response body of the second version and the response body of the second version to obtain a differential comparison result of the response body of the second version and the response body of the second version; and then determine the field-level change point of the health code system according to the differential comparison result of the interface request body of the first version and the interface request body of the second version and the differential comparison result of the response body of the second version and the response body of the second version.

[0033] S103, performing iteration test on the health code system based on the field-level change point and the pixel-level change point of the health code system.

[0034] ​In this step, the electronic device can perform iterative testing on the health code system based on the field-level change point and the pixel-level change point of the health code system. Specifically, the electronic device can first perform testing on the field-level change point of the health code system, and then perform testing on the pixel-level change point of the health code system.

[0035] The health code iterative testing method provided in the embodiments of the present application first acquires the interface request body and response body of the first version and the interface request body and response body of the second version of the health code system; then determines the field-level change point and the pixel-level change point of the health code system based on the interface request body and response body of the first version and the interface request body and response body of the second version; and finally performs iterative testing on the health code system based on the field-level change point and the pixel-level change point of the health code system. That is, in the technical solution of the present application, the health code system can be iteratively tested based on multi-level differences. In the prior art, the change points are actively provided by the development, and the test engineers lack the ability to independently judge the change points. In the process of continuous version iteration, situations such as untimely document supplement and personnel flow may occur, historical iteration accumulation is lost, and technical debt is high. Therefore, compared with the prior art, the health code iterative testing method provided in the embodiments of the present application can iteratively test the health code system based on multi-level differences, achieve field-level and pixel-level change control monitoring, thereby improving the testing efficiency and ensuring perfect test results; and the technical solution of the embodiments of the present application is simple and convenient to implement, easy to popularize, and has a wider application range.

[0036] Embodiment Two

[0037] Figure 2 The second flowchart of the health code iterative testing method provided in the embodiments of the present application is shown. The above technical solution is further optimized and expanded, and can be combined with the above various optional embodiments.

[0038] As shown in Figure 2 , the health code iterative testing method can include the following steps:

[0039] S201, sending a first HTTP request message and a second HTTP request message to a server through a health code system.

[0040] In this step, the electronic device can send a first HTTP request message and a second HTTP request message to a server through a health code system. Specifically, the HTTP request in the embodiments of the present application refers to a request message from a client to a server, and the message content can include: a request method of a resource, a request identifier, a request header, a request body, etc.

[0041] The interface request body in the embodiments of the present application refers to a request message sent by a client to a server, and the response body refers to a response text in a response message returned by the server after the server receives and interprets the request message. For example, in one scenario, assuming that a user opens a search engine interface on a client, enters a keyword, and the client sends the keyword to a server of the search engine through a first interface, and the server returns search results to the client through a second interface. In the above scenario, the interface request body and the response body both refer to related information returned by an HTTP interface request. For example, the keyword entered by the user is generally used as a component of the interface request body, and the response body can include HTML tags, json return, and other information.

[0042] S202, receiving a first HTTP return message returned by the server in response to the first HTTP request message and a second HTTP return message returned by the server in response to the second HTTP request message; wherein the first HTTP request message and the first HTTP return message are respectively the interface request body and the response body of the first version; and the second HTTP request message and the second HTTP return message are respectively the interface request body and the response body of the second version.

[0043] In this step, the electronic device can receive the first HTTP return message returned by the server in response to the first HTTP request message; and can also receive the second HTTP return message returned by the server in response to the second HTTP request message. At this time, the electronic device can take the first HTTP request message and the first HTTP return message as the interface request body and the response body of the first version; and take the second HTTP request message and the second HTTP return message as the interface request body and the response body of the second version.

[0044] S203, determining the change points at the field level and the change points at the pixel level of the health code system based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, respectively.

[0045] In this step, the electronic device can determine the field-level change points and the pixel-level change points of the health code system based on the interface request body and response body of the first version and the interface request body and response body of the second version. Specifically, the method for determining the field-level change points of the health code system by the electronic device can include the following steps: first, differentially compare the interface request body of the first version and the interface request body of the second version to obtain the differential comparison result of the interface request body of the first version and the interface request body of the second version; then, differentially compare the response body of the first version and the response body of the second version to obtain the differential comparison result of the response body of the first version and the response body of the second version; and then, according to the differential comparison result of the interface request body of the first version and the interface request body of the second version and the differential comparison result of the response body of the first version and the response body of the second version, determine the field-level change points of the health code system.

[0046] Further, when differentially comparing the interface request body of the first version and the interface request body of the second version, the electronic device can first extract a field from the interface request body of the first version and the interface request body of the second version as the current first request body field and the current second request body field according to the pre-set request body field order; if the current first request body field and the current second request body field are different, the electronic device can determine the current first request body field and the current second request body field as the differential comparison result of the interface request body of the first version and the interface request body of the second version; repeat the above operation until all differential comparison results of the interface request body of the first version and the interface request body of the second version are determined.

[0047] Further, when differentially comparing the response body of the first version and the response body of the second version, the electronic device can extract a field from the response body of the first version and the response body of the second version as the current first return body field and the current second return body field according to the pre-set return body field order; if the current first return body field and the current second return body field are different, the electronic device can determine the current first return body field and the current second return body field as the differential comparison result of the response body of the first version and the response body of the second version; repeat the above operation until all differential comparison results of the response body of the first version and the response body of the second version are determined.

[0048] S204, based on the field-level change points and the pixel-level change points of the health code system, iteratively test the health code system.

[0049] In this step, the electronic device can perform iterative testing on the health code system based on the field-level change points and the pixel-level change points of the health code system. Specifically, the electronic device can first perform testing on the field-level change points of the health code system, and then perform testing on the pixel-level change points of the health code system.

[0050] The health code iterative testing method provided by the embodiments of the present application first acquires the interface request body and response body of the first version and the interface request body and response body of the second version of the health code system; then determines the field-level change points and the pixel-level change points of the health code system based on the interface request body and response body of the first version and the interface request body and response body of the second version; and finally performs iterative testing on the health code system based on the field-level change points and the pixel-level change points of the health code system. That is, in the technical solution of the present application, the health code system can be iteratively tested based on multi-level differences. In the prior art, the change points are actively provided by the development, and the test engineers lack the ability to independently determine the change points. In the process of continuous version iteration, situations such as untimely document supplement and personnel flow may occur, historical iteration accumulation is lost, and technical debt is high. Therefore, compared with the prior art, the health code iterative testing method provided by the embodiments of the present application can iteratively test the health code system based on multi-level differences, achieve field-level and pixel-level change control monitoring, thereby improving the testing efficiency and ensuring perfect test results; and the technical solution of the embodiments of the present application is simple and convenient to implement, easy to popularize, and has a wider application range.

[0051] Embodiment Three

[0052] Figure 3 The third flowchart of the health code iterative testing method provided by the embodiments of the present application is shown. The above technical solution is further optimized and expanded, and can be combined with the above various optional embodiments.

[0053] As shown in Figure 3 , the health code iterative testing method can include the following steps:

[0054] S301, a first HTTP request message and a second HTTP request message are sent to a server by a health code system respectively.

[0055] S302, a first HTTP return message returned in response to the first HTTP request message and a second HTTP return message returned in response to the second HTTP request message are received; wherein the first HTTP request message and the first HTTP return message are respectively the interface request body and the response body of the first version; and the second HTTP request message and the second HTTP return message are respectively the interface request body and the response body of the second version.

[0056] In this step, the electronic device can receive the first HTTP return message returned by the server in response to the first HTTP request message; and can also receive the second HTTP return message returned by the server in response to the second HTTP request message. At this time, the electronic device can take the first HTTP request message and the first HTTP return message as the interface request body and response body of the first version; and take the second HTTP request message and the second HTTP return message as the interface request body and response body of the second version.

[0057] S303, differentially compare the interface request body of the first version and the interface request body of the second version to obtain the differential comparison result of the interface request body of the first version and the interface request body of the second version.

[0058] In this step, the electronic device can extract a field from the interface request body of the first version and the interface request body of the second version as the current first request body field and the current second request body field according to the pre-set request body field order; if the current first request body field and the current second request body field are different, the electronic device can determine the current first request body field and the current second request body field as the differential comparison result of the interface request body of the first version and the interface request body of the second version; and repeat the above operation until all differential comparison results of the interface request body of the first version and the interface request body of the second version are determined.

[0059] S304, differentially compare the response body of the first version and the response body of the second version to obtain the differential comparison result of the response body of the first version and the response body of the second version.

[0060] In this step, the electronic device can extract a field from the response body of the first version and the response body of the second version as the current first return body field and the current second return body field according to the pre-set return body field order; if the current first return body field and the current second return body field are different, the electronic device can determine the current first return body field and the current second return body field as the differential comparison result of the response body of the first version and the response body of the second version; and repeat the above operation until all differential comparison results of the response body of the first version and the response body of the second version are determined.

[0061] S305, according to the differential comparison result of the interface request body of the first version and the interface request body of the second version and the differential comparison result of the response body of the second version and the response body of the second version, determine the field level change point of the health code system.

[0062] In this step, the electronic device can determine the field-level change point of the health code system according to the differential comparison result of the interface request body of the first version and the interface request body of the second version and the differential comparison result of the response body of the first version and the response body of the second version. For example, for a certain field, if there is a difference between the interface request body of the first version and the interface request body of the second version, it is considered that the field is a field-level change point of the health code system; or for a certain field, if there is a difference between the response body of the first version and the response body of the second version, it can also be considered that the field is a field-level change point of the health code system.

[0063] S306, generate a first version of the page screenshot based on the interface request body and the response body of the first version.

[0064] In this step, the electronic device can generate a first version of the page screenshot based on the interface request body and the response body of the first version. Specifically, the user can send a first HTTP request to the server through the client, and the server returns a first HTTP response, at which time the client can generate a first version of the page screenshot based on the first HTTP request and the first HTTP response.

[0065] S307, generate a second version of the page screenshot based on the interface request body and the response body of the second version.

[0066] In this step, the electronic device can generate a second version of the page screenshot based on the interface request body and the response body of the second version. Specifically, the user can send a second HTTP request to the server through the client, and the server returns a second HTTP response, at which time the client can generate a second version of the page screenshot based on the second HTTP request and the second HTTP response.

[0067] S308, determine the pixel-level change point of the health code system according to the first version of the page screenshot and the second version of the page screenshot.

[0068] In this step, the electronic device can determine the pixel-level change point of the health code system according to the first version of the page screenshot and the second version of the page screenshot. Specifically, the electronic device can extract a pixel point as a current first pixel point and a current second pixel point in the first version of the page screenshot and the second version of the page screenshot according to a pre-set pixel order; if the current first pixel point and the current second pixel point are different, the electronic device can determine the current first pixel point and the current second pixel point as the pixel-level change point of the health code system; repeat the above operation until all the pixel-level change points of the health code system are determined.

[0069] S309, iteratively test the health code system based on the field-level change point and the pixel-level change point of the health code system.

[0070] In specific embodiments of the present application, the electronic device can also take the first version of the response body and the header of the first version of the response body, and the second version of the response body and the header of the second version of the response body as the simulation values of the first version interface and the second version interface respectively; and then based on the simulation values of the first version interface and the second version interface, save the first version of the page screenshot and the second version of the page screenshot. In this way, the test results can be saved and traced based on version management, providing support for system iteration.

[0071] The health code iteration test method provided in the embodiments of the present application first acquires the interface request body and response body of the first version and the interface request body and response body of the second version of the health code system; then based on the interface request body and response body of the first version and the interface request body and response body of the second version, respectively determines the field-level change points and the pixel-level change points of the health code system; and then based on the field-level change points and the pixel-level change points of the health code system, iteratively tests the health code system. That is, in the technical solution of the present application, the health code system can be iteratively tested based on multi-level differences. In the prior art, the change points are actively provided by the development, and the test engineers lack the ability to independently judge the change points. In the process of continuous iteration of the version, it is easy to appear that the document is not supplemented in time, the personnel flow, the loss of historical iteration accumulation, and the high technical debt. Therefore, compared with the prior art, the health code iteration test method provided in the embodiments of the present application can iteratively test the health code system based on multi-level differences, achieve field-level and pixel-level change control monitoring, so as to improve the test efficiency and guarantee perfect test results; and the technical solution of the embodiments of the present application is simple and convenient to implement, easy to popularize, and has a wider application range.

[0072] Embodiment Four

[0073] Figure 4 The structure schematic diagram of the health code iteration test device provided in the embodiments of the present application is shown in FIG. 1. As shown in FIG. 1, the health code iteration test device includes an acquisition module 401, a determination module 402 and a test module 403. Figure 4

[0074] The acquisition module 401 is configured to acquire the interface request body and response body of the first version and the interface request body and response body of the second version of the health code system.

[0075] The determination module 402 is configured to determine the field-level change points and the pixel-level change points of the health code system based on the interface request body and response body of the first version and the interface request body and response body of the second version.

[0076] ​The test module 403 is configured to perform iterative testing on the health code system based on the field-level change points and the pixel-level change points of the health code system.

[0077] The health code iterative testing device described above can perform the method provided by any of the embodiments of the present application, has the corresponding function modules and beneficial effects of performing the method. Technical details not described in detail in the present embodiment can be referred to the health code iterative testing method provided by any of the embodiments of the present application.

[0078] Embodiment five

[0079] Figure 5 The structural schematic diagram of the electronic device provided by the embodiments of the present application is shown. Figure 5 A block diagram of an exemplary electronic device suitable to implement embodiments of the present application is shown. Figure 5 The electronic device 12 shown is merely one example and should not be taken as limiting the scope of functionality or use of embodiments of the present application.

[0080] As shown in Figure 5 The electronic device 12 is in the form of a general-purpose computing device. Components of electronic device 12 can include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including system memory 28 and processing unit 16.

[0081] Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics bus, a processor or local bus using any of a variety of bus architectures. By way of example, these architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0082] Electronic device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by electronic device 12 and includes both volatile and non-volatile media, removable and non-removable media.

[0083] System memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Electronic device 12 can further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a "hard drive"). Figure 5 Not shown, is typically called a "hard disk drive") for reading from and writing to non-removable, non-volatile magnetic media (not shown and typically called a "hard drive"). Although Figure 5A disk drive, a floppy disk drive, a CD-ROM drive, a DVD-ROM drive, or other removable media drive, a flash memory card drive, a multimedia arcade game drive, and / or a hard disk drive can be provided in the computer system 10, as shown in FIG. 1. Each of these drives can be connected to the system bus 18 by one or more drive interfaces. The drives and their associated computer-readable media provide nonvolatile storage of data, data files, computer-readable instructions (e.g., application programs), and the like for the computer system 10. Although the exemplary environment described herein employs a hard disk, a removable magnetic disk, a removable optical disk, or a flash memory card as storage media for computer-readable instructions, programs, and data, who skilled in the art will appreciate that other types of storage media that are readable by a computer system 10, such as zip drives, magnetic cassettes, tape, cartridges, redundant array of independent disks (RAID) systems, and the like, can also be used in the exemplary operating environment. In the illustrated embodiment, a number of program modules and data files are stored in the system memory 28. While the exemplary computer system 10 is described as employing a system memory 28, who skilled in the art will appreciate that the computer system 10 can employ both system memory and removable computer-readable media, such as a floppy disk, a CD-ROM, and / or a flash memory card, to store program modules, data, and the like. In this illustrative example, the computer system 10 includes a system memory 28, a processor 16, and a system bus 18. The system bus 18 communicatively couples system memory 28 to processor 16. Although the computer system 10 is described as employing a system bus 18, who skilled in the art will appreciate that the computer system 10 can employ any of a variety of bus architectures, including, but not limited to, an Industry Standard Architecture (ISA) bus, an Enhanced ISA (EISA) bus, a Micro Channel Architecture (MCA) bus, a Video Electronics Standards Association (VESA) local bus, an Accelerated Graphics Port (AGP) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express bus, a Personal Computer Memory Card International Association (PCMCIA) bus, and the like, to communicatively couple the system memory 28 to the processor 16. The system memory 28 includes computer-readable instructions, program modules, and program data for the computer system 10. In this illustrative example, the system memory 28 includes operating system 30, one or more application programs 32, other program modules 34, and program data 36. The operating system 30 acts to control and allocate resources of the computer system 10. Applications 32 take advantage of the

[0084] Program / utility 40, having a set (at least one) of program modules 42, can be stored in, for example, system memory 28 by way of example, such program modules 42 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination thereof, likely include implementation of a network environment. Program modules 42 generally carry out the functions and / or methodologies of embodiments described herein.

[0085] The electronic device 12 can also communicate with one or more external devices 14 such as a keyboard or a pointing device, displays 24, etc.; other devices such as devices that enable a user to interact with the electronic device 12; and / or any devices (e.g., network card, modem, etc.) that enable the electronic device 12 to communicate with one or more other computing devices. Such communication can occur via the input / output (I / O) interface 22. Still yet, the electronic device 12 can communicate with one or more networks, such as a local area network (LAN), a wide area network (WAN), and / or the Internet, through a network adapter 20. As depicted, the network adapter 20 communicates with the other components of the electronic device 12 via the bus 18. It should be appreciated that the network adapter 20 can also be connected to one or more components of the electronic device 12 in some other fashion or in some other device entirely. Also, it should be appreciated that the bus 18 can be implemented using any type of bus structures over electrical, optical, or quantum interconnects, such as a System S bus etc. Figure 5 Other hardware and / or software modules that can be used in conjunction with the electronic device 12 can also be employed in the exemplary environment, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

[0086] The processing unit 16 performs various function applications and data processing by running programs stored in the system memory 28, such as implementing the health code iteration test method provided by the embodiments of the present application.

[0087] Embodiment six

[0088] The embodiments of the present application provide a computer storage medium.

[0089] The computer readable storage medium of the embodiments of the present application can adopt any combination of one or more computer readable media. The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium may, for example, but is not limited to, an electrical, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, device or apparatus, or any combination of the above. More specific examples (a non-exhaustive list) of the computer readable storage medium include 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 above. In this document, the computer readable storage medium can be any tangible medium that contains or stores a program used by or in connection with an instruction execution system, apparatus or device.

[0090] The computer readable signal medium can include a computer readable program code in a baseband or propagated as a carrier wave in a propagation medium. Such a propagated signal can take a wide variety of forms, including but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium can 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.

[0091] Program code embodied on a computer readable medium can be transmitted using any appropriate medium, including but not limited to wireless, wire line, optical fiber cable, RF, etc., or any suitable combination of the above.

[0092] Computer program code for carrying out operations of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can 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 latter scenario, the remote computer can 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 can be made to an external computer (for example, through the Internet using an Internet Service Provider). In an embodiment of the application, the remote computer can be a server or another desktop computer.

[0093] It is to be noted that the above-mentioned embodiments illustrate rather than limit the application, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the application. The word "comprising" does not exclude the presence of elements or steps other than those listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. It is further noted that characteristics relating to the different embodiments can be combined, and not just those within respective sections of the description.

Claims

1. A health code iteration testing method, characterized in that, Applied to a client, the method comprises: Obtaining an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system; wherein the interface request body and the response body of the first version are a first HTTP request message and a first HTTP return message respectively; the interface request body and the response body of the second version are a second HTTP request message and a second HTTP return message respectively; Based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, respectively determine the field level change point and the pixel level change point of the health code system; wherein based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, determining the field level change point of the health code system comprises: comparing the interface request body of the first version and the interface request body of the second version to obtain the difference comparison result of the interface request body of the first version and the interface request body of the second version; comparing the response body of the first version and the response body of the second version to obtain the difference comparison result of the response body of the first version and the response body of the second version; according to the difference comparison result of the interface request body of the first version and the interface request body of the second version and the difference comparison result of the response body of the first version and the response body of the second version, determining the field level change point of the health code system; Based on the field level change point and the pixel level change point of the health code system, iteratively test the health code system.

2. The method of claim 1, wherein, Obtaining an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system comprises: Sending a first hypertext transfer protocol (HTTP) request message and a second HTTP request message to a server through the health code system respectively; Receiving a first HTTP return message returned by the server in response to the first HTTP request message and a second HTTP return message returned by the server in response to the second HTTP request message.

3. The method of claim 1, wherein, Comparing the interface request body of the first version and the interface request body of the second version to obtain the difference comparison result of the interface request body of the first version and the interface request body of the second version comprises: According to the pre-set request body field order, extracting a field from the interface request body of the first version and the interface request body of the second version as a current first request body field and a current second request body field respectively; If the current first request body field and the current second request body field are different, the current first request body field and the current second request body field are determined as the difference comparison result of the interface request body of the first version and the interface request body of the second version; repeat the above operation until all difference comparison results of the interface request body of the first version and the interface request body of the second version are determined.

4. The method of claim 1, wherein, The first version of the response body is differentially compared with the second version of the response body to obtain a differential comparison result of the first version of the response body and the second version of the response body, including: A field is extracted from the first version of the response body and the second version of the response body as a current first return body field and a current second return body field according to a pre-set return body field order; If the current first return body field and the current second return body field are different, the current first return body field and the current second return body field are determined as the differential comparison result of the first version of the response body and the second version of the response body; the above operation is repeatedly performed until all differential comparison results of the first version of the response body and the second version of the response body are determined.

5. The method of claim 1, wherein, Based on the first version of the interface request body and the response body and the second version of the interface request body and the response body, a pixel-level change point of the health code system is determined, including: A first version of the page screenshot is generated based on the first version of the interface request body and the response body; A second version of the page screenshot is generated based on the second version of the interface request body and the response body; According to the first version of the page screenshot and the second version of the page screenshot, a pixel-level change point of the health code system is determined.

6. The method of claim 5, wherein, According to the first version of the page screenshot and the second version of the page screenshot, a pixel-level change point of the health code system is determined, including: A pixel point is extracted from the first version of the page screenshot and the second version of the page screenshot as a current first pixel point and a current second pixel point according to a pre-set pixel order; If the current first pixel point and the current second pixel point are different, the current first pixel point and the current second pixel point are determined as the pixel-level change point of the health code system; the above operation is repeatedly performed until all pixel-level change points of the health code system are determined.

7. The method of claim 5, wherein, The method further includes: The first version of the response body and the header of the first version of the response body, and the second version of the response body and the header of the second version of the response body are respectively taken as the simulation value of the first version interface and the simulation value of the second version interface; Based on the simulation value of the first version interface and the simulation value of the second version interface, the first version of the page screenshot and the second version of the page screenshot are saved.

8. A health code iteration testing device, characterized in that, The device includes an acquisition module, a determination module and a test module; wherein, The acquisition module is configured to acquire an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system; wherein, the interface request body and the response body of the first version are a first HTTP request message and a first HTTP return message respectively; the interface request body and the response body of the second version are a second HTTP request message and a second HTTP return message respectively; The acquisition module is configured to acquire an interface request body and a response body of a first version and an interface request body and a response body of a second version of a health code system; wherein, the interface request body and the response body of the first version are a first HTTP request message and a first HTTP return message respectively; the interface request body and the response body of the second version are a second HTTP request message and a second HTTP return message respectively; The determining module is configured to determine the field-level change point and the pixel-level change point of the health code system based on the interface request body and the response body of the first version and the interface request body and the response body of the second version, respectively; wherein, the determination of the field-level change point of the health code system based on the interface request body and the response body of the first version and the interface request body and the response body of the second version comprises: differentiating and comparing the interface request body of the first version and the interface request body of the second version to obtain a differentiated comparison result of the interface request body of the first version and the interface request body of the second version; differentiating and comparing the response body of the first version and the response body of the second version to obtain a differentiated comparison result of the response body of the first version and the response body of the second version; and determining the field-level change point of the health code system according to the differentiated comparison result of the interface request body of the first version and the interface request body of the second version and the differentiated comparison result of the response body of the first version and the response body of the second version. The testing module is configured to perform iterative testing on the health code system based on the field-level change point and the pixel-level change point of the health code system.

9. An electronic device, comprising: Comprise: One or more processors; Memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the health code iterative testing method of any one of claims 1 to 7.

10. A storage medium having stored thereon a computer program, characterized in that The program is executed by the processor to implement the health code iterative testing method of any one of claims 1 to 7.

Images