A mini program review method and system

Abstract

The embodiments of this specification disclose a mini-program review method and system. The method includes: obtaining a user's first operation through the mini-program review platform, the first operation including uploading part of the mini-program's code data to the mini-program review platform; based on the first operation, calling a first review module to perform a first review on the uploaded part of the mini-program's code data; sending the first review result of the mini-program to the user; obtaining a second operation of the user through the mini-program review platform, based on the second operation, calling a second review module to perform a second review on all the mini-program's code data; when all the mini-program's code data passes the second review, allowing the mini-program to be published.

Description

Technical Field

[0001] This manual relates to the field of computer applications, and in particular to a method for reviewing small programs. Background Art

[0002] With the development of computer technology, the use of mini programs is becoming increasingly common. After a mini program is written or updated, the code data must be uploaded to the mini program publishing platform and submitted for review. The mini program can only be released online after approval. If the mini program fails the review, it will be returned to the developer, who will need to modify the code and resubmit it for review. Uploading and submitting the entire code data for review each time can take a long time, potentially affecting the mini program's launch time.

[0003] Therefore, we hope to provide a method to improve the approval rate of mini programs. Summary of the Invention

[0004] One of the embodiments of this specification provides a mini-program review method, which is applied to a mini-program review platform, and the method includes: obtaining a user's first operation through the mini-program review platform, the first operation including uploading part of the code data of the mini-program to the mini-program review platform; based on the first operation, calling a first review module to perform a first review on the uploaded part of the code data of the mini-program; sending the first review result of the mini-program to the user; obtaining the user's second operation through the mini-program review platform, and based on the second operation, calling a second review module to perform a second review on all the code data of the mini-program, and when all the code data of the mini-program passes the second review, allowing the mini-program to be published.

[0005] In some embodiments, calling the first review module to perform a first review on the uploaded partial code data of the mini program includes: sending the uploaded partial code data of the mini program to the first terminal device through the first review module, and the first terminal device performing a first review on the partial code data of the mini program; and obtaining the first review result of the partial code data of the mini program by the first terminal device.

[0006] In some embodiments, the mini program review platform is a mini program publishing platform.

[0007] In some embodiments, the method further includes: performing a real-machine testing service on the mini-program based on partial code data of the mini-program uploaded to the mini-program review platform; wherein the real-machine testing service includes running the mini-program on a second terminal device.

[0008] One of the embodiments of this specification provides a mini-program review system, which is applied to a mini-program review platform. The system includes: an acquisition module for acquiring a user's first operation, wherein the first operation includes uploading part of the code data of the mini-program to the mini-program review platform; a first review module for performing a first review on the uploaded part of the code data of the mini-program based on the first operation; a sending module for sending the first review result of the mini-program to the user; and a second review module for acquiring the user's second operation, and performing a second review on all the code data of the mini-program based on the second operation. When all the code data of the mini-program passes the second review, the mini-program is allowed to be published.

[0009] In some embodiments, the first review module is used to: send the uploaded partial code data of the mini program to a first terminal device, and have the first terminal device perform a first review of the partial code data of the mini program; and obtain a first review result of the partial code data of the mini program by the first terminal device.

[0010] In some embodiments, the mini program review platform is a mini program publishing platform.

[0011] In some embodiments, the system also includes a testing module, which is used to: perform real-machine testing services on the mini-program based on partial code data of the mini-program uploaded to the mini-program review platform; wherein, the real-machine testing service includes running the mini-program on a second terminal device.

[0012] One of the embodiments of this specification provides a mini-program auditing device, including a processor, which is used to execute the method as described above.

[0013] One embodiment of this specification provides a computer-readable storage medium, which stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes the method described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] This specification will be further described in the form of exemplary embodiments, which will be described in detail with reference to the accompanying drawings. These embodiments are not limiting, and in these embodiments, like numbers represent like structures, wherein:

[0015] Figure 1 This is a schematic diagram of an application scenario of the mini-program review method according to some embodiments of this specification;

[0016] Figure 2 is an exemplary block diagram of a mini-program review system according to some embodiments of this specification;

[0017] Figure 3 It is an exemplary flowchart of the mini-program review method shown in some embodiments of this specification. DETAILED DESCRIPTION

[0018] To more clearly illustrate the technical solutions of the embodiments of this specification, the following briefly describes the drawings required for describing the embodiments. Obviously, the drawings described below are merely examples or embodiments of this specification. Those skilled in the art can apply this specification to other similar scenarios based on these drawings without inventive effort. Unless otherwise apparent from the context or otherwise noted, the same reference numerals in the figures represent the same structure or operation.

[0019] It should be understood that the terms "system," "device," "unit," and / or "module" used herein are a method for distinguishing different components, elements, parts, portions, or assemblies at different levels. However, if other terms can achieve the same purpose, the terms may be replaced by other expressions.

[0020] As used in this specification, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" are not intended to refer to the singular but may include the plural. Generally speaking, the terms "comprise" and "include" only indicate the inclusion of the steps and elements specifically identified, and these steps and elements do not constitute an exclusive list. A method or apparatus may also include other steps or elements.

[0021] The embodiments of this specification provide a method for improving the approval rate of mini-programs. In some embodiments, before a mini-program is released and launched, its code data needs to be reviewed for risks, capabilities, etc. by the mini-program review platform. When the mini-program passes the review, it is released and launched. In some embodiments, after completing the mini-program writing, the developer can upload all the code data of the mini-program to the mini-program review platform and submit it for review. The mini-program review platform can review the code data of the mini-program based on the user's submission review operation. When the mini-program fails to pass the review of the mini-program review platform, the mini-program developer needs to modify the code data of the mini-program and upload all the code data of the mini-program to the mini-program review platform again for review after the modification is completed. Since the time between the development of a mini-program and its launch is very short, submitting the review after all the functions of the mini-program are developed, if the mini-program fails the review and then modifies it again, it may affect the normal launch time of the mini-program. In some embodiments, when the mini-program developer uploads part of the code data of the mini-program to the mini-program review platform, part of the code data of the mini-program can be reviewed. When there are errors in part of the code data of the mini-program, the developer can be notified in time so that it can be modified. This can improve the approval rate of the entire code data of the mini-program and the convenience and efficiency of the mini-program launch.

[0022] Figure 1 It is a schematic diagram of the application scenario of the mini program review method shown in some embodiments of this specification.

[0023] like Figure 1 As shown, the scenario 100 may include a server 110, a network 120, a terminal device 130, a database 140, and other data sources 150. In some embodiments, the mini-program audit method can be applied to the mini-program audit platform. For example, the server 110 can obtain all or part of the code data of the mini-program uploaded to the mini-program audit platform, and audit all or part of the code data of the mini-program through the mini-program audit module (for example, the first audit module, the second audit module). When all the code data pass the audit, the mini-program is allowed to be released online. If it fails to pass the audit, the mini-program can be returned to the developer or the terminal device 130 so that the developer can modify the code data of the mini-program.

[0024] The server 110 can be used to manage resources and process data and / or information from at least one component in the scene 100 or an external data source (e.g., a cloud data center). For example, the server 110 can obtain the mini-program operation data from the terminal device 130. For another example, the server 110 can obtain the code data of the mini-program from the database 140 and review it. In some embodiments, the server 110 can be part of the mini-program review platform. For example, the server 110 can be the background server of the mini-program review platform.

[0025] In some embodiments, server 110 can be a single server or a server group. In some embodiments, the server group can be centralized or distributed (for example, server 110 can be a distributed system). In some embodiments, server 110 can be local or remote. For example, server 110 can access information and / or data stored in terminal device 130 and / or database 140 through network 120. For another example, server 110 can be directly connected to terminal device 130 and / or database 140 to access stored information and / or data. In some embodiments, server 110 can be implemented on a cloud platform. As an example only, a cloud platform can include private cloud, public cloud, hybrid cloud, community cloud, distributed cloud, cross-cloud, multi-cloud, etc. or any combination of the above examples. In some embodiments, server 110 can be implemented on a computing device, such as a computer, mobile device or any device with computing processing capabilities.

[0026] In some embodiments, the server 110 may include a processing device 112. The processing device 112 may process various information and / or data related to the mini-program review to perform one or more functions described in this specification. For example, the processing device 112 may obtain the running data of the mini-program from the terminal device 130. In some embodiments, the processing device 112 may include one or more processors (for example, a single-chip processor or a multi-chip processor). By way of example only, the processing device 112 may include one or more hardware processors, such as a central processing unit (CPU), an application-specific integrated circuit (ASIC), an application-specific instruction set processor (ASIP), a graphics processing unit (GPU), a physical processing unit (PPU), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a controller, a microcontroller unit, a reduced instruction set computer (RISC), a microprocessor, etc., or any combination of the above examples.

[0027] The network 120 can facilitate the exchange of information and / or data. In some embodiments, one or more components in the scene 100 (e.g., server 110, terminal device 130, database 140) can send information and / or data to other components in the scene 100 via the network 120. For example, the server 110 can obtain applet operation data from the terminal device 130 via the network 120. For another example, the server 110 can obtain applet code data from the database 140 via the network 120. In some embodiments, the network 120 can be any one of a wired network or a wireless network or a combination thereof. As an example only, the network 120 can include a cable network, a wired network, an optical fiber network, a remote communication network, an intranet, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), a metropolitan area network (MAN), a wide area network (WAN), a public switched telephone network (PSTN), a Bluetooth network, a ZigBee network, a near field communication (NFC) network, etc. or any combination of the above examples. In some embodiments, the network 120 can include one or more network exchange points. For example, network 120 may include wired or wireless network exchange points, such as base stations and / or Internet exchange points 120-1, 120-2, ..., through which one or more components of scenario 100 may connect to network 120 to exchange data and / or information.

[0028] The terminal device 130 can be used to input and / or retrieve data and / or information. In some embodiments, the terminal device 130 may include a smartphone 130-1, a tablet computer 130-2, a laptop computer 130-3, etc. In some embodiments, the terminal device 130 may include a mobile terminal device, etc. For example, the mobile device may include a smart home device, a wearable device, a smart mobile device, a virtual reality device, an augmented reality device, etc., or any combination of the above. In some embodiments, the smart home device may include smart lighting devices, smart appliance control devices, smart monitoring devices, smart TVs, smart cameras, walkie-talkies, etc., or any combination of the above. In some embodiments, the wearable device may include a bracelet, shoes and socks, glasses, a helmet, a watch, clothing, a backpack, smart accessories, etc., or any combination of the above. In some embodiments, the smart mobile device may include a mobile phone, a personal digital assistant, a gaming device, a navigation device, a POS terminal, a laptop computer, a desktop computer, etc., or any combination of the above.

[0029] In some embodiments, the terminal device 130 can be any device that can provide mini-program operation. For example, the terminal device 130 can obtain the mini-program code data from the server 110 to perform real-device testing of the mini-program. In some embodiments, the terminal device 130 can be any terminal device used for mini-program code writing. For example, a user can use the terminal device 130 to write, update, or modify the mini-program code data. For another example, a user can use the terminal device 130 to upload the mini-program code data to the mini-program review platform. In some embodiments, the terminal device 130 can be used for mini-program code data review. For example, the mini-program review platform can send the mini-program code data to a remote terminal device so that the terminal device can review the code data. In some embodiments, the scenario 100 may include one or more terminal devices 130. For example, the scenario 100 may include one or more mobile terminal devices used for real-device testing. For another example, the scenario 100 may include a mobile terminal device used for real-device testing, as well as a desktop terminal device used for updating, modifying, or reviewing the mini-program code data.

[0030] The database 140 may store data and / or instructions. In some embodiments, the database 140 may store data obtained from the terminal device 130 and / or the network 120. In some embodiments, the database 140 may store data and / or instructions for execution or use by the server 110, and the server 110 may implement the exemplary method described in this specification by executing or using these data and / or instructions. In some embodiments, the database 140 may include a large-capacity memory, a removable memory, a volatile read-write memory, a read-only memory (ROM), etc., or any combination of the above examples. Exemplary large-capacity memory may include a magnetic disk, an optical disk, a solid-state disk, etc. Exemplary removable memory may include a flash drive, a floppy disk, an optical disk, a memory card, a compressed disk, a magnetic tape, etc. In some embodiments, the database 140 may be implemented on a cloud platform. By way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, a cross-cloud, a multi-cloud, etc., or any combination of the above examples.

[0031] In some embodiments, database 140 may be connected to network 120 to communicate with one or more components in scene 100 (e.g., server 110, terminal device 130). One or more components in scene 100 may access data or instructions stored in database 140 through network 120. In some embodiments, database 140 may be directly connected to or communicate with one or more components in scene 100 (e.g., server 110, terminal device 130). In some embodiments, database 140 may be part of server 110 and / or terminal device 130.

[0032] Other data sources 150 can be used to provide one or more sources of other information for scenario 100. In some embodiments, other data sources 150 may include one or more devices, one or more application programming interfaces, one or more database query interfaces, one or more protocol-based information acquisition interfaces, or other ways of obtaining information, or a combination of two or more of the above methods. In some embodiments, the information provided by the data source may include information that already exists when the information is extracted, temporarily generated when the information is extracted, or a combination of the above methods. In some embodiments, other data sources 150 can be used to provide mini-program code data, audit data, and other data for scenario 100.

[0033] In some alternative embodiments, scenario 100 may also include other components for mini-program auditing, for example, it may include a second server for auditing part of the code data of the mini-program, etc. This specification does not limit this.

[0034] Figure 2 This is an exemplary block diagram of a mini-program audit system according to some embodiments of this specification. Figure 2 As shown, the system 200 is applied to a mini program review platform, which may include an acquisition module 210 , a first review module 220 , a sending module 230 and a second review module 240 .

[0035] The acquisition module 210 can be used to obtain the user's first operation. The first operation may include uploading part of the code data of the mini program to the mini program review platform. In some embodiments, the mini program review platform may include a mini program publishing platform. For more information about uploading part of the code data of the mini program to the mini program review platform, please refer to Figure 3 The related descriptions will not be repeated here.

[0036] The first audit module 220 can be used to perform a first audit on part of the code data of the uploaded mini program based on the user's first operation. In some embodiments, the first audit module 220 can send part of the code data of the uploaded mini program to a first terminal device, and the first terminal device can perform a first audit on part of the code data of the mini program; and obtain the first audit result of the part of the code data of the mini program by the first terminal device. For more information about the first audit of part of the code data of the uploaded mini program, please refer to Figure 3 The related descriptions will not be repeated here.

[0037] The sending module 230 can be used to send the first audit result of the mini program to the user. For more information about sending the first audit result of the mini program to the user, please refer to Figure 3 The related descriptions will not be repeated here.

[0038] The second audit module 240 can be used to perform a second audit on all code data of the mini program. In some embodiments, the second audit module 240 can obtain the user's second operation, and based on the second operation, perform a second audit on all code data of the mini program. When all code data of the mini program passes the second audit, the mini program audit platform can allow the mini program to be published. In some embodiments, the second operation can be a submission audit operation for the mini program. For more information about the second audit of all code data of the mini program, please refer to Figure 3 The related descriptions will not be repeated here.

[0039] In some embodiments, the system 200 may further include a testing module 250. The testing module 250 may be used to perform real-machine testing on the mini-program. In some embodiments, the testing module 250 may perform real-machine testing services on the mini-program based on partial code data of the mini-program uploaded to the mini-program review platform. In some embodiments, the testing module 250 may perform real-machine testing services based on all code data of the mini-program uploaded to the mini-program review platform. The real-machine testing service includes running the mini-program on a second terminal device.

[0040] It should be understood that Figure 2 The system and its modules shown can be implemented in various ways. For example, the system and its modules can be implemented by hardware, software, or a combination of software and hardware. Among them, the hardware part can be implemented using dedicated logic; the software part can be stored in a memory and executed by an appropriate instruction execution system, such as a microprocessor or dedicated design hardware. Those skilled in the art will understand that the above-mentioned methods and systems can be implemented using computer-executable instructions and / or contained in processor control code, for example, such as a carrier medium such as a disk, CD or DVD-ROM, a programmable memory such as a read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. Such code is provided on the device and its modules of this specification. Not only can the hardware circuits such as ultra-large-scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc. be implemented, they can also be implemented using software executed by various types of processors, and can also be implemented by a combination of the above-mentioned hardware circuits and software (for example, firmware).

[0041] It should be noted that the above description of system 200 is for convenience only and does not limit this specification to the scope of the embodiments described. It is understood that those skilled in the art, after understanding the principles of the system, may arbitrarily combine the various modules or form subsystems connected to other modules without departing from these principles. For example, system 200 may also include a communication module for communicating with other components. For another example, the various modules in system 200 may share a storage module, or each module may have its own storage module. Variations such as these are within the scope of protection of this specification.

[0042] Figure 3 This is an exemplary flow chart of the mini-program review method according to some embodiments of this specification. Figure 3 As shown, method 300 can be applied to a mini-program audit platform, which may include steps 310, 320, 330, and 340. In some embodiments, method 300 may be implemented by a processing device (e.g., server 110) or a mini-program audit system (e.g., system 200).

[0043] Step 310 , obtaining the user's first operation, where the first operation includes uploading part of the code data of the mini program to the mini program review platform. In some embodiments, step 310 can be performed by the acquisition module 210 .

[0044] A mini program review platform refers to a platform that can review the security, performance, content, etc. of mini programs. By reviewing mini programs, it is possible to improve the control of mini programs and help mini programs be released online. In some embodiments, the mini program review platform can be a mini program release platform. That is, the mini program review platform can be a one-stop platform that provides mini program release processes and corresponding operating capabilities. In some embodiments, the mini program review platform can obtain the user's first operation, second operation, and other operations on the platform corresponding to different instructions of the mini program review platform. For example, the first operation can be the operation of the mini program developer (i.e., the user) uploading part of the mini program code data to the mini program review platform, and the second operation can be the operation of the mini program developer submitting the mini program for review. In some embodiments, the mini program review platform can store or manage the mini program code based on the user's upload operation (i.e., the first operation); the mini program review platform can review the mini program code data based on the user's submission review operation (i.e., the second operation), allow it to be released online if the review passes, and notify the developer to modify the mini program data if the review fails.

[0045] In some embodiments, the first operation may include a direct upload operation or an indirect upload operation. As an example only, the first operation may be an operation for a user to upload the mini program code data to the mini program review platform through other terminal devices. For example, a mini program developer can edit the mini program code on the mini program editor, and the first operation may be an operation for the developer to upload part of the functions of the mini program to the mini program review platform after editing it. The mini program review platform can obtain the user's first operation based on the data uploaded from the mini program editor. In some embodiments, the mini program developer can directly perform the upload operation of part or all of the mini program data on the page of the mini program review platform. For example, a user can upload part of the code data of the mini program to the mini program review platform by clicking the upload button on the mini program review platform page. By uploading part or all of the code data of the mini program to the mini program review platform, the edited mini program code data can be saved to the mini program review platform.

[0046] In step 320 , based on the first operation, the first audit module is called to perform a first audit on the uploaded portion of the code data of the mini program. In some embodiments, step 320 may be performed by the first audit module 220 .

[0047] In some embodiments, the audit items of the mini program may include at least one of a security audit, a content audit, and a capability audit. For example, a security audit may include a code security audit, a user privacy security audit, and a data security audit. Content audit may mean that the content in the mini program to be audited must not include pornography, violence, sensitive topics, or other illegal and unlawful content. Capability audit may refer to an audit of the mini program's ability to be implemented and run normally. For example, the mini program does not have serious bugs (vulnerabilities). For example, bugs may include but are not limited to being unable to add, unable to open, unable to return, unable to exit, severe freezes, and the program is prone to crashes.

[0048] In some embodiments, since the user only uploaded a portion of the mini-program's code data to the mini-program review platform during the first operation, the processing device may invoke a first review module that only includes a portion of the mini-program's review items to perform a first review on the uploaded portion of the mini-program's code data. For example, if all review items for a mini-program review include security review, content review, and performance review, the first review module may only include security review and content review of the portion of the mini-program's code data. In some embodiments, the review items for the first review may range from 10% to 95% of all review items for the mini-program. For example, the review items for the first review may range from 30% to 50% of all review items. For another example, the review items for the first review may range from 50% to 80% of all review items. For another example, the review items for the first review may range from 80% to 95% of all review items. Preferably, the review items for the first review may range from 80% to 95% of all review items. It will be understood that the above numerical ranges are merely examples. In alternative embodiments, the first review items may range from any percentage of all review items, for example, the same as all review items. This specification does not impose any limitation on this.

[0049] In some embodiments, the first audit may include a local audit or a remote audit. For example, based on the user's first operation, the mini-program audit platform may call the first audit module through the mini-program audit platform's server (e.g., server 110) to perform a first audit on the uploaded part of the mini-program's code data to obtain a first audit result. For another example, based on the user's first operation, the mini-program audit platform may send the uploaded part of the mini-program's code data to the first terminal device, and the first terminal device may perform a first audit on the part of the mini-program's code data, and obtain the first audit result of the first terminal device on the part of the mini-program's code data.

[0050] In some embodiments, the processing device can perform a first audit on the mini-program using a trained machine learning model. For example, a portion of the mini-program's code data can be input into the trained first audit model to obtain a first audit result output by the first audit model.

[0051] The processing device can perform a first review operation on the portion of the Mini Program code data uploaded to the Mini Program review platform each time it receives the user's first operation (i.e., upload operation). By reviewing the portion of the Mini Program code data based on the user's upload operation, problems (such as security risks, code errors, etc.) in the Mini Program code data can be discovered in a timely manner, allowing developers to modify the code data in a timely manner. This reduces the failure rate when reviewing the entire Mini Program code data based on the user's submission review operation, thereby improving the efficiency of Mini Program launches.

[0052] Step 330 , sending the first review result of the mini program to the user. In some embodiments, step 330 may be performed by the sending module 230 .

[0053] The first audit result may include audit passed and audit failed. In some embodiments, the processing device may generate a first audit report for the mini program based on the first audit result. For example, an error report may be generated based on problems existing in the mini program code data in the first audit result. For example, the error report may include but is not limited to the image size in the mini program being too large, the existence of data security risks, etc. In some embodiments, the first audit report may include one or more combinations of audit results, existing problems, the location of the problem, etc. For example, the audit report may be: audit failed, there is a data security risk on line 35 of the code, etc.; or the audit report may be: audit passed, or no problems were found in this part of the code data, etc.

[0054] In some embodiments, the processing device may store the first audit report of the mini program in a storage device (e.g., database 140). In some embodiments, the processing device may send the first audit report to the mini program developer (i.e., the user). For example, the first audit report may be sent to the developer's terminal device. In some embodiments, the processing device may send a data link containing the first audit report or the first audit result to the user. For example, a prompt message similar to "The audit has been completed, click this link to view the audit results" may be sent to the user.

[0055] After the developer modifies the mini program code data based on the first review results, he or she can re-upload this part of the data, or upload it together with new code data after it is updated. This manual does not impose any restrictions on this.

[0056] If the user operation obtained through the Mini Program review platform is still the user's first operation, then return to step 310. For example, the user corrects the error and changes part of the Mini Program code data before uploading it again. If the user operation obtained through the Mini Program review platform is the user's second operation, then proceed to step 340.

[0057] Step 340: Obtain the user's second operation. Based on the second operation, call the second review module to perform a second review of all the code data of the mini program. When all the code data of the mini program passes the second review, the mini program is allowed to be released. In some embodiments, step 340 can be performed by the second review module 240.

[0058] The second operation may refer to a user initiating a review request to the mini-program review platform. For example, after a user (developer) completes all mini-program functions and uploads all corresponding code data to the mini-program review platform, they can initiate a review request to the mini-program review platform by clicking "Submit for Review" on the mini-program review platform page. In some embodiments, a user may also initiate a review request after uploading part of the mini-program's code data. Based on the user's second operation obtained by the mini-program review platform, the processing device may invoke the first review module to perform a second review of the mini-program's entire code data. In some embodiments, the second review may review code data that was not reviewed in the first review. In some embodiments, the second review may review code data modified after the first review. In some embodiments, the second review may review all mini-program code data. For example, the review may include whether the functions implemented in the mini-program's entire code data involve violence, violate social morality, violate laws and regulations, etc., whether the functions implemented in the code data protect user privacy, whether images included in the code data can be displayed normally, and whether the mini-program's application program interface capabilities meet publishing requirements. In some embodiments, the second review may include all review items for the mini-program. In some embodiments, the mini-program review items of the first review module may be part of the mini-program review items of the second review module. In some embodiments, the mini-program review items of the first review module may be the same as the mini-program review items of the second review module.

[0059] In some embodiments, all code data of the mini-program can be input into the second audit model through the trained second audit model to obtain the second audit result output by the second audit model. In some embodiments, the second audit model and the first audit model can be the same or different audit models. For example, the first audit model and the second audit model can be the same model. When the first audit is triggered based on the user upload operation (i.e., the first operation), some mini-program audit modules in the audit model (e.g., the first audit module) can be called to perform the corresponding audit operation. When the second audit is triggered based on the user submission audit operation (i.e., the second operation), all audit modules in the audit model (e.g., the second audit module) can be called to perform the corresponding audit operation.

[0060] If all the code data of the mini program passes the second review, the mini program is allowed to be published. For example, the mini program review platform can directly publish the mini program. In some embodiments, if all the code data of the mini program fails the second review, the review can be rejected and a second review report can be generated. In some embodiments, the mini program review platform can send the generated second review report to the user so that the user can make changes to the mini program code data.

[0061] In some embodiments, the processing device may perform a real-machine testing service on the mini-program when the mini-program passes the first review or the second review. The real-machine testing service includes running the mini-program on a second terminal device. For example, a real-machine testing service may be performed on the mini-program based on part of the code data of the mini-program uploaded to the mini-program review platform. By performing a real-machine testing service on the mini-program, it is possible to test whether the functions of the mini-program can be normally implemented on the terminal device. In some embodiments, the processing device may determine whether to publish the mini-program based on the real-machine testing results. For example, when the functions of the mini-program cannot be executed normally on the terminal device, the results may be fed back to the developer so that the developer can modify it and then review and / or publish it after the modification.

[0062] The mini-program review method provided in the embodiments of this specification can be continuously constructed. Each time the mini-program review platform obtains partial code data of the mini-program uploaded by the user, it triggers the first review operation for the partial code data of the mini-program. This can help developers promptly discover problems in the mini-program code data and solve them in a timely manner, thereby increasing the mini-program review pass rate based on the submission review operation by 20%.

[0063] It should be noted that the above description of method 300 is for illustrative purposes only and does not limit the scope of application of this specification. Those skilled in the art may, under the guidance of this specification, make various modifications and alterations to method 300. However, such modifications and alterations remain within the scope of this specification. For example, in step 330, after the first audit result is sent to the user, the user-modified code data may be retrieved from the terminal device and the first audit operation may be performed again.

[0064] The beneficial effects that may be brought about by the embodiments of this specification include but are not limited to: (1) After the mini program developer has developed part of the code, he can trigger the review operation by uploading it and obtain the review results. He can modify the problematic code data in a timely manner, thereby significantly improving the review pass rate; (2) There is no need to wait for all the mini program code data to be reviewed, which shortens the review and the time for returning the review results, improves the review pass rate, and ensures that the mini program can be launched on time. It should be noted that different embodiments may produce different beneficial effects. In different embodiments, the beneficial effects that may be produced may be any one or a combination of the above, or any other possible beneficial effects.

[0065] While the basic concepts have been described above, it will be apparent to those skilled in the art that the detailed disclosure is merely illustrative and does not limit the embodiments of this specification. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and revisions to the embodiments of this specification. Such modifications, improvements, and revisions are suggested in the embodiments of this specification and remain within the spirit and scope of the exemplary embodiments of this specification.

[0066] This specification also uses specific terms to describe the embodiments of this specification. For example, "one embodiment," "an embodiment," and / or "some embodiments" refer to a feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "one embodiment," "an embodiment," or "an alternative embodiment" two or more times in different locations in this specification do not necessarily refer to the same embodiment. Furthermore, certain features, structures, or characteristics of one or more embodiments of this specification may be appropriately combined.

[0067] In addition, it will be understood by those skilled in the art that the various aspects of the embodiments of this specification may be illustrated and described by a number of patentable categories or situations, including any new and useful process, machine, product or combination of substances, or any new and useful improvements thereto. Accordingly, the various aspects of the embodiments of this specification may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may all be referred to as "data blocks," "modules," "engines," "units," "components," or "systems." In addition, the various aspects of the embodiments of this specification may be represented as a computer product located in one or more computer-readable media, the product including computer-readable program code.

[0068] A computer storage medium may include a propagated data signal embodying the computer program code, for example, in baseband or as part of a carrier wave. The propagated signal may be in a variety of forms, including electromagnetic, optical, or any suitable combination thereof. A computer storage medium may be any computer-readable medium other than a computer-readable storage medium that can be connected to an instruction execution system, apparatus, or device to communicate, propagate, or transfer the program for use. The program code on the computer storage medium may be transmitted via any suitable medium, including radio, cable, fiber optic cable, RF, or similar media, or any combination of these.

[0069] The computer program coding required for the operation of each part of the embodiment of this specification can be written in any one or more programming languages, including object-oriented programming languages ​​such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python, etc., conventional procedural programming languages ​​such as C language, VisualBasic, Fortran2003, Perl, COBOL2002, PHP, ABAP, dynamic programming languages ​​such as Python, Ruby and Groovy, or other programming languages, etc. The program coding can be run completely on the user's computer, or run on the user's computer as an independent software package, or partly run on the user's computer and partly run on a remote computer, or run completely on a remote computer or processing equipment. In the latter case, the remote computer can be connected to the user's computer by any network form, such as a local area network (LAN) or a wide area network (WAN), or be connected to an external computer (such as by the Internet), or in a cloud computing environment, or used as a service such as software as a service (SaaS).

[0070] In addition, unless expressly stated in the claims, the order of the processing elements and sequences, the use of alphanumeric characters, or the use of other names described in the embodiments of this specification are not intended to limit the order of the processes and methods of the embodiments of this specification. Although the above disclosure discusses some of the invention embodiments that are currently considered useful through various examples, it should be understood that such details are for illustrative purposes only, and the appended claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing processing device or mobile device.

[0071] Similarly, it should be noted that, in order to simplify the presentation of the embodiments disclosed in this specification and thereby facilitate understanding of one or more invention embodiments, the foregoing descriptions of the embodiments of this specification sometimes combine multiple features into a single embodiment, figure, or description thereof. However, this disclosure method does not mean that the embodiments of this specification require more features than those recited in the claims. In fact, an embodiment may have fewer features than all of the features of a single disclosed embodiment.

[0072] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, and documents, cited in this specification is hereby incorporated by reference in its entirety. This includes application history documents that are inconsistent with or conflict with the content of this specification, as well as documents (currently or subsequently attached to this specification) that limit the broadest scope of the claims of this specification. It should be noted that if the descriptions, definitions, and / or terminology used in the accompanying materials are inconsistent or conflicting with the content of this specification, the descriptions, definitions, and / or terminology used in this specification will control.

[0073] Finally, it should be understood that the embodiments described in this specification are intended only to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of the embodiments of this specification. Therefore, by way of example and not limitation, alternative configurations of the embodiments of this specification may be considered consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly described and illustrated in this specification.

Claims

1. A mini program review method, applied to a mini program review platform, comprising: Obtaining, through the mini program review platform, a first operation of the user, wherein the first operation includes uploading part of the code data of the mini program to the mini program review platform; Based on the first operation, calling a first review module to perform a first review on the uploaded portion of code data of the mini program; Sending the first review result of the mini program to the user; Obtaining, through the mini program review platform, a second operation of the user, where the second operation includes initiating an operation of submitting a review request to the mini program review platform; Based on the second operation, a second review module is called to perform a second review on all code data of the mini program. When all code data of the mini program passes the second review, the mini program is allowed to be released.

2. The method according to claim 1, wherein calling the first audit module to perform a first audit on the uploaded portion of the code data of the mini program comprises: Sending the uploaded partial code data of the mini program to a first terminal device through the first review module, and having the first terminal device perform a first review on the partial code data of the mini program; as well as Obtain a first review result of the first terminal device on part of the code data of the mini program.

3. According to the method of claim 1, the mini program review platform is a mini program publishing platform.

4. The method according to claim 1, further comprising: Performing real-device testing services on the mini-program based on partial code data of the mini-program uploaded to the mini-program review platform; The real device testing service includes running the mini program on a second terminal device.

5. A mini program review system, which is applied to a mini program review platform and includes: An acquisition module, configured to acquire a first operation of the user, wherein the first operation includes uploading part of the code data of the mini program to the mini program review platform; A first review module, configured to perform a first review on the uploaded portion of code data of the mini program based on the first operation; A sending module, configured to send the first review result of the mini program to the user; The second review module is used to obtain the second operation of the user, and based on the second operation, perform a second review of all the code data of the mini program. When all the code data of the mini program passes the second review, the mini program is allowed to be released; the second operation includes initiating an operation of submitting a review request to the mini program review platform.

6. The system according to claim 5, wherein the first audit module is configured to: Sending the uploaded partial code data of the mini program to a first terminal device, and having the first terminal device perform a first review on the partial code data of the mini program; and Obtain a first review result of the first terminal device on part of the code data of the mini program.

7. In the system according to claim 5, the mini program review platform is a mini program publishing platform.

8. The system according to claim 5, further comprising a testing module, wherein the testing module is configured to: Performing real-device testing services on the mini-program based on partial code data of the mini-program uploaded to the mini-program review platform; in, The real device testing service includes running the mini program on a second terminal device.

9. A mini-program auditing device, comprising a processor, wherein the processor is configured to execute the method according to any one of claims 1 to 4.

10. A computer-readable storage medium, wherein the storage medium stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes the method according to any one of claims 1 to 4.

Images