CN114138321A

CN114138321A - Applet auditing method and system

Info

Publication number: CN114138321A
Application number: CN202010913725.5A
Authority: CN
Inventors: 张亮
Original assignee: Alipay Labs Singapore Pte Ltd
Current assignee: Advanced Nova Technology Singapore Holdings Ltd
Priority date: 2020-09-03
Filing date: 2020-09-03
Publication date: 2022-03-04

Abstract

The embodiment of the specification discloses a small program auditing method and system. The method comprises the following steps: acquiring a first operation of a user through an applet auditing platform, wherein the first operation comprises uploading partial code data of the applet to the applet auditing platform; calling a first auditing module to conduct first auditing on part of uploaded code data of the applet based on the first operation; sending the first review result of the applet to the user; and acquiring a second operation of the user through the applet auditing platform, calling a second auditing module to perform second auditing on all code data of the applet based on the second operation, and allowing the applet to be issued when all the code data of the applet pass the second auditing.

Description

Applet auditing method and system

Technical Field

The specification relates to the field of computer application, in particular to an applet auditing method.

Background

With the development of computer technology, the application of applets is more and more common. After the small program is written or updated, the code data needs to be uploaded on the small program publishing platform, the verification is submitted, and the small program can be published and online after the small program is verified. If the small program is not approved, the small program needs to be returned to the developer, and the developer needs to revise the small program code and then submit the audit again. All code data are uploaded and submitted to auditing each time, auditing time is long, and online time of the small program can be influenced.

It is therefore desirable to provide a method for increasing the throughput rate of a program audit.

Disclosure of Invention

One of the embodiments of the present specification provides an applet auditing method, which is applied to an applet auditing platform, and includes: acquiring a first operation of a user through the applet auditing platform, wherein the first operation comprises uploading partial code data of the applet to the applet auditing platform; calling a first auditing module to conduct first auditing on part of uploaded code data of the applet based on the first operation; sending the first review result of the applet to the user; and acquiring a second operation of the user through the applet auditing platform, calling a second auditing module to perform second auditing on all code data of the applet based on the second operation, and allowing the applet to be issued when all the code data of the applet pass the second auditing.

In some embodiments, the invoking a first audit module to perform a first audit on the uploaded partial code data of the applet comprises: the uploaded part of code data of the small program is sent to a first terminal device through the first auditing module, and the first terminal device conducts first auditing on the part of code data of the small program; and acquiring a first examination result of the first terminal device on the partial code data of the applet.

In some embodiments, the applet auditing platform is an applet publishing platform.

In some embodiments, the method further comprises: performing real machine test service on the small program based on partial code data of the small program uploaded to the small program checking platform; wherein the live testing service comprises running the applet at a second terminal device.

One of embodiments of the present specification provides an applet auditing system, where the system is applied to an applet auditing platform, and the system includes: the acquisition module is used for acquiring a first operation of a user, wherein the first operation comprises uploading partial code data of the applet to the applet auditing platform; the first auditing module is used for carrying out first auditing on the uploaded partial code data of the applet based on the first operation; the sending module is used for sending the first examination result of the applet to the user; and the second auditing module is used for acquiring second operation of the user, performing second auditing on all code data of the applet based on the second operation, and allowing the applet to be issued when all the code data of the applet pass through the second auditing.

In some embodiments, the first review module is to: sending the uploaded partial code data of the small program to first terminal equipment, and performing first audit on the partial code data of the small program by the first terminal equipment; and acquiring a first examination result of the first terminal device on the partial code data of the applet.

In some embodiments, the system further comprises a testing module to: performing real machine test service on the small program based on partial code data of the small program uploaded to the small program checking platform; wherein the live testing service comprises running the applet at a second terminal device.

One of the embodiments of the present specification provides an applet auditing apparatus including a processor configured to execute the method described above.

One of the embodiments of the present specification provides a computer-readable storage medium storing computer instructions, and when the computer instructions in the storage medium are read by a computer, the computer executes the method as described above.

Drawings

The present description will be further explained by way of exemplary embodiments, which will be described in detail by way of the accompanying drawings. These embodiments are not intended to be limiting, and in these embodiments like numerals are used to indicate like structures, wherein:

FIG. 1 is a schematic diagram of an application scenario of an applet auditing method according to some embodiments of the present description;

FIG. 2 is an exemplary block diagram of an applet auditing system shown in accordance with some embodiments of the present description;

FIG. 3 is an exemplary flow diagram of an applet auditing method according to some embodiments shown herein.

Detailed Description

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only examples or embodiments of the present description, and that for a person skilled in the art, the present description can also be applied to other similar scenarios on the basis of these drawings without inventive effort. Unless otherwise apparent from the context, or otherwise indicated, like reference numbers in the figures refer to the same structure or operation.

It should be understood that "system", "device", "unit" and/or "module" as used herein is a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, other words may be substituted by other expressions if they accomplish the same purpose.

As used in this specification, the terms "a", "an" and/or "the" are not intended to be inclusive of the singular, but rather are intended to be inclusive of the plural, unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.

The embodiment of the specification provides a method for improving the auditing passing rate of an applet. In some embodiments, before the applet is released and brought online, the applet auditing platform needs to audit the code data of the applet for risks, capabilities and the like, and when the applet auditing is passed, the applet is released and brought online. In some embodiments, after the applet is written, the developer may upload all code data of the applet to an applet auditing platform and submit the audit, and the applet auditing platform may audit the code data of the applet based on a user submitting audit operation. When the small program does not pass the review of the small program review platform, the small program developer needs to modify the code data of the small program, and after the modification is completed, all the code data of the small program are uploaded to the small program review platform again to submit the review. Because the time before the development of the small program is finished and the small program is online is short, the auditing is submitted after the development of all functions of the small program is finished, and if the auditing of the small program is not passed through and is modified again, the normal online time of the small program can be influenced. In some embodiments, when the small program developer uploads the small program partial code data to the small program auditing platform, the small program partial code data can be audited, and when the small program partial code data has errors, the developer can be informed in time to modify the small program partial code data, so that the auditing passing rate of all the small program code data and the small program on-line convenience and efficiency can be improved.

Fig. 1 is a schematic view of an application scenario of an applet auditing method according to some embodiments of the present description.

As shown in FIG. 1, 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 applet auditing method may be applied to an applet auditing platform. For example, the server 110 may obtain all or part of the code data of the applet uploaded to the applet auditing platform, audit all or part of the code data of the applet through the applet auditing module (e.g., the first auditing module and the second auditing module), allow the applet to be released online when all the code data audits are passed, and return the applet to the developer or the terminal device 130 if the audit is not passed, so that the developer may modify the code data of the applet.

The server 110 may be used to manage resources and process data and/or information from at least one component in the scenario 100 or an external data source (e.g., a cloud data center). For example, the server 110 may obtain applet run data from the terminal device 130. As another example, the server 110 may obtain code data for an applet from the database 140 and audit it. In some embodiments, the server 110 may be part of an applet auditing platform. For example, the server 110 may be a backend server of the applet auditing platform.

In some embodiments, the server 110 may be a single server or a server farm. In some embodiments, the server farm may be centralized or distributed (e.g., the server 110 may be a distributed system). In some embodiments, the server 110 may be local or remote. For example, server 110 may access information and/or data stored in terminal device 130 and/or database 140 via network 120. As another example, server 110 may be directly connected to terminal device 130 and/or database 140 to access stored information and/or data. In some embodiments, the server 110 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, across clouds, multiple clouds, the like, or any combination of the above. In some embodiments, the server 110 may be implemented on a computing device, such as a computer, a mobile device, or any device with computing processing capabilities.

In some embodiments, the server 110 may include a processing device 112. The processing device 112 may process various applet audit related information and/or data to perform one or more of the functions described herein. For example, the processing device 112 may obtain the operating data of the applet from the terminal device 130. In some embodiments, the processing device 112 may include one or more processors (e.g., a single wafer processor or a multi-wafer 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), an image processing unit (GPU), a physical arithmetic 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, or the like, or any combination of the above.

Network 120 may facilitate the exchange of information and/or data. In some embodiments, one or more components (e.g., server 110, terminal device 130, database 140) in the scenario 100 may send information and/or data to other components in the scenario 100 through the network 120. For example, the server 110 may obtain applet running data from the terminal device 130 via the network 120. As another example, the server 110 may obtain the applet code data from the database 140 via the network 120. In some embodiments, the network 120 may be any one or combination of a wired network or a wireless network. By way of example only, network 120 may include a cable network, a wired network, a fiber optic 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, the like, or any combination of the above. In some embodiments, network 120 may include one or more network switching points. For example, the network 120 may include wired or wireless network switching points, such as base stations and/or internet switching points 120-1, 120-2, … …, through which one or more components of the scenario 100 may connect to the network 120 to exchange data and/or information.

Terminal device 130 may be used to input and/or retrieve data and/or information. In some embodiments, the end device 130 may include a smartphone 130-1, a tablet 130-2, a laptop 130-3, and so on. In some embodiments, terminal device 130 may comprise a mobile terminal device or the like. 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, the like, or any combination of the above. In some embodiments, the smart home devices may include smart lighting devices, control devices for smart appliances, smart monitoring devices, smart televisions, smart cameras, interphones, and the like, or any combination thereof. In some embodiments, the wearable device may include a bracelet, footwear, glasses, helmet, watch, clothing, backpack, smart accessory, or the like, or any combination of the above. In some embodiments, the smart mobile device may include a mobile handset, a personal digital assistant, a gaming device, a navigation device, a POS machine, a laptop computer, a desktop computer, the like, or any combination of the above.

In some embodiments, terminal device 130 may be any device that may provide applet execution. For example, the terminal device 130 may obtain applet code data from the server 110 to perform an applet true machine test. In some embodiments, the terminal device 130 may be any terminal device used in the programming of applet code. For example, a user may write, update or modify applet code data via the terminal device 130. For another example, the user may upload the code data of the applet to the applet auditing platform through the terminal device 130. In some embodiments, the terminal device 130 may be used for applet code data auditing. For example, the applet auditing platform may send the code data of the applet to a remote terminal device so that the terminal device can audit the code data. In some embodiments, the scenario 100 may include one or more terminal devices 130. For example, scenario 100 may include one or more mobile terminal devices for live machine testing. As another example, scenario 100 may include a mobile terminal device for live machine testing, and a desktop terminal device for applet code data update, modification, or auditing.

Database 140 may store data and/or instructions. In some embodiments, database 140 may store data obtained from terminal device 130 and/or network 120. In some embodiments, database 140 may store data and/or instructions for execution or use by server 110, which server 110 may execute or use to implement the example methods described herein. In some embodiments, database 140 may include mass storage, removable memory, volatile read-write memory, read-only memory (ROM), the like, or any combination of the above. Exemplary mass storage devices may include magnetic disks, optical disks, solid state disks, and the like. Exemplary removable memories may include flash drives, floppy disks, optical disks, memory cards, compact disks, magnetic tape, and the like. In some embodiments, 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, across clouds, multiple clouds, the like, or any combination of the above.

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

Other data sources 150 may be used to provide one or more sources of other information for the scene 100. In some embodiments, the other data sources 150 may include one or more devices, one or more application program interfaces, one or more database query interfaces, one or more protocol-based information acquisition interfaces, or other manners in which information may be acquired, or the like, or combinations of two or more of the foregoing. In some embodiments, the information provided by the data source may include information that already exists at the time the information is extracted, that is temporarily generated at the time the information is extracted, or a combination thereof. In some embodiments, other data sources 150 may be used to provide data such as applet code data, audit data, and the like for the scenario 100.

In some alternative embodiments, the scenario 100 may further include other components for applet review, for example, a second server for reviewing partial code data of the applet may be included, and the present specification does not limit this.

FIG. 2 is an exemplary block diagram of an applet auditing system, shown in some embodiments according to the present description. As shown in FIG. 2, the system 200 is applied to an applet review platform, which can include an acquisition module 210, a first review module 220, a sending module 230, and a second review module 240.

The obtaining module 210 may be configured to obtain a first operation of a user. The first operation may include an upload operation of uploading partial code data of the applet to an applet auditing platform. In some embodiments, the applet auditing platform may include an applet publishing platform. For more contents of uploading part of the code data of the applet to the applet auditing platform, reference may be made to fig. 3 and its related description, which are not described herein again.

The first auditing module 220 may be configured to perform a first audit on the uploaded partial code data of the applet based on a first operation of the user. In some embodiments, the first auditing module 220 may send the uploaded partial code data of the applet to a first terminal device, and the first terminal device performs a first audit on the partial code data of the applet; and acquiring a first examination result of the first terminal device on the partial code data of the applet. For more details on the first audit of the part of the code data of the uploaded applet, reference may be made to fig. 3 and the related description thereof, which are not described herein again.

The sending module 230 may be configured to send the first review result of the applet to the user. For more contents of sending the first review result of the applet to the user, reference may be made to fig. 3 and the related description thereof, which are not described herein again.

The second audit module 240 may be used to perform a second audit on the entire code data of the applet. In some embodiments, the second auditing module 240 may obtain a second operation of the user, and perform a second audit on the entire code data of the applet based on the second operation. The applet audit platform may allow the applet to issue when all code data for the applet passes the second audit. In some embodiments, the second operation may be a commit audit operation on the applet. For more details on the second audit of the whole code data of the applet, reference may be made to fig. 3 and the related description thereof, which are not described herein again.

In some embodiments, system 200 may also include a test module 250. The test module 250 may be used to perform a true machine test on the applet. In some embodiments, the testing module 250 may service the applet for live testing based on the portion of the code data of the applet uploaded to the applet auditing platform. In some embodiments, the testing module 250 may perform a live machine testing service based on the entire code data of the applet uploaded to the applet auditing platform. And the real machine testing service comprises the step of running the small program on the second terminal equipment.

It should be understood that the system and its modules shown in FIG. 2 may be implemented in a variety of ways. For example, the system and its modules may be implemented by hardware, software, or a combination of software and hardware. Wherein the hardware portion may be implemented using dedicated logic; the software portions may be stored in a memory for execution by a suitable instruction execution system, such as a microprocessor or specially designed hardware. Those skilled in the art will appreciate that the methods and systems described above may be implemented using computer executable instructions and/or embodied in processor control code, such code being provided, for example, on a carrier medium such as a diskette, CD-or DVD-ROM, a programmable memory such as read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. The devices and modules thereof in this specification may be implemented not only by hardware circuits such as very 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., but also by software executed by various types of processors, for example, or by a combination of the above hardware circuits and software (e.g., firmware).

It should be noted that the above description of system 200 is merely for convenience of description and is not intended to limit the scope of the present disclosure to the illustrated embodiments. It will be appreciated by those skilled in the art that, given the teachings of the present system, any combination of modules or sub-system configurations may be used to connect to other modules without departing from such teachings. For example, the system 200 may also include a communication module for communicating with other components. For another example, the modules in the system 200 may share one memory module, and each module may have a memory module. Such variations are within the scope of the present disclosure.

FIG. 3 is an exemplary flow diagram of an applet auditing method according to some embodiments shown herein. As shown in FIG. 3, the method 300 may be applied to an applet auditing platform, which may include

steps

310, 320, 330, and 340. In some embodiments, the method 300 may be implemented by a processing device (e.g., the server 110) or an applet auditing system (e.g., the system 200).

In step 310, a first operation of the user is obtained, where the first operation includes uploading partial code data of the applet to an applet auditing platform. In some embodiments, this step 310 may be performed by the acquisition module 210.

The applet auditing platform is a platform capable of auditing the safety, performance, content and the like of the applet, and by auditing the applet, the management and control of the applet can be improved, and the applet can be released and online. In some embodiments, the applet auditing platform may be an applet publishing platform. That is, the applet auditing platform may be a one-stop platform that provides an applet publishing process and corresponding operational capabilities. In some embodiments, the applet auditing platform may obtain operations corresponding to different instructions of the applet auditing platform, such as a first operation, a second operation, and the like of a user on the platform. For example, the first operation may be an operation in which an applet developer (i.e., a user) uploads written portions of applet code data to an applet auditing platform, and the second operation may be an operation in which the applet developer submits an audit on the applet. In some embodiments, the applet auditing platform can perform functions such as storing or code management on the applet code based on the uploading operation (i.e. the first operation) of the user; the applet auditing platform can audit the code data of the applet based on the submission auditing operation (namely, the second operation) of the user, the applet is allowed to be issued online when the auditing is passed, and the developer is informed to modify the data of the applet when the auditing is not passed.

In some embodiments, the first operation may comprise a direct upload operation or an indirect upload operation. For example only, the first operation may be an operation in which the user uploads the applet code data to the applet auditing platform through another terminal device. For example, an applet developer may edit the applet code on an applet editor, the first operation may be an operation of uploading the applet code to an applet auditing platform after the developer edits part of functions of the applet, and the applet auditing platform may obtain the first operation of the user based on data uploaded from the applet editor. In some embodiments, the applet developer may perform an upload operation of some or all of the applet data directly on the page of the applet auditing platform. For example, a user may upload part of the code data of the applet to the applet review platform by clicking an upload button in the applet review platform page. By uploading part or all of the code data of the applet to the applet auditing platform, the edited applet code data can be saved to the applet auditing platform.

And 320, calling a first auditing module to perform first auditing on part of the uploaded code data of the applet based on the first operation. In some embodiments, this step 320 may be performed by the first review module 220.

In some embodiments, the audit item of the applet may include at least one of a security audit, a content audit, and a capability audit. For example, the security audit may include a code security audit, a user privacy security audit, and a data security audit. Content review may mean that the content in the applet to be reviewed must not include pornography, violence, sensitive topics, or other illicit content. Capability audit can refer to an audit of the capabilities that an applet can normally implement and run. For example, applets do not have a severe Bug. For example, a Bug may include, but is not limited to, not being able to add, not being able to open, not being able to return, not being able to exit, being badly stuck, being easily crashed, etc.

In some embodiments, since in the first operation, the user only uploads the partial code data of the applet on the applet auditing platform, the processing device may invoke a first auditing module containing only partial applet auditing items to perform a first audit on the uploaded partial code data of the applet. For example, all audit items for the applet audit include a security audit, a content audit and a performance audit, and the first audit module may only include the security audit and the content audit on the applet part code data. In some embodiments, the audit items for the first audit can be 10% -95% of the total audit items for the applet. For example, the audit items for the first audit can be 30% -50% of the total audit items. For another example, the audit items for the first audit can be 50% to 80% of all audit items. For another example, the audit items for the first audit can be 80% -95% of all audit items. Preferably, the audit items for the first audit can be 80% of the total audit items. It will be appreciated that the above numerical ranges are merely exemplary, and that in some alternative embodiments, the first review item may be any percentage of the total review items, e.g., consistent with the total review items, and the description is not intended to be limiting.

In some embodiments, the first review may include a local review or a remote review. For example, the applet auditing platform may invoke, by a server (e.g., the server 110) of the applet auditing platform, a first auditing module to perform a first auditing on the uploaded partial code data of the applet based on the first operation of the user to obtain a first auditing result. For another example, the applet auditing platform may send the uploaded partial code data of the applet to the first terminal device based on the first operation of the user, where the first terminal device performs a first audit on the partial code data of the applet, and obtains a first audit result of the partial code data of the applet by the first terminal device.

In some embodiments, the processing device may perform a first audit of the applet through the trained machine learning model. For example, partial code data of the applet may be input into the trained first audit model, and a first audit result output by the first audit model is obtained.

The processing device may perform a first audit operation on a portion of the applet code data uploaded to the applet audit platform after each acquisition of a first operation (i.e., an upload operation) of the user. The method has the advantages that partial code data of the small program are audited based on the user uploading operation, so that problems (such as potential safety hazards, code errors and the like) in the code data of the small program can be found in time, developers can modify the code data in time, the failure rate of auditing all the code data of the small program based on the user submitting the auditing operation is reduced, and the online efficiency of the small program is improved.

And step 330, sending the first examination result of the applet to the user. In some embodiments, this step 330 may be performed by the sending module 230.

The first review result may include a pass and a fail of the review. In some embodiments, the processing device may generate a first review report for the applet based on the first review result. For example, an error report can be generated based on a problem with the applet code data in the first review result. For example, the error report may include, but is not limited to, an oversized picture in the applet, a data security hazard, and the like. In some embodiments, the first review report may include a combination of one or more of the results of the review, the problems present, the location of the problems, and the like. For example, the audit report may be: the audit is not passed, and the 35 th line of the code has data safety hidden danger and the like; or the audit report may be: the audit is passed, or no problem is found in the part of code data.

In some embodiments, the processing device may store the first audit report of the applet in a storage device (e.g., database 140). In some embodiments, the processing device may send a first audit report to the applet developer (i.e., the user). For example, the first review report may be sent to the developer's terminal device. In some embodiments, the processing device may send a data link containing the first review report or the first review result to the user. For example, a prompt may be sent to the user like "review is complete, click on this connection to view the results of the review".

The developer may re-upload the part of the data after modifying the applet code data based on the first review result, or upload the part of the data together after updating the new code data, which is not limited in this specification.

If the user operation obtained through the applet auditing platform is still the first operation of the user, the process returns to step 310. For example, the user may modify the error and modify a portion of the applet code data before uploading again. If the user operation obtained through the applet auditing platform is the second operation of the user, then step 340 is performed.

And 340, acquiring a second operation of the user, calling a second auditing module to perform second auditing on all code data of the applet based on the second operation, and allowing the applet to be issued when all the code data of the applet pass the second auditing. In some embodiments, this step 340 may be performed by the second review module 240.

The second operation may refer to the user initiating a submit review request to the applet review platform. For example, after a user (developer) completes all functions of the applet and uploads all corresponding code data to the applet auditing platform, an auditing request can be initiated to the applet auditing platform by clicking 'submit auditing' of the applet auditing platform page. In some embodiments, the user may also initiate a submit audit request after uploading portions of the code data of the applet. The processing device may call the first auditing module to perform second auditing on all code data of the applet based on the second operation of the user acquired by the applet auditing platform. In some embodiments, the second audit may perform an audit on code data that was not reviewed in the first audit. In some embodiments, the second audit can perform an audit on the code data modified after the first audit. In some embodiments, the second audit can review all code data of the applet. For example, it is possible to check whether or not the functions that can be realized in all the code data of the applet relate to the contents of violence, violation of social moral, violation of laws and regulations, whether or not the information such as user privacy can be protected in the functions that can be realized by the code data, whether or not the pictures and the like that are related in the code data can be normally displayed, whether or not the application program interface capability of the applet satisfies the distribution requirement, and the like. In some embodiments, the second audit can include all audit items for the applet. In some embodiments, the applet review item of the first review module can be part of an applet review item of the second review module. In some embodiments, the applet review items of the first review module can be the same as the applet review items of the second review module.

In some embodiments, all code data of the applet can be input into the second audit model through the trained second audit model, and a second audit result output by the second audit model is obtained. In some embodiments, the second audit model may be the same or different audit model than the first audit model. For example, the first audit model and the second audit model may be the same model, and when the first audit is triggered based on the user upload operation (i.e., the first operation), a part of applet audit modules (e.g., the first audit module) in the audit model may be called to perform corresponding audit operations, and when the second audit is triggered based on the user submission of the audit operation (i.e., the second operation), all of the audit modules (e.g., the second audit module) in the audit model may be called to perform corresponding audit operations.

And if all code data of the small program pass the second audit, allowing the small program to be issued. For example, the applet auditing platform may publish the applet directly. In some embodiments, if all code data of the applet fails the second audit, the audit may be rejected and a second audit report generated. In some embodiments, the applet review platform may send the generated second review report to the user for the user to make changes to the applet code data.

In some embodiments, the processing device may perform a live test service on the applet when the applet passes the first audit or the second audit. And the real machine testing service comprises the step of running the small program on the second terminal equipment. For example, the applet may be serviced for live testing based on partial code data of the applet uploaded to the applet auditing platform. By carrying out real machine test service on the small program, whether the functions of the small program can be normally realized on the terminal equipment can be tested. In some embodiments, the processing device may determine whether to publish the applet based on the live machine test result. For example, the function of the applet cannot be normally executed in the terminal device, and the result can be fed back to the developer so that the developer can modify the applet and then review and/or release the applet after the modification.

The applet auditing method provided by the embodiment of the description can trigger the first auditing operation aiming at the part code data of the applet in a continuous construction mode when the applet auditing platform acquires the part code data of the applet uploaded by a user every time, can help a developer to find out the problems existing in the applet code data in time so as to solve the problems in time, and can improve the applet auditing passing rate based on the submitting operation by 20%.

It should be noted that the above description of method 300 is for purposes of example and illustration only and is not intended to limit the scope of applicability of the present description. Various modifications and alterations to method 300 will become apparent to those skilled in the art in light of the present description. However, such modifications and variations are intended to be within the scope of the present description. For example, in step 330, after the first review result is sent to the user, the code data modified by the user may be acquired from the terminal device, and the first review operation may be performed again.

The beneficial effects that may be brought by the embodiments of the present description include, but are not limited to: (1) after the small program developer develops part of the codes, the small program developer can trigger the auditing operation in an uploading mode and obtain the auditing result, and can modify the code data with problems in time, so that the auditing passing rate can be greatly improved; (2) the verification can be carried out without waiting for the completion of all the small program code data, the time for verifying and returning the verification result is shortened, the verification passing rate is improved, and meanwhile, the small program can be ensured to be on-line on time. It is to be noted that different embodiments may produce different advantages, and in different embodiments, any one or combination of the above advantages may be produced, or any other advantages may be obtained.

Having thus described the basic concept, it will be apparent to those skilled in the art that the foregoing detailed disclosure is to be considered merely illustrative and not restrictive of the embodiments herein. Various modifications, improvements and adaptations to the embodiments described herein may occur to those skilled in the art, although not explicitly described herein. Such modifications, improvements and adaptations are proposed in the embodiments of the present specification and thus fall within the spirit and scope of the exemplary embodiments of the present specification.

Also, the description uses specific words to describe embodiments of the description. Reference throughout this specification to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic described in connection with at least one embodiment of the specification is included. Therefore, it is emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, some features, structures, or characteristics of one or more embodiments of the specification may be combined as appropriate.

Moreover, those skilled in the art will appreciate that aspects of the embodiments of the present description may be illustrated and described in terms of several patentable species or situations, including any new and useful combination of processes, machines, manufacture, or materials, or any new and useful improvement thereof. Accordingly, aspects of embodiments of the present description may be carried out entirely by hardware, entirely by software (including firmware, resident software, micro-code, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. Furthermore, aspects of the embodiments of the present specification may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media.

The computer storage medium may comprise a propagated data signal with the computer program code embodied therewith, for example, on baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, etc., or any suitable combination. A computer storage medium may be any computer-readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code located on a computer storage medium may be propagated over any suitable medium, including radio, cable, fiber optic cable, RF, or the like, or any combination of the preceding.

Computer program code required for operation of various portions of the embodiments of the present description may be written in any one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C + +, C #, VB.NET, Python, and the like, a conventional programming language such as C, VisualBasic, Fortran2003, Perl, COBOL2002, PHP, ABAP, a dynamic programming language such as Python, Ruby, and Groovy, or other programming languages, and the like. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or processing device. In the latter scenario, the remote computer may be connected to the user's computer through any network format, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet), or in a cloud computing environment, or as a service, such as a software as a service (SaaS).

In addition, unless explicitly stated in the claims, the order of processing elements and sequences, use of numbers and letters, or use of other names in the embodiments of the present specification are not intended to limit the order of the processes and methods in the embodiments of the present specification. While various presently contemplated embodiments of the invention have been discussed in the foregoing disclosure by way of example, it is to be understood that such detail is solely for that purpose and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements that are within the spirit and scope of the embodiments herein. For example, although the system components described above may be implemented by hardware devices, they may also be implemented by software-only solutions, such as installing the described system on an existing processing device or mobile device.

Similarly, it should be noted that in the preceding description of embodiments of the specification, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more embodiments of the invention. This method of disclosure, however, is not intended to imply that more features are required than are expressly recited in the claims. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.

For each patent, patent application publication, and other material, such as articles, books, specifications, publications, documents, etc., cited in this specification, the entire contents of each are hereby incorporated by reference into this specification. Except where the application history document does not conform to or conflict with the contents of the present specification, it is to be understood that the application history document, as used herein in the present specification or appended claims, is intended to define the broadest scope of the present specification (whether presently or later in the specification) rather than the broadest scope of the present specification. It is to be understood that the descriptions, definitions and/or uses of terms in the accompanying materials of this specification shall control if they are inconsistent or contrary to the descriptions and/or uses of terms in this specification.

Finally, it should be understood that the embodiments described herein are merely illustrative of the principles of the embodiments of the present disclosure. Other variations are possible within the scope of the embodiments of the present description. Thus, by way of example, and not limitation, alternative configurations of the embodiments of the specification can be considered consistent with the teachings of the specification. Accordingly, the embodiments of the present description are not limited to only those embodiments explicitly described and depicted herein.

Claims

1. An applet auditing method applied to an applet auditing platform, the method comprising:

acquiring a first operation of a user through the applet auditing platform, wherein the first operation comprises uploading partial code data of the applet to the applet auditing platform;

calling a first auditing module to conduct first auditing on part of uploaded code data of the applet based on the first operation;

sending the first review result of the applet to the user;

and acquiring a second operation of the user through the applet auditing platform, calling a second auditing module to perform second auditing on all code data of the applet based on the second operation, and allowing the applet to be issued when all the code data of the applet pass the second auditing.

2. The method of claim 1, the invoking a first audit module to perform a first audit on the uploaded partial code data of the applet comprising:

the uploaded part of code data of the small program is sent to a first terminal device through the first auditing module, and the first terminal device conducts first auditing on the part of code data of the small program; and

and acquiring a first examination result of the first terminal device on the partial code data of the small program.

3. The method of claim 1, the applet auditing platform being an applet publishing platform.

4. The method of claim 1, further comprising:

performing real machine test service on the small program based on partial code data of the small program uploaded to the small program checking platform;

wherein the live testing service comprises running the applet at a second terminal device.

5. An applet auditing system, the system being applied to an applet auditing platform, the system comprising:

the acquisition module is used for acquiring a first operation of a user, wherein the first operation comprises uploading partial code data of the applet to the applet auditing platform;

the first auditing module is used for carrying out first auditing on the uploaded partial code data of the applet based on the first operation;

the sending module is used for sending the first examination result of the applet to the user;

and the second auditing module is used for acquiring second operation of the user, performing second auditing on all code data of the applet based on the second operation, and allowing the applet to be issued when all the code data of the applet pass through the second auditing.

6. The system of claim 5, the first review module to:

sending the uploaded partial code data of the small program to first terminal equipment, and performing first audit on the partial code data of the small program by the first terminal equipment; and

7. The system of claim 5, the applet auditing platform being an applet publishing platform.

8. The system of claim 5, further comprising a testing module to:

9. An applet auditing apparatus comprising a processor for performing the method of any one of claims 1 to 4.

10. A computer-readable storage medium storing computer instructions which, when read by a computer, cause the computer to perform the method of any one of claims 1 to 4.