CN114327416A - Interface synchronization method and device applied to development branch and electronic equipment - Google Patents
Interface synchronization method and device applied to development branch and electronic equipment Download PDFInfo
- Publication number
- CN114327416A CN114327416A CN202210261410.6A CN202210261410A CN114327416A CN 114327416 A CN114327416 A CN 114327416A CN 202210261410 A CN202210261410 A CN 202210261410A CN 114327416 A CN114327416 A CN 114327416A
- Authority
- CN
- China
- Prior art keywords
- interface
- data exchange
- development
- file
- interface platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The invention provides an interface synchronization method, an interface synchronization device and electronic equipment applied to development branches, wherein the method comprises the following steps: after receiving an instruction of a back-end developer for editing the annotation, the back-end system generates a data exchange file according to the edited annotation and the acquired file format specified by the interface platform; uploading the data exchange file to an interface platform; the front-end system acquires the data exchange files corresponding to development branches of the back-end developer from the interface platform, wherein each development branch corresponds to one data exchange file; and the front-end system extracts interface information from the data exchange file according to the file format specified by the interface platform and sends the interface information to a development branch page associated with a front-end developer. The invention realizes the automatic synchronization of the interface information in the same development branch, avoids the mutual interference of the interface information of different development branches and improves the software development efficiency.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to an interface synchronization method and device applied to development branches and electronic equipment.
Background
Currently, the development of software basically adopts a mode of separating a front end from a back end, and the basic flow is roughly as follows: the back-end developer defines an interface to provide data services, and the front-end developer calls an interface document through a development page to acquire interface information and render the page.
Currently, there are also modes of developing branches, namely: a project is divided into a plurality of development branches, interface documents are copied into a plurality of shares equal to the number of the development branches, and the plurality of interface documents are distributed to the development branches in a one-to-one correspondence manner.
In the development branch mode, after the interface information is modified by the back-end developer, the interface document corresponding to the modified interface information needs to be manually sent to the front-end developer, and the interference of the interface information between different development branches caused by sending errors needs to be manually avoided, so that the development efficiency is low.
Disclosure of Invention
The embodiment of the invention provides an interface synchronization method applied to development branches, and aims to solve the problems that in a development branch mode, a back-end developer needs to manually send an interface document corresponding to interface information after the interface information is changed to a front-end developer, and the interference of the interface information among different development branches caused by sending errors needs to be manually avoided, so that the development efficiency is low.
In order to solve the technical problem, the invention is realized as follows:
in a first aspect, an embodiment of the present invention provides an interface synchronization method applied to a development branch, including:
after receiving an instruction of a back-end developer for editing the annotation, the back-end system generates a data exchange file according to the edited annotation and the acquired file format specified by the interface platform; uploading the data exchange file to an interface platform;
the front-end system acquires the data exchange files corresponding to development branches of the back-end developer from the interface platform, wherein each development branch corresponds to one data exchange file;
and the front-end system extracts interface information from the data exchange file according to the file format specified by the interface platform and sends the interface information to a development branch page associated with a front-end developer.
Alternatively,
and the back-end system uploads the data exchange file to an interface platform in a continuous integrated CI mode.
Alternatively,
the back-end system uploads the data exchange file to an interface platform in a continuous integrated CI mode, and the method comprises the following steps:
running development software to recognize and read the data exchange file and judge whether the file format of the data exchange file is the same as the file format type specified by the interface platform;
if so, uploading the data exchange file to the interface platform;
if not, converting the file format of the data exchange file to ensure that the file format type of the data exchange file is the same as the file format type specified by the interface platform, and uploading the data exchange file after the format conversion to the interface platform.
Alternatively,
the development software is at least secondary development software of the following software: apifox, Eolink, Yapi and Swagger.
Alternatively,
the file format specified by the interface platform is a json format.
Alternatively,
the interface platform is an Openapi interface platform, and the file format of the interface platform is Openapi 2.0; or the file format of the interface platform is Openapi 3.0.
In a second aspect, an embodiment of the present invention provides an interface synchronization apparatus applied to a development branch, including:
a front-end system and a back-end system;
the back-end system is used for generating a data exchange file according to the edited annotation and the acquired file format specified by the interface platform after receiving an instruction of a back-end developer for editing the annotation; uploading the data exchange file to an interface platform;
the front-end system is used for acquiring the data exchange files corresponding to development branches of the back-end developer from the interface platform, wherein each development branch corresponds to one data exchange file;
and the front-end system is used for extracting interface information from the data exchange file according to the file format specified by the interface platform and sending the interface information to a development branch page associated with a front-end developer.
Alternatively,
and the back-end system is used for uploading the data exchange file to an interface platform in a continuous integrated CI mode.
In a third aspect, an embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor, where the program or instructions, when executed by the processor, implement the steps in the interface synchronization method according to any one of the first aspect.
In a fourth aspect, the embodiment of the present invention provides a readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps in the interface synchronization method according to any one of the first aspect.
In the embodiment of the invention, the data exchange file is uploaded to the interface platform through the back-end system, and then the data exchange file corresponding to the development branch of the back-end developer is acquired from the interface platform through the front-end system, so that the automatic synchronization of the interface information in the same development branch is realized, the mutual interference of the interface information of different development branches is avoided, and the software development efficiency is improved.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flowchart illustrating an interface synchronization method applied to a development branch according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a development branch in an interface synchronization method applied to the development branch according to an embodiment of the present invention;
FIG. 3 is a second flowchart of an interface synchronization method applied to a development branch according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a software development flow using an interface synchronization method applied to development branches according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an internal structure of an interface synchronization apparatus applied to a development branch according to an embodiment of the present invention;
fig. 6 is a schematic diagram of an internal structure of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An embodiment of the present invention provides an interface synchronization method applied to a development branch, and referring to fig. 1, fig. 1 is a schematic flow diagram of an interface synchronization method applied to a development branch in an embodiment of the present invention, where the method includes:
step 11: after receiving an instruction of a back-end developer for editing the annotation, the back-end system generates a data exchange file according to the edited annotation and the acquired file format specified by the interface platform; uploading the data exchange file to an interface platform;
step 12: the front-end system acquires data exchange files corresponding to development branches of a rear-end developer from the interface platform, wherein each development branch corresponds to one data exchange file;
step 13: and the front-end system extracts interface information from the data exchange file according to the file format specified by the interface platform and sends the interface information to a development branch page associated with a front-end developer.
The branch development comprises the following steps: 1. backbone development, in this mode, developers almost always sign in code to the backbone, with few branches used. 2. Branches are created per release, in which mode a branch is created just before a release of a version, on which branch the testing and verification of the release version is all done, while the latest development work is still done on the backbone. 3. Branches are created by functional property, which is a mode to make it easier for development teams to work in parallel at the "property" level and to maintain the publishable state of the backbone. Each user story or characteristic is developed and completed on different branches, and a story is merged onto the backbone only after being verified by a tester to be problem-free, so as to ensure that the backbone is always distributable. The motivation for this model is the desire to maintain the publishable state of the backbone at all times. 4. Creating branches by team, this mode attempts to address the following conditions: in a large team, there are many developers working on multiple work units simultaneously, and also maintaining the backbone always in a publishable state.
In some embodiments of the present invention, optionally, referring to fig. 2, fig. 2 is a schematic diagram of a development branch in an interface synchronization method applied to the development branch in an embodiment of the present invention, and based on a plurality of modification requirements, modification of interface information in each corresponding development branch and selection of the development branch can implement at least one of the following functions: interface import, interface export, mock of interface data, interface debugging, and editing and viewing of interfaces. For example, the developer selects the development branch to implement interface debugging, and at this time, the modification requirement corresponding to the interface information that is modified in the development branch is a requirement for perfecting the error reporting part in the previous software development version.
In some embodiments of the present invention, optionally, the developer may select the development branch with a view to implementing interface import, and at this time, the modification requirement corresponding to the interface information that is modified in the development branch is a requirement for solving a problem to be solved urgently in software development.
In some embodiments of the present invention, optionally, the developer's choice for developing the branch may be to implement mock of the interface data.
The mock test is a test method which is created by using a virtual object for some objects which are not easy to construct or obtain in the test process. This virtual object is the mock object. mock objects are substitutes for real objects during commissioning, real objects have indeterminate behavior, produce unpredictable effects, (e.g., stock quotes, weather forecasts) real objects are difficult to create, certain behaviors of real objects are difficult to trigger, real objects do not actually exist (cross other development teams or new hardware), and so on. An interface is used to describe this object. This interface is implemented in the product code, in the test code, and the object is only referenced through the interface in the code under test, so it does not know whether the referenced object is a real object or a mock object.
In some embodiments of the present invention, optionally, the front-end system detects an instruction of the back-end developer to complete editing of the annotation at a preset time interval, and if the instruction of the back-end developer to complete editing of the annotation exists, step 11 is executed.
In some embodiments of the present invention, optionally, the front-end system detects an instruction of the back-end developer to complete editing of the annotation at a preset time point, and if the instruction of the back-end developer to complete editing of the annotation exists, performs step 11.
In some embodiments of the present invention, optionally, the front-end system detects an instruction of the back-end developer to complete editing of the annotation after the front-end developer performs a certain preset operation or a few preset operations, and if there is an instruction of the back-end developer to complete editing of the annotation, step 11 is executed.
In some embodiments of the present invention, optionally, the front-end system detects an instruction of the back-end developer to complete editing of the annotation after the back-end developer performs a certain preset operation or a few preset operations, and if the instruction of the back-end developer to complete editing of the annotation exists, performs step 11.
In the embodiment of the invention, the data exchange file is uploaded to the interface platform through the back-end system, and then the data exchange file corresponding to the development branch of the back-end developer is acquired from the interface platform through the front-end system, so that the automatic synchronization of the interface information in the same development branch is realized, the mutual interference of the interface information of different development branches is avoided, and the software development efficiency is improved.
In some embodiments of the present invention, the first and second electrodes are, optionally,
and the back-end system uploads the data exchange file to the interface platform in a continuous integrated CI mode.
CI (Continuous Integration), through which developers can frequently integrate code into the main branch of a common code repository. Developers can submit works to the repository multiple times at any time, rather than developing each functional module independently and submitting one at a time at the end of the development cycle.
The CI setting is beneficial to simplifying integration in the software development process into a simple and easily repeated daily development task, so that the integration is automated, manual operation is reduced, the overall construction cost is reduced, and defects are found early in the development period.
In some embodiments of the present invention, the first and second electrodes are, optionally,
referring to fig. 3, fig. 3 is a second schematic flow chart of the interface synchronization method applied to development branches according to the embodiment of the present invention, in which a backend system uploads a data exchange file to an interface platform in a persistent integration CI manner, including:
step 31: running development software to read the data exchange file and judge whether the file format of the data exchange file is the same as the file format type specified by the interface platform;
step 32: if so, uploading the data exchange file to an interface platform;
step 33: if not, converting the file format of the data exchange file to ensure that the file format type of the data exchange file is the same as the file format type specified by the interface platform, and uploading the data exchange file after the format conversion to the interface platform.
The above arrangement avoids the problem that the data exchange file is incompatible with the interface platform, and by judging whether the data exchange file is the same as the file format type specified by the interface platform, unnecessary operation of converting the file format of the data exchange file when the data exchange file is the same is avoided, the operation efficiency is improved, and the time cost of development is reduced.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the file format specified by the interface platform is the json format.
JSON (JavaScript Object Notation) is a lightweight data exchange format. It stores and represents data in a text format that is completely independent of the programming language, based on a subset of ECMAScript (js specification set by the european computer association). The compact and clear hierarchy makes JSON an ideal data exchange language. The network transmission method is easy to read and write by people, is easy to analyze and generate by machines, and effectively improves the network transmission efficiency.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the development software is secondary development software of at least one of the following software: apifox, Eolink, Yapi and Swagger.
Apifox solves the problem of data synchronization among a plurality of systems through a set of systems and a copy of data. As long as the interface document is defined, the interface debugging, the data Mock and the interface testing can be directly used without being defined again; the interface document and the interface development and debugging use the same tool, and the interface can be ensured to be completely consistent with the definition of the interface document after the interface debugging is finished.
Eolink supports main stream protocols such as HTTP (S), Websocket, TCP and UDP, API documents are automatically generated through code annotation, or codes of all common development languages and frameworks are generated reversely from the API documents, and the API design and development time is saved. The powerful version of the API and change management lets you not pass through any changes to the API.
YAPI is a visual interface management tool developed by a local network mobile architecture group (YMFE for short, a group of large front-end teams with imagination, creativity and influence jointly formed by FE, iOS and Android engineers), and is a locally-deployable interface management platform for communicating front and back ends and QA. YAPI is intended to provide more elegant interface management services for developers, products and testers, and can help developers easily create, publish and maintain APIs of different projects and different platforms. With YAPI, we can conveniently test, manage and maintain API interfaces of multiple items, unlike Swagger which goes on and off with application (and most of online environment needs to be shut down), YAPI is an independent service platform.
Swagger is a canonical and complete framework for generating, describing, invoking and visualizing RESTful-style Web services. The goal of Swagger is to define a standard and language-independent interface to REST APIs that allows people and computers to have the ability to discover and understand services without having to access source code, documentation, or network traffic monitoring. When properly defined by Swagger, the user can understand the remote service and interact with the remote service using minimal implementation logic. Swagger eliminates guesses that may be had when calling a service, similar to the interface implemented for the underlying programming.
Swagger supports API to automatically generate synchronized online documents: after the Swagger is used, the document can be directly generated through the code, the interface document does not need to be written manually, the method is very convenient for programmers, and the time for writing the document can be saved to learn a new technology.
Swagger provides the Web page online test API: the light documentation is not enough and the documentation generated by Swagger also supports online testing. And parameters and formats are set, and the interface can be tested on line by directly inputting values corresponding to the parameters on the interface.
In some embodiments of the present invention, the first and second electrodes are, optionally,
the interface platform is an Openapi interface platform, and the network protocol of the interface platform is an Openapi 2.0 protocol.
OpenAPI, the full name of API is Application Programming Interface (Application Programming Interface), which is not a new concept and already existed in the early days of the advent of computer operating systems. In the internet era, services of websites are packaged into a series of computer-recognizable data interfaces which are opened for third-party developers to use, the behavior is called as API of open websites, and correspondingly, the opened API is called as OpenAPI.
The Openapi 2.0 protocol. The predecessor to the OpenAPI protocol is the swagger protocol. Swagger is a suite of tools that facilitate front-end separation, interface management and testing. "MUST", "MUST NOT", "REQUIRED", "SHAL", "SHALL NOT", "SHAULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" as used in the OpenAPI 2.0 protocol all follow the RFC 2119 definitions.
In some embodiments of the present invention, optionally, referring to fig. 4, fig. 4 is a schematic diagram of a software development flow of an interface synchronization method applied to a development branch according to an embodiment of the present invention, where:
the technical level is as follows:
generating swagger json files by annotation using swagger
Need to define the generate command and call in the CI
CI development submission and branch merging CI streams
Two commands are included: json and front-end pull interface command are generated by the back end through annotation
Developing a flow:
1. the back end writes comments in the service;
2. triggering development submission CI when commit is submitted;
3. CI executes the defined command to generate swagger.
4. CI calls OpenAPI to correspondingly upload swagger json files to generate interface documents;
5. the front end executes the command and pulls the interface information through OpenAPI and automatically generates an interface request code;
when the branches are merged, the CI pushes a main branch swagger json through the OpenAPI and archives an interface document of the current branch;
when the interface needs to be changed, the back end can synchronously change the comments during the development of the service, the interface document can be automatically updated after the code is submitted, and the front end can pull the generated code again.
An embodiment of the present invention provides an interface synchronization apparatus applied to a development branch, and referring to fig. 5, fig. 5 is a schematic diagram of an internal structure of an interface synchronization apparatus 50 applied to a development branch according to an embodiment of the present invention, where the interface synchronization apparatus 50 includes:
a front-end system 52 and a back-end system 51;
the back-end system 51 is configured to generate a data exchange file according to the edited annotation and the acquired file format specified by the interface platform after receiving the instruction that the back-end developer finishes editing the annotation; uploading the data exchange file to an interface platform;
a front-end system 52, configured to obtain data exchange files corresponding to development branches of a back-end developer from the interface platform, where each development branch corresponds to one data exchange file;
and the front-end system 52 is used for extracting the interface information from the data exchange file according to the file format specified by the interface platform and sending the interface information to a development branch page associated with a front-end developer.
In some embodiments of the present invention, the first and second electrodes are, optionally,
and the back-end system 51 is used for uploading the data exchange file to the interface platform in a continuous integrated CI mode.
In some embodiments of the present invention, the first and second electrodes are, optionally,
a backend system 51 for uploading the data exchange files to an interface platform in a persistent integrated CI manner,
the back-end system 51 is further configured to run development software to read the data exchange file, and determine whether the file format of the data exchange file is the same as the file format type specified by the interface platform; if so, uploading the data exchange file to the interface platform; if not, converting the file format of the data exchange file to ensure that the file format type of the data exchange file is the same as the file format type specified by the interface platform, and uploading the data exchange file after the format conversion to the interface platform.
The interface synchronization apparatus 50 applied to development branching provided in the embodiment of the present application can implement each process implemented by the method embodiments of fig. 1 to fig. 4, and achieve the same technical effect, and is not described herein again to avoid repetition.
Referring to fig. 6, fig. 6 is a schematic diagram illustrating an internal structure of an electronic device 60 according to an embodiment of the present invention, and the electronic device 60 includes a processor 61, a memory 62, and a program or an instruction stored in the memory 62 and executable on the processor 61, where the program or the instruction, when executed by the processor, implements any step of the method for interface synchronization applied to a development branch according to an embodiment of the present invention.
The embodiment of the present invention provides a readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of any one of the above embodiments of the interface synchronization method applied to development of a branch, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.
The readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (10)
1. An interface synchronization method applied to development branching is characterized in that: the method comprises the following steps:
after receiving an instruction of a back-end developer for editing the annotation, the back-end system generates a data exchange file according to the edited annotation and the acquired file format specified by the interface platform; uploading the data exchange file to an interface platform;
the front-end system acquires the data exchange files corresponding to development branches of the back-end developer from the interface platform, wherein each development branch corresponds to one data exchange file;
and the front-end system extracts interface information from the data exchange file according to the file format specified by the interface platform and sends the interface information to a development branch page associated with a front-end developer.
2. The interface synchronization method according to claim 1, wherein:
and the back-end system uploads the data exchange file to an interface platform in a continuous integrated CI mode.
3. The interface synchronization method according to claim 2, wherein:
the back-end system uploads the data exchange file to an interface platform in a continuous integrated CI mode, and the method comprises the following steps:
running development software to recognize and read the data exchange file and judge whether the file format of the data exchange file is the same as the file format type specified by the interface platform;
if so, uploading the data exchange file to the interface platform;
if not, converting the file format of the data exchange file to ensure that the file format type of the data exchange file is the same as the file format type specified by the interface platform, and uploading the data exchange file after the format conversion to the interface platform.
4. The interface synchronization method according to claim 3, wherein: the development software is at least secondary development software of the following software: apifox, Eolink, Yapi and Swagger.
5. The interface synchronization method according to claim 1, wherein:
the file format specified by the interface platform is a json format.
6. The interface synchronization method according to claim 1, wherein:
the interface platform is an Openapi interface platform, and the file format of the interface platform is Openapi 2.0; or the file format of the interface platform is Openapi 3.0.
7. An interface synchronization device applied to development branching is characterized in that: the method comprises the following steps:
a front-end system and a back-end system;
the back-end system is used for generating a data exchange file according to the edited annotation and the acquired file format specified by the interface platform after receiving an instruction of a back-end developer for editing the annotation; uploading the data exchange file to an interface platform;
the front-end system is used for acquiring the data exchange files corresponding to development branches of the back-end developer from the interface platform, wherein each development branch corresponds to one data exchange file;
and the front-end system is used for extracting interface information from the data exchange file according to the file format specified by the interface platform and sending the interface information to a development branch page associated with a front-end developer.
8. The interface synchronization apparatus of claim 7, wherein:
and the back-end system is used for uploading the data exchange file to an interface platform in a continuous integrated CI mode.
9. An electronic device, characterized in that: comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, which program or instructions, when executed by the processor, implement the steps in the interface synchronization method according to any of claims 1 to 6.
10. A readable storage medium, characterized by: the readable storage medium stores thereon a program or instructions which, when executed by a processor, implement the steps in the interface synchronization method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210261410.6A CN114327416A (en) | 2022-03-17 | 2022-03-17 | Interface synchronization method and device applied to development branch and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210261410.6A CN114327416A (en) | 2022-03-17 | 2022-03-17 | Interface synchronization method and device applied to development branch and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114327416A true CN114327416A (en) | 2022-04-12 |
Family
ID=81033238
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210261410.6A Pending CN114327416A (en) | 2022-03-17 | 2022-03-17 | Interface synchronization method and device applied to development branch and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114327416A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115809089A (en) * | 2023-01-12 | 2023-03-17 | 深圳市银云信息技术有限公司 | Method for developing based on document and test driver |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030200348A1 (en) * | 2002-04-17 | 2003-10-23 | Marshall Lee Humphries | Multi-platform software interface and documentation generator |
| CN111930635A (en) * | 2020-09-17 | 2020-11-13 | 深圳微品致远信息科技有限公司 | Swagger-based rapid automatic testing method and system |
| CN113630468A (en) * | 2021-08-16 | 2021-11-09 | 上海观安信息技术股份有限公司 | Dynamic proxy method |
| CN113849404A (en) * | 2021-09-23 | 2021-12-28 | 北京房江湖科技有限公司 | Management method, device and storage medium for interface test related information |
| CN114003293A (en) * | 2021-12-30 | 2022-02-01 | 云账户技术(天津)有限公司 | Interface management method, device, electronic equipment and readable storage medium |
| CN114168190A (en) * | 2020-09-11 | 2022-03-11 | 腾讯科技（深圳）有限公司 | Interface document generation method and device, computer equipment and storage medium |
-
2022
- 2022-03-17 CN CN202210261410.6A patent/CN114327416A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030200348A1 (en) * | 2002-04-17 | 2003-10-23 | Marshall Lee Humphries | Multi-platform software interface and documentation generator |
| CN114168190A (en) * | 2020-09-11 | 2022-03-11 | 腾讯科技（深圳）有限公司 | Interface document generation method and device, computer equipment and storage medium |
| CN111930635A (en) * | 2020-09-17 | 2020-11-13 | 深圳微品致远信息科技有限公司 | Swagger-based rapid automatic testing method and system |
| CN113630468A (en) * | 2021-08-16 | 2021-11-09 | 上海观安信息技术股份有限公司 | Dynamic proxy method |
| CN113849404A (en) * | 2021-09-23 | 2021-12-28 | 北京房江湖科技有限公司 | Management method, device and storage medium for interface test related information |
| CN114003293A (en) * | 2021-12-30 | 2022-02-01 | 云账户技术(天津)有限公司 | Interface management method, device, electronic equipment and readable storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115809089A (en) * | 2023-01-12 | 2023-03-17 | 深圳市银云信息技术有限公司 | Method for developing based on document and test driver |
| CN115809089B (en) * | 2023-01-12 | 2023-08-15 | 深圳市银云信息技术有限公司 | Method for developing based on document and test driver |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109117131B (en) | Code generation method and device, storage medium and electronic terminal | |
| KR102443654B1 (en) | Automatically create machine learning models for software tools that operate on source code | |
| WO2021088724A1 (en) | Testing method and apparatus | |
| Wells | Performance analysis using CPN tools | |
| US20080209405A1 (en) | Distributed debugging for a visual programming language | |
| CN102479152A (en) | Method and device for obtaining tool automatic test results on basis of Android platform | |
| CN107608873B (en) | Software testing method and system and testing platform | |
| CN111158656A (en) | Method and device for generating test codes based on fruit tree method | |
| CN110297637A (en) | The applicable resource file thermogravimetric of full platform client software carries tool and method of development | |
| CN107797805B (en) | Code packaging method and device and computer readable storage medium | |
| CN110765010B (en) | Method and device for online debugging visual development based on Flink | |
| CN113505082A (en) | Application program testing method and device | |
| CN114327416A (en) | Interface synchronization method and device applied to development branch and electronic equipment | |
| CN113312035B (en) | Hyperledger Fabric-oriented intelligent contract development plug-in implementation method | |
| CN104317580A (en) | Integrated development environment for virtual test application (APP) | |
| Craggs et al. | Agedis case studies: Model-based testing in industry | |
| CN111143228B (en) | Test code generation method and device based on decision table method | |
| CN111078529B (en) | Client writing module testing method and device and electronic equipment | |
| CN112988267A (en) | Loading method and device, storage medium and electronic equipment | |
| Schmid et al. | A survey of simulation tools for requirements engineering | |
| CN105302731A (en) | Testing system and method for upgrading website configuration | |
| CN117215661A (en) | Event processing method, device and storage medium | |
| CN113971024B (en) | Interface management method, device, electronic equipment and readable storage medium | |
| JPH08314760A (en) | Program development supporting device | |
| Englisch et al. | Automated generation of tests for education in software engineering |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220412 |