CN112711421B

CN112711421B - Cross-service Mock data sharing use method, system, equipment and storage medium

Info

Publication number: CN112711421B
Application number: CN202011583869.5A
Authority: CN
Inventors: 胡梅; 古知己
Original assignee: Guangzhou Pinwei Software Co Ltd
Current assignee: Guangzhou Pinwei Software Co Ltd
Priority date: 2020-12-28
Filing date: 2020-12-28
Publication date: 2024-04-19
Anticipated expiration: 2040-12-28
Also published as: CN112711421A

Abstract

The invention discloses a sharing use method, a system, equipment and a storage medium of cross-service Mock data, wherein the method comprises the following steps: acquiring the types of the rules and returned data in a manner of calling Mocker services by the UI automation engineering service; analyzing the type of the acquired rule and the returned data to acquire content data of which the rule is a Mock type; the content data is called and used in the process of writing and executing the UI automation use case. The invention can improve the execution efficiency of UI automation engineering, reduce the maintenance and management cost of redundant files, reduce the steps of writing automation use cases, change Mock data into visualizations, and make the operation and use simpler, more convenient and faster.

Description

Cross-service Mock data sharing use method, system, equipment and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, a system, an apparatus, and a storage medium for sharing and using cross-service Mock data.

Background

Currently, UI automation stores Mock (analog) data under a unified folder of an engineering catalog when using the Mock data, and requires storage-reading-use according to a unified storage rule. Once the Mock data is accumulated and more, after the data is huge, engineering resources are occupied, execution efficiency is affected, and meanwhile, certain manpower and resources are consumed for maintenance and application.

The above information is presented as background information only to aid in the understanding of the present disclosure and is not intended or admitted to be prior art relative to the present disclosure.

Disclosure of Invention

The invention provides a method, a system, equipment and a storage medium for sharing and using cross-service Mock data, which are used for solving the defects in the prior art.

In order to achieve the above object, the present invention provides the following technical solutions:

In a first aspect, an embodiment of the present invention provides a method for sharing and using cross-service Mock data, where the method includes:

acquiring the types of the rules and returned data in a manner of calling Mocker services by the UI automation engineering service;

Analyzing the type of the acquired rule and the returned data to acquire content data of which the rule is a Mock type;

The content data is called and used in the process of writing and executing the UI automation use case.

Further, in the method for sharing and using the service Mock data, the step of obtaining the type of the rule and the returned data by calling Mocker the service through the UI automation engineering service includes:

Initiating, by the UI automation service, an Http request to invoke showRule () interface of Mocker services to query a database of Mocker services;

The type of rule and return data is obtained from a database served by Mocker.

Further, in the method for sharing and using the service Mock data, the step of calling and using the content data in the process of writing and executing the UI automation case includes:

In the process of writing and executing UI automation use cases, monitoring and intercepting interface requests of interfaces needing to use Mock data through a proxy server, and importing the acquired content data to replace intercepted return data;

the UI automation use case uses the content data to check data and display the UI.

In a second aspect, an embodiment of the present invention provides a system for sharing and using cross-service Mock data, where the system includes:

the calling module is used for acquiring the types of the rules and the returned data in a manner of calling Mocker services by the UI automation engineering service;

The analysis module is used for analyzing the type of the acquired rule and the returned data to acquire content data of the rule of the Mock type;

And the use module is used for calling the content data and using the content data when writing and executing the UI automation use case procedure.

Further, in the cross-service Mock data sharing usage system, the calling module is specifically configured to:

The type of rule and return data is obtained from a database served by Mocker.

Further, in the cross-service Mock data sharing usage system, the usage module is specifically configured to:

In a third aspect, an embodiment of the present invention provides a computer device, including a memory and a processor, where the memory stores a computer program, and the processor implements the method for using cross-service Mock data according to any one of the above aspects when executing the computer program.

In a fourth aspect, embodiments of the present invention provide a storage medium containing computer-executable instructions for execution by a computer processor to implement the method of shared use of cross-service Mock data as described in any of the above aspects.

The cross-service Mock data sharing and using method, system, equipment and storage medium provided by the embodiment of the invention can improve the execution efficiency of UI automation engineering, reduce the maintenance and management cost of redundant files, reduce the steps of automatic case writing, change Mock data into visualization, and make the operation and use simpler, more convenient and faster.

Drawings

In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the description below are only some embodiments of the invention, and that other drawings can be obtained from these drawings without inventive faculty for a person skilled in the art.

Fig. 1 is a flow chart of a method for sharing and using cross-service Mock data according to a first embodiment of the present invention;

fig. 2 is a flow chart of a method for sharing and using cross-service Mock data according to a second embodiment of the present invention;

Fig. 3 is a flow chart of a method for sharing and using cross-service Mock data according to a third embodiment of the present invention;

fig. 4 is a schematic diagram of a functional module of a cross-service Mock data sharing system according to a fourth embodiment of the present invention.

Fig. 5 is a schematic structural diagram of a computer device according to a fifth embodiment of the present invention.

Detailed Description

In order to make the objects, features and advantages of the present invention more obvious and understandable, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is apparent that the embodiments described below are only some embodiments of the present invention, not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

In the description of the present invention, it will be understood that when one component is referred to as being "connected" to another component, it can be directly connected to the other component or intervening components may also be present. When an element is referred to as being "disposed on" another element, it can be directly on the other element or intervening elements may also be present.

Furthermore, the terms "long," "short," "inner," "outer," and the like, as used herein, refer to an orientation or positional relationship based on that shown in the drawings, for convenience of description of the present invention, and are not intended to indicate or imply that the apparatus or elements referred to must have this particular orientation, operate in a particular orientation configuration, and thus should not be construed as limiting the invention.

The technical scheme of the invention is further described below by the specific embodiments with reference to the accompanying drawings.

Example 1

In view of the defects of the prior art, the inventor actively researches and innovates based on the rich practical experience and professional knowledge in the industry for many years and the application of the academic so as to create a feasible cross-service Mock data sharing and using technology, so that the method has higher practicability. After continuous research, design and repeated test and improvement, the invention with practical value is finally created.

Referring to fig. 1, fig. 1 is a flow chart of a method for sharing and using cross-service Mock data, which is disclosed in an embodiment of the present invention, and the method is applicable to a scenario of sharing and implementing remote Mock data. As shown in fig. 1, the method for sharing and using cross-service Mock data may include the following steps:

S101, acquiring types of rules and returned data in a mode of calling Mocker services through a UI automation engineering service.

Wherein the return data is Response.

The UI automation engineering calls Mocker the service by a predetermined parameter (rule ID ).

In addition, invoking Mocker a service refers specifically to invoking an interface of Mocker a service to be able to access and query the database of Mocker services. The types of rules and return data are stored in the Mocker service database.

S102, analyzing the acquired rule type and the returned data to acquire content data of the rule type Mock.

It should be noted that, in this step, specifically, a rule of type=mock is identified, and then content data of which the current rule is of the Mock Type is obtained.

S103, calling the content data and using the content data when writing and executing the UI automation use case procedure.

In this step, in the process of writing and executing the UI automation use case, if Mock data is needed, the obtained content data of type=mock is directly called for use.

The embodiment supports the simultaneous use of single Mock data and a plurality of Mock data in one UI automation use case design, and also supports the obtaining of the Mock rule content in the Get and Post request modes.

The cross-service Mock data sharing and using method provided by the embodiment of the invention can improve the execution efficiency of UI automation engineering, reduce the maintenance and management cost of redundant files, reduce the steps of automatic case writing, change Mock data into visualization, and make the operation and use simpler, more convenient and faster.

Example two

As shown in fig. 2, the shared usage method of cross-service Mock data provided by the second embodiment of the present invention further optimizes the type of the rule and the returned data acquired by the UI automation engineering service call Mocker service in step S101 "based on the technical solution provided by the first embodiment. The explanation of the same or corresponding terms as those of the above embodiments is not repeated here. Namely:

The type of rule and return data is obtained from a database served by Mocker.

Based on the above optimization, as shown in fig. 2, the method for sharing and using cross-service Mock data provided in this embodiment may include the following steps:

s201, initiating a Http request to call showRule () interface of Mocker service through the UI automation engineering service to inquire a database of Mocker service.

Wherein Mocker service is Appmocker, and the calling mode is UI automation engineering afferent ruleID.

S202, acquiring the types of the rules and the returned data from a database served by Mocker.

S203, analyzing the acquired rule type and the returned data to acquire content data of the rule type Mock.

S204, calling the content data and using the content data when writing and executing the UI automation use case procedure.

Example III

As shown in fig. 3, the method for sharing and using cross-service Mock data provided by the third embodiment of the present invention is based on the technical solution provided by the first embodiment, and further optimizes "call and use content data in writing and executing UI automation use case procedure" in step S103. The explanation of the same or corresponding terms as those of the above embodiments is not repeated here. Namely:

in the process of writing and executing the UI automation use case, monitoring and intercepting an interface request of an interface needing to use Mock data through a proxy server, and importing the acquired content data to replace intercepted return data.

Based on the above optimization, as shown in fig. 3, the method for sharing and using cross-service Mock data provided in this embodiment may include the following steps:

S301, acquiring types of rules and returned data in a mode of calling Mocker services through a UI automation engineering service.

S302, analyzing the acquired rule type and returned data to acquire content data of the rule type Mock.

S303, in the process of compiling and executing the UI automation use case, monitoring and intercepting an interface request of an interface which needs to use Mock data through a proxy server, and transmitting the acquired content data to replace intercepted return data.

Wherein the proxy server specifically refers to AppProxy.

S304, the UI automation use case uses the content data to check data and display the UI.

The cross-service Mock data sharing and using method provided by the embodiment of the invention can reduce maintenance of engineering local files, data of a multi-service public database, interface the Mock data, update and view the Mock data in real time, facilitate debugging of problems, improve efficiency of executing automatic use cases and reduce use of engineering resources.

Example IV

Referring to fig. 4, fig. 4 is a cross-service Mock data sharing and using system according to a fourth embodiment of the present invention, where the system is adapted to execute the cross-service Mock data sharing and using method according to the embodiment of the present invention. The system specifically comprises the following modules:

A calling module 401, configured to obtain the type of the rule and the return data by using a UI automation engineering service to call Mocker the service;

the parsing module 402 is configured to parse the obtained type of the rule and the returned data, and obtain content data with the rule being a Mock type;

a use module 403, configured to call the content data and use the content data when writing and executing the UI automation case procedure.

Preferably, the calling module 401 is specifically configured to:

The type of rule and return data is obtained from a database served by Mocker.

Preferably, the usage module 403 is specifically configured to:

The cross-service Mock data sharing and using system provided by the embodiment of the invention can improve the execution efficiency of UI automation engineering, reduce the maintenance and management cost of redundant files, reduce the steps of automatic case writing, change Mock data into visualization, and make the operation and use simpler, more convenient and faster.

The product can execute the method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Example five

Fig. 5 is a schematic structural diagram of a computer device according to a fifth embodiment of the present invention. Fig. 5 illustrates a block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention. The computer device 12 shown in fig. 5 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.

As shown in FIG. 5, the computer device 12 is in the form of a general purpose computing device. Components of computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16.

Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

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

The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. The computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (not shown in FIG. 5, commonly referred to as a "hard disk drive"). Although not shown in fig. 5, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of embodiments of the invention.

A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the embodiments described herein.

The computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the computer device 12, and/or any devices (e.g., network card, modem, etc.) that enable the computer device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Moreover, computer device 12 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through network adapter 20. As shown, network adapter 20 communicates with other modules of computer device 12 via bus 18. It should be appreciated that although not shown in fig. 5, other hardware and/or software modules may be used in connection with computer device 12, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing the shared use method of cross-service Mock data provided by the embodiment of the present invention.

That is, the processing unit realizes when executing the program: acquiring the types of the rules and returned data in a manner of calling Mocker services by the UI automation engineering service; analyzing the type of the acquired rule and the returned data to acquire content data of which the rule is a Mock type; the content data is called and used in the process of writing and executing the UI automation use case.

Example six

The sixth embodiment of the present application provides a computer-readable storage medium, on which computer-executable instructions are stored, which when executed by a processor implement the method for sharing and using cross-service Mock data provided by all the embodiments of the present application:

That is, the processing unit realizes when executing the program: modifying plug-ins of the Clang compiler; acquiring the types of the rules and returned data in a manner of calling Mocker services by the UI automation engineering service; analyzing the type of the acquired rule and the returned data to acquire content data of which the rule is a Mock type; the content data is called and used in the process of writing and executing the UI automation use case.

Any combination of one or more computer readable media may be employed. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: 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 this document, 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.

The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations of the present invention 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 kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

The description of the foregoing embodiments has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular embodiment are generally not limited to the particular embodiment, but, where applicable, may be interchanged and used with the selected embodiment even if not specifically shown or described. The same elements or features may also be varied in many ways. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.

Example embodiments are provided so that this disclosure will be thorough, and will fully convey the scope to those skilled in the art. Numerous details are set forth, such as examples of specific parts, devices, and methods, in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to one skilled in the art that the exemplary embodiments may be embodied in many different forms without the use of specific details, and neither should be construed to limit the scope of the disclosure. In certain example embodiments, well-known processes, well-known device structures, and well-known techniques are not described in detail.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises" and "comprising" are inclusive and, therefore, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed and illustrated, unless specifically indicated. It should also be appreciated that additional or alternative steps may be employed.

When an element or layer is referred to as being "on," "engaged with," "connected to" or "coupled to" another element or layer, it can be directly on, engaged with, connected to or coupled to the other element or layer, or intervening elements or layers may also be present. In contrast, when an element or layer is referred to as being "directly on" … …, "" directly engaged with "… …," "directly connected to" or "directly coupled to" another element or layer, there may be no intervening elements or layers present. Other words used to describe the relationship of elements should be interpreted in a similar fashion (e.g., "between … …" and "directly between … …", "adjacent" and "directly adjacent", etc.). The term "and/or" as used herein includes any and all combinations of one or more of the associated listed items. Although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region or section from another element, component, region or section. Unless clearly indicated by the context, terms such as the terms "first," "second," and other numerical values are used herein to not imply a sequence or order. Accordingly, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the example embodiments.

Spatially relative terms, such as "inner," "outer," "below," "beneath," "lower," "above," "upper," and the like, may be used herein for ease of description to describe one element or feature's relationship to another element or feature as illustrated in the figures. Spatially relative terms may be intended to encompass different orientations of the device in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as "below" or "beneath" other elements or features would then be oriented "above" the other elements or features. Thus, the example term "below … …" may include both upward and downward orientations. The device may be otherwise oriented (rotated 90 degrees or otherwise) and interpreted in the relative description of the space herein.

Claims

1. A method for sharing and using cross-service Mock data, the method comprising:

calling the content data and using the content data in the process of writing and executing the UI automation use case;

the step of acquiring the types of the rules and the returned data by the way of calling Mocker the service through the UI automation engineering service comprises the following steps:

Acquiring the types of rules and returned data from a database served by Mocker;

the step of calling the content data and using the content data in the process of writing and executing the UI automation use case comprises the following steps:

2. A shared use system for cross-service Mock data, the system comprising:

The use module is used for calling the content data and using the content data when writing and executing the UI automation use case process;

The calling module is specifically configured to:

The use module is specifically used for:

3. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor when executing the computer program implements the cross-service Mock data sharing method of claim 1.

4. A storage medium containing computer-executable instructions for execution by a computer processor to implement the cross-service Mock data sharing usage method of claim 1.