CN107291494B - Method and device for generating application program installation package - Google Patents
Method and device for generating application program installation package Download PDFInfo
- Publication number
- CN107291494B CN107291494B CN201710395584.0A CN201710395584A CN107291494B CN 107291494 B CN107291494 B CN 107291494B CN 201710395584 A CN201710395584 A CN 201710395584A CN 107291494 B CN107291494 B CN 107291494B
- Authority
- CN
- China
- Prior art keywords
- file
- formal
- version
- keyword
- installation package
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method and a device for generating an application program installation package, wherein the method comprises the following steps: after receiving a specified command, identifying and selecting a formal version file to be issued from a formal version file to be issued and an informal version file for testing which are contained in a preset code library; and generating an application program installation package to be released according to the selected formal version file. According to the method and the device for generating the application program installation package, formal files can be automatically identified and selected from the preset code library, and developers do not need to manually select the formal files, so that the situation that the developers use the informal files as the formal files and generate the application program installation package to be released by using the informal files can be avoided. Therefore, the error rate of the generated application program installation package can be reduced, the success rate and the efficiency of application program updating are improved, and the user experience is further improved.
Description
Technical Field
The invention relates to the field of terminals, in particular to a method and a device for generating an application program installation package.
Background
At present, when a developer develops an application, different files are used to implement different functions of the application. Since the development environment and the formal use environment are different from each other, the files are generally classified into an informal version and a formal version.
In order to facilitate research and development and testing in the development stage of the application program, a developer generates an installation package of the application program by using an informal version file when developing the application program. After the application program is developed, a developer needs to check the content to be published for many times, and can publish the installation package of the application program to the market on the basis of ensuring the safety and reliability of the content to be published. In the prior art, when a development version file meets a release requirement, a developer manually replaces an informal version file in an installation package to be released with a formal version file.
However, since there are many functions to be tested or test environments are different, there are cases where a plurality of development version files exist, and therefore, in the process of manually replacing an informal version file in an installation package with a formal version file, there is a problem that a development version file that does not satisfy a release requirement or is incomplete is easily replaced with a formal version file, and application update fails.
Disclosure of Invention
The invention provides a method and a device for generating an application program installation package, which are used for reducing the error rate of the generated application program installation package and further improving the success rate of updating an application program.
In a first aspect, the present invention provides a method for generating an application installation package, where the method includes:
after receiving a specified command, identifying and selecting a formal version file to be issued from a formal version file to be issued and an informal version file for testing which are contained in a preset code library;
and generating an application program installation package to be released according to the selected formal version file.
In a possible implementation manner, the identifying and selecting a formal version file to be published includes:
acquiring file identification information of each file, judging whether the file identification information of each file contains first keywords one by one, and selecting the file containing the first keywords as the formal version file to be released;
the first keyword of the file is used for identifying the file as the formal version file.
In another possible embodiment, the identifying and selecting a formal version file to be published includes:
acquiring file identification information of each file, judging whether the file identification information of each file contains first keywords one by one, when the file identification information of each file does not contain the first keywords, further determining the file containing second keywords in the file identification information as the informal version file, and selecting other files except the informal version file in each file as formal version files;
the first keyword of the file is used for identifying the file as the official file, and the second keyword of the file is used for identifying the file as the informal file.
In another possible embodiment, the file identification information includes at least any one of the following information: file name information, file label information, file path information.
In another possible embodiment, the file is a binary file.
In another possible implementation manner, after the identifying and selecting the formal version file to be published, before the generating the application installation package to be published, the method further includes:
compressing the selected formal version file to generate a formal version file compression package;
the generating of the application program installation package to be released includes:
and generating an application program installation package to be released according to the generated formal version file compression package.
In another possible implementation, the specified command is a predetermined packaging instruction for obtaining the application installation package.
In another possible embodiment, the preset code library is provided on the target server.
In a first aspect, the present invention provides an apparatus for generating an application installation package, the apparatus comprising:
the receiving module is used for receiving a specified command;
the processing module is used for identifying and selecting the formal version files to be issued from the formal version files to be issued and the informal version files for testing contained in the preset code library after the receiving module receives the specified command;
and the generating module is used for generating the application program installation package to be released according to the selected formal version file.
In a possible implementation manner, the processing module is specifically configured to obtain file identification information of each file, determine one by one whether the file identification information of each file includes a first keyword, and select a file including the first keyword as the formal version file to be released;
the first keyword of the file is used for identifying the file as the formal version file.
In another possible implementation manner, the processing module is specifically configured to obtain file identification information of each file, determine whether the file identification information of each file includes a first keyword one by one, when the file identification information of each file does not include the first keyword, further determine a file including a second keyword in the file identification information as the informal version file, and select another file in each file except the informal version file as a formal version file;
the first keyword of the file is used for identifying the file as the official file, and the second keyword of the file is used for identifying the file as the informal file.
In another possible embodiment, the file identification information includes at least any one of the following information: file name information, file label information, file path information.
In another possible embodiment, the file is a binary file.
In another possible implementation manner, the generating module is specifically configured to compress the extracted formal version file, generate the formal version file compression package, and generate the application installation package to be released according to the generated formal version file compression package.
In another possible implementation, the specified command is a predetermined packaging instruction for obtaining the application installation package.
In another possible embodiment, the preset code library is provided on the target server.
According to the method and the device for generating the application program installation package, after the appointed command is received, the formal version file to be issued can be automatically identified and selected from the formal version file to be issued and the informal version file for testing which are contained in the preset code base, and then the application program installation package to be issued can be generated according to the formal version file which is automatically selected. By the method, the error rate in the process of generating the application program installation package can be reduced, the success rate and the efficiency of updating the application program are improved, and the user experience is further improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic flow chart of a method for generating an application installation package according to the present invention;
fig. 2 is a schematic structural diagram of an apparatus for generating an application installation package according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, 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, but 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.
The method for generating the application program installation package is used for reducing the error rate in the process of generating the application program installation package, and further improving the success rate of updating the application program. Of course, the processing method of the file provided by the present invention includes, but is not limited to, the above application scenarios, and as long as the scenario related to replacing the file in the installation package is concerned, the generation method of the application installation package provided by the present invention can be adopted.
The technical solution of the present invention will be described in detail below with specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments.
Fig. 1 is a schematic flow chart of a method for generating an application installation package according to the present invention. The following description will be given taking the example of a terminal device (for short, a terminal device) in which an execution main body is a generation device integrated with an application installation package, and the present embodiment relates to a process in which the terminal device generates an application installation package to be released according to a formal version file to be released, which is identified and selected from a preset code library, according to a specified command. As shown in fig. 1, the method may include:
s101, after receiving a specified command, identifying and selecting a formal version file to be released from formal version files to be released and informal version files for testing contained in a preset code library.
When a developer develops an application, the developer uses different files to implement different functions of the application. Since the development environment is different from the formal use environment, the files of the application program can be divided into an informal version and a formal version for research and development and testing in the development stage of the application program. When a developer develops an application program, the installation package of the application program can be generated by using the informal version file, so that the development and the test of the application program in the development stage are facilitated. After the development or the test of the application program is finished, developers need to manually replace an informal version file in an installation package with a formal version file before issuing the application program, and it is guaranteed that the application program can obtain correct function upgrade and repair after being updated by the installation package containing the formal version file. In addition, the formal version file also contains verification content, so that the application program installation package generated by using the formal version file can be ensured to be safe and reliable. After the application program installation package is released to the market, the application program installation package can be ensured not to be cracked easily.
In this embodiment, the developer may store the formal version file and the informal version file of the application program in the preset code library. Therefore, when a developer needs to generate an installation package of an application program to be released, the terminal device may receive a specified command, and may automatically identify and select a formal version file to be released of the application program from a preset code library according to the specified command. The above-mentioned designated command may be, for example, a preset packaging instruction for acquiring the application installation package. In a specific implementation, the specified command may be manually input to the terminal device by a developer. In this embodiment, the device for sending the packaging instruction is not limited, and therefore, the developer can send the packaging instruction to the terminal device by using various devices.
For example, the developer may store the official version file and the informal version file in different paths in a preset code library. Therefore, the terminal device can automatically identify and select the formal version file to be released of the application program from the preset code library according to the path information of the formal version file. Optionally, the formal version files and the informal version files corresponding to the same function can be stored in different folders under the same function folder, so that unified management is facilitated.
Alternatively, the developer may set different file names for the official version file and the informal version file in a preset code library. Therefore, the terminal device can automatically identify and select the formal version file to be released of the application program from the preset code library according to the file name information of the formal version file.
Alternatively, the developer may set different file tags for the official version files and the informal version files in a preset code base. Therefore, the terminal device can automatically identify and select the formal version file to be released of the application program from the preset code library according to the file label information of the formal version file.
It should be noted that the preset code library may be set on any server that can be accessed by the terminal device, for example: the preset code library can be arranged on a target server and the like. In some embodiments, the preset code library may also be provided on the terminal device.
And S102, generating an application program installation package to be released according to the selected formal version file.
Specifically, after the terminal device identifies and selects the official version file to be released, the selected official version file may be used to replace the informal version file in the installation package, so as to generate the application installation package to be released. The terminal equipment can automatically identify and select the formal version files from the preset code library, and developers do not need to manually select the formal version files, so that the situation that the developers take the informal version files as the formal version files and use the informal version files to generate the application program installation package to be released can be avoided. Therefore, the method of the embodiment can reduce the error rate of the generated application program installation package and improve the success rate and efficiency of the application program update.
Meanwhile, due to the fact that the informal version files lack a verification process, if the installation package containing the informal version files is released to the market by the terminal device, the installation package is easy to decipher by other developers, so that the problems of user information leakage and the like are caused, user experience is low, and economic loss is large. The application program installation package to be released generated in the above way can ensure that the generated installation package does not have informal version files. Therefore, after the application program installation package to be published is published to the market, the terminal equipment can meet the requirements in practical use, improves the user experience and avoids economic loss.
Illustratively, when the file stored in the preset code library is a binary file, for example, a so-formatted binary file, etc. The terminal device may compress the formal version file to generate a formal version file compression package after selecting the formal version file. Then, the terminal device may generate an application installation package to be released according to the generated formal version file compression package. The format of the formal file compression package may be any format that can be read by a terminal device, for example: the formal version file compression package can be a compression package in aar format, and the like. It should be noted that, the process of compressing the formal version file by the terminal device to generate the formal version file compression package may refer to the prior art, and is not described herein again.
For example, when the file stored in the preset code library is a formal file compression package, the terminal device may directly generate an application installation package to be released after selecting the formal file compression package.
According to the file processing method provided by the invention, after the appointed command is received, the formal version file to be issued and the informal version file for testing are automatically identified and selected from the formal version file to be issued and the informal version file to be tested, and then the application program installation package to be issued can be generated according to the selected formal version file. By the method, the error rate of the generated application program installation package can be reduced, the success rate and the efficiency of application program updating are improved, and further the user experience is improved.
Further, on the basis of the foregoing embodiment, this embodiment relates to a process in which the terminal device identifies and selects a formal version file to be published from a formal version file to be published and an informal version file for testing, which are contained in a preset code library, and then the foregoing S101 may include the following two cases:
in the first case: the method comprises the steps that a developer sets a first keyword in file identification information of a formal version file in a preset code base, and the file is identified as the formal version file through the first keyword.
Therefore, after receiving the specified command, the terminal device may obtain the file identification information of each file in the preset code library. Then, the terminal device may determine whether the file identification information of each file includes the first keyword one by one, and select the file including the first keyword as the formal version file to be released.
That is to say, the developer sets a uniform first keyword in the file identification information of all the formal version files, so that the terminal device can automatically and correctly identify and select the formal version files of the application program in the preset code library through the first keyword. The first keyword can be specifically determined according to naming habits of developers. For example: the first keyword may be release.
Taking the file identification information as the file name information as an example, the developer may set a uniform first keyword in the file name information of all formal files. For example, the suffix of the file names of all the formal version files in the preset code library may be set as _ release. In this scenario, the terminal device may obtain file name information of each file in a preset code library. Then, the terminal device may determine whether the file name information of each file includes _ release one by one, and select the file including _ release as the formal version file to be released.
Taking the file identification information as the file tag information as an example, the developer may set a uniform first keyword in the file tag information of all formal files. For example, the file tag suffixes of all formal version files in the preset code library may be set to _ release. In this scenario, the terminal device may obtain file tag information of each file in a preset code library. Then, the terminal device may determine whether the file tag information of each file includes _ release one by one, and select the file including _ release as the formal version file to be released.
Taking the file identification information as the file path information (i.e. the path information of the file stored in the preset code library) as an example, the developer may store the formal file in the folder named by the first keyword in the preset code library. In this way, the first keyword can be present in the file path information of the formal version file. For example, the first keyword is _ release. In this scenario, the terminal device may obtain file path information of each file in a preset code library. Then, the terminal device may determine whether the file path information of each file includes _ release one by one, and select the file including _ release as the formal version file to be released.
In the second case: in the preset code base, a developer does not set a first keyword in the file identification information of the official version file, but sets a second keyword in the file identification information of the informal version file, so that the file is identified as the informal version file through the second keyword.
Therefore, after receiving the specified command, the terminal device may obtain the file identification information of each file in the preset code library, and determine whether the file identification information of each file contains the first keyword one by one. When the file identification information of each file does not include the first keyword, the terminal device may further determine the file including the second keyword in the file identification information as an informal version file, and select another file in each file except the formal version file as the formal version file.
That is to say, the developer sets a uniform second keyword in the file identification information of all the informal version files, so that the terminal device can automatically exclude which files are informal version files from the preset code library through the second keyword, and thus, the remaining files in the preset code library are identified as the formal version files of the application program. The second keyword can be specifically determined according to naming habits of developers. For example: the second key may be debug or test.
Taking the file identification information as the file name information as an example, the developer may set a uniform second keyword in the file name information of all the informal version files. For example, the suffix of the file names of all the files of the informal version in the preset code library may be set to _ debug. In this scenario, the terminal device may obtain file name information of each file in the preset code library, and determine whether the file name information of each file includes the first keyword one by one. When the file name information of each file does not include the first keyword, the terminal device may further determine the file including the _ debug in the file name information as an informal version file, and select another file in each file except the formal version file as the formal version file.
Taking the file identification information as the file tag information as an example, the developer may set a uniform second keyword in the file tag information of all the informal versions of the file. For example, the file tag suffixes of all the files in the informal version in the preset code library may be set to _ debug. In this scenario, the terminal device may obtain file tag information of each file in the preset code library, and determine whether the file tag information of each file includes the first keyword one by one. When the file tag information of each file does not include the first keyword, the terminal device may further determine the file including the _ debug in the file tag information as an informal version file, and select another file in each file except the formal version file as the formal version file.
Taking the file identification information as the file path information (i.e. the path information of the file stored in the preset code library) as an example, the developer may store the informal version file in the folder named by the second keyword in the preset code library. In this way, the second keyword can be made to exist in the file path information of the informal version file. In this scenario, the terminal device may obtain file path information of each file in the preset code library, and determine whether the file path information of each file includes the first keyword one by one. When the file path information of each file does not include the first keyword, the terminal device may further determine the file including the _ debug in the file path information as an informal version file, and select another file in each file except the formal version file as the formal version file.
According to the file processing method provided by the invention, after the appointed command is received, the formal version file to be issued and the informal version file for testing are automatically identified and selected from the formal version file to be issued and the informal version file to be tested, and then the application program installation package to be issued can be generated according to the selected formal version file. By the method, the error rate in the process of generating the application program installation package can be reduced, the success rate and the efficiency of updating the application program are improved, and the user experience is further improved.
It should be noted that, although the above example takes the generation of the application installation package to be released as an example, the generation method of the application installation package provided by the present invention is described and explained. However, it can be understood by those skilled in the art that the method for generating the application installation package provided by the present invention may also be adopted to generate the application installation package for testing, which has similar implementation principles and technical effects, and thus, no further description is provided herein.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Fig. 2 is a schematic structural diagram of an apparatus for generating an application installation package according to the present invention. Referring to fig. 2, the generating device of the application installation package may include a receiving module 11, a processing module 12, and a generating module 13. Wherein the content of the first and second substances,
a receiving module 11, configured to receive a specified command; the designation command may be, for example, a predetermined packing instruction for acquiring the application installation package.
The processing module 12 is configured to identify and select a formal version file to be released from a formal version file to be released and an informal version file for testing, which are included in the preset code library, after the receiving module 11 receives the specified command; the preset code library referred to herein may be located, for example, on the target server.
And the generating module 13 is configured to generate an application installation package to be released according to the selected formal version file.
In some embodiments, the processing module 12 is specifically configured to obtain file identification information of each file, determine whether the file identification information of each file includes a first keyword one by one, and select a file that includes the first keyword as the official version file to be released; the first keyword of the file is used for identifying the file as the formal version file.
The file may be, for example, a binary file. The file identification information at least includes any one of the following information: file name information, file label information, file path information.
In some embodiments, the processing module 12 is specifically configured to obtain file identification information of each file, determine whether the file identification information of each file includes a first keyword one by one, when the file identification information of each file does not include the first keyword, further determine a file including a second keyword in the file identification information as the informal version file, and select another file in each file except the informal version file as a formal version file; the first keyword of the file is used for identifying the file as the official file, and the second keyword of the file is used for identifying the file as the informal file.
The file may be, for example, a binary file. The file identification information at least includes any one of the following information: file name information, file label information, file path information.
In some embodiments, the generating module 13 is specifically configured to compress the extracted formal version file, generate the formal version file compression package, and generate the application installation package to be released according to the generated formal version file compression package.
The device for generating the application installation package provided by the invention can execute the method embodiment, and the implementation principle and the beneficial effect are similar, and are not described again here.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (7)
1. A method for generating an application installation package, the method comprising:
after receiving a specified command, identifying and selecting a formal version file to be issued from a formal version file to be issued and an informal version file for testing which are contained in a preset code library;
generating an application program installation package to be released according to the selected formal version file;
the identifying and selecting the formal version file to be released comprises the following steps:
acquiring file identification information of each file, judging whether the file identification information of each file contains first keywords one by one, and selecting the file containing the first keywords as the formal version file to be released;
the first keyword of the file is used for identifying the file as the formal file;
the identifying and selecting the formal version file to be released comprises the following steps:
acquiring file identification information of each file, judging whether the file identification information of each file contains first keywords one by one, when the file identification information of each file does not contain the first keywords, further determining the file containing second keywords in the file identification information as the informal version file, and selecting other files except the informal version file in each file as formal version files;
the first keyword of the file is used for identifying the file as the official file, and the second keyword of the file is used for identifying the file as the informal file.
2. The method according to claim 1, wherein the file identification information includes at least any one of the following information: file name information, file label information, file path information.
3. The method according to claim 1 or 2, wherein the file is a binary file.
4. The method according to claim 1 or 2, wherein the generating of the application installation package to be released according to the picked formal version file comprises:
compressing the selected formal version file to generate a formal version file compression package;
and generating an application program installation package to be released according to the generated formal version file compression package.
5. The method according to claim 1 or 2, wherein the specified command is a predetermined packaging instruction for obtaining the application installation package.
6. The method according to claim 1 or 2, wherein the preset code library is provided on a target server.
7. An apparatus for generating an application installation package, the apparatus comprising:
the receiving module is used for receiving a specified command;
the processing module is used for identifying and selecting the formal version files to be issued from the formal version files to be issued and the informal version files for testing contained in the preset code library after the receiving module receives the specified command;
the generating module is used for generating an application program installation package to be released according to the selected formal version file;
the processing module is specifically configured to obtain file identification information of each file, determine one by one whether the file identification information of each file includes a first keyword, and select a file including the first keyword as the official version file to be released; the first keyword of the file is used for identifying the file as the formal file;
the processing module is specifically configured to obtain file identification information of each file, determine whether the file identification information of each file includes a first keyword one by one, when the file identification information of each file does not include the first keyword, further determine a file including a second keyword in the file identification information as the informal version file, and select another file in each file except the informal version file as a formal version file; the first keyword of the file is used for identifying the file as the official file, and the second keyword of the file is used for identifying the file as the informal file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710395584.0A CN107291494B (en) | 2017-05-27 | 2017-05-27 | Method and device for generating application program installation package |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710395584.0A CN107291494B (en) | 2017-05-27 | 2017-05-27 | Method and device for generating application program installation package |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107291494A CN107291494A (en) | 2017-10-24 |
| CN107291494B true CN107291494B (en) | 2021-02-02 |
Family
ID=60095031
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710395584.0A Active CN107291494B (en) | 2017-05-27 | 2017-05-27 | Method and device for generating application program installation package |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107291494B (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050114829A1 (en) * | 2003-10-30 | 2005-05-26 | Microsoft Corporation | Facilitating the process of designing and developing a project |
| CN102591661A (en) * | 2011-12-30 | 2012-07-18 | 苏州汉清投资管理有限公司 | System for realizing software integration |
| US9383976B1 (en) * | 2015-01-15 | 2016-07-05 | Xerox Corporation | Methods and systems for crowdsourcing software development project |
| CN105373401B (en) * | 2015-10-27 | 2018-09-07 | 上海找钢网信息科技股份有限公司 | Software package method for automatically releasing and system |
| CN105912342A (en) * | 2016-04-29 | 2016-08-31 | 乐视控股（北京）有限公司 | APK (Android Package) development method and system based on overlay mechanism |
| CN106484470A (en) * | 2016-09-29 | 2017-03-08 | 努比亚技术有限公司 | The processing method of application program installation kit, device and server |
-
2017
- 2017-05-27 CN CN201710395584.0A patent/CN107291494B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107291494A (en) | 2017-10-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108415832B (en) | Interface automation test method, device, equipment and storage medium | |
| CN104821954A (en) | Cross-platform remote procedure call method | |
| CN111158741B (en) | Method and device for monitoring dependency relationship change of service module on third party class library | |
| CN108959086B (en) | Program package testing deployment method, device, system, electronic equipment and storage medium | |
| US11422917B2 (en) | Deriving software application dependency trees for white-box testing | |
| CN109739704A (en) | A kind of interface test method, server-side and computer readable storage medium | |
| CN117112060A (en) | Component library construction method and device, electronic equipment and storage medium | |
| CN113687858A (en) | Configuration file checking method and device, electronic equipment and storage medium | |
| CA3184892A1 (en) | Data parsing method and device, computer equipment and storage medium for batch stream computing tasks | |
| CN111752820B (en) | gRPC interface pressure test method, computer equipment and storage medium | |
| CN108897588B (en) | Routing method and routing device for communication between modules | |
| CN112631763A (en) | Program changing method and device of host program | |
| CN107291494B (en) | Method and device for generating application program installation package | |
| CN115756484A (en) | Pre-compiled object code warehouse determination method and device and storage medium | |
| CN109213502B (en) | Application updating method and device | |
| US10958514B2 (en) | Generating application-server provisioning configurations | |
| CN113485942A (en) | Automatic testing method and device based on independent module | |
| CN112667491A (en) | Function test method and device of virtual machine | |
| KR101737575B1 (en) | Method and device for verifying data based on sql sentences generated automatically | |
| CN116700840B (en) | File execution method, device, electronic equipment and readable storage medium | |
| CN111090638A (en) | Method and device for comparing transaction functions in database migration | |
| US10726109B2 (en) | Method and system for identifying whether an application is genuine by means of digital watermarks | |
| CN115543486B (en) | Server-free computing oriented cold start delay optimization method, device and equipment | |
| US11940870B2 (en) | Method and device for automatically detecting potential failures in mobile applications | |
| CN115576574A (en) | Code packaging method, device, medium and equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |